Apple LD always uses a dylib if present (was: Build gcc-4.9.4 on OSX-ppc ...)

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

 



>> [QUESTION]: libiconv included in sourcetree was build, but later ignored at link time in favor of system libiconv?
>
> The system linker ld64 [at least at the 85.2.1 version from XCode 3.1.4] will prefer a shared library if it finds one (even if there is a convenience library of the same name first on the link line).
>
> There is a reason for this - to do with the different model for symbol resolution in the Mach-O toolchain (c.f. the ELF ones, for example).  This has some advantages (only need to present libraries once) and some gotchas (the shlib will be found over the convenience one).  Recent versions of ld64 have more controls over this, but you’d need to use my port of the PPC stuff (since that was dropped from ld64 around XCode 3.2.x).

Thanks for that Iain. I've always wondered about that behavior;
especially on iOS where most user programs cannot dynamically link to
libraries.

Jeff




[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