You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by zhangzhiqiangcs May 2, 2024
Hi, all, I try to build a static bpftrace binary on my arm64 manchine in a alpine:3.18 container, just followed the docker/Dockerfile.static and static.sh, the build process always filed at final link stage with err
-fpic
Generate position-independent code (PIC) suitable for use in a shared library, if supported for the target machine. Such code accesses all constant addresses through a global offset table (GOT). The dynamic loader resolves the GOT entries when the program starts (the dynamic loader is not part of GCC; it is part of the operating system). If the GOT size for the linked executable exceeds a machine-specific maximum size, you get an error message from the linker indicating that -fpic does not work; in that case, recompile with -fPIC instead. (These maximums are 8k on the SPARC, 28k on AArch64 and 32k on the m68k and RS/6000. The x86 has no such limit.)
Position-independent code requires special support, and therefore works only on certain machines. For the x86, GCC supports PIC for System V but not for the Sun 386i. Code generated for the IBM RS/6000 is always position-independent.
When this flag is set, the macros pic and PIC are defined to 1.
-fPIC
If supported for the target machine, emit position-independent code, suitable for dynamic linking and avoiding any limit on the size of the global offset table. This option makes a difference on AArch64, m68k, PowerPC and SPARC.
Position-independent code requires special support, and therefore works only on certain machines.
Discussed in #3148
Originally posted by zhangzhiqiangcs May 2, 2024
Hi, all, I try to build a static bpftrace binary on my arm64 manchine in a alpine:3.18 container, just followed the
docker/Dockerfile.static
andstatic.sh
, the build process always filed at final link stage with errThe text was updated successfully, but these errors were encountered: