Re: libstdc++.so did not link cause of libm.a was not compiled with fpic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Klaus Rudolph via Gcc-help:

> I try to cross compile gcc 14.1.0 for an older arm linux.
>
> During compilation it fails with a long list of linking problems for
> libstdc++.so
>
> I configured gcc with:
> ../configure --prefix=/opt/armv7_$(GCC_VERSION) --enable-languages=c,c++
> --with-sysroot=/opt/podman_debian8/merged --enable-multiarch
> --with-fpu=vfpv3-d16 --with-mode=thumb --with-arch=armv7-a
> --target=arm-linux-gnueabihf --disable-multilib --with-stdc++lib=static
>
> Is it possible to add/remove some flags for ./configure to get the new
> compiler to work even with the libm.a library from the target system
> which was not compiled with fPic.

It looks like you are targeting glibc.  You can't link static libm.a
while linking dynamically.  You need to use libm.so and libm.so.6.  The
libm.a archive can only be used with fully static links.

Thanks,
Florian




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux