diff options
| author | Gyorgy Sarvari <skandigraun@gmail.com> | 2026-02-04 09:57:30 +0100 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2026-02-06 10:06:18 -0800 |
| commit | bfbd962813058ec124f307d8323c28294974e8fc (patch) | |
| tree | 91407db6bdd3d8ccfcdaf226eee2c99c43e3b5b6 /meta-python/recipes-devtools/python/python3-flask-user_0.6.19.bb | |
| parent | 5ff9251b941d37f40a7158057ea3d5f4305f6a93 (diff) | |
| download | meta-openembedded-bfbd962813058ec124f307d8323c28294974e8fc.tar.gz | |
nodejs: extend libatomic patch to x86
This patch isn't intended to introduce new behavior, rather it
changes the order of some existing LDFLAGS to fix a workaround that
stopped working at some point in the past.
LDFLAGS:x86 contains libatomic, because linking with this library
is required for this platform.
However when gyp links, it invokes the following (pseudo-)command:
$LD $LDFLAGS $RESOURCES_TO_LINK $EXTRA_LIBS $EXTRA_LDFLAGS
The EXTRA* arguments are coming from the gyp config. Since
LDFLAGS appears very early in the command, libatomic also
appears early amongst the resources, and the linker couldn't
find the relevant symbols when compiled for x86 platform (as
it was processed the very last):
| [...] undefined reference to `__atomic_compare_exchange'
Using this patch the library appears at the end, along with
the other EXTRA_LIBS, after the list of linked resources,
allowing linking to succeed.
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-flask-user_0.6.19.bb')
0 files changed, 0 insertions, 0 deletions
