Zachary Turner <divisorthe...@gmail.com> writes: > The codebase is large, but is new to linux. It was originally > developed on windows and then ported to linux. It makes heavy use of > C++, STL, and boost and we'd like to (if possible) link *everything* > statically. This means libc, libgcc, libstdc++, boost, libpthread, > etc.
This message is not appropriate for the gcc@gcc.gnu.org mailing list. It would be appropriate for the gcc-h...@gcc.gnu.org mailing list. Please take any followups to gcc-help. Thanks. This is actually not a gcc issue. This is a library issue. On GNU/Linux, the library is glibc. The glibc maintainers have decided that they do not want to support static linking (I personally disagree with this position). They only support dynamically linking against libc. Static linking sort of grudgingly works, but some things will fail. For example, if your statically linked program does DNS lookups, it will generally fail on any system which is not running the precise version of glibc as the system on which it was built. My guess is that the problems you are encountering are problems statically linking with glibc. You can certainly bring these up with the glibc maintainers--see http://sourceware.org/glibc . However, they will ignore you with prejudice. You may want to consider using -Bstatic and -Bdynamic to statically link everything except glibc. Ian
