#7203: gcc4 seems to have an issue locating libraries ----------------------------+---------------------------- Reporter: scottmc | Owner: zooey Type: bug | Status: new Priority: high | Milestone: R1/alpha3 Component: Build System | Version: R1/Development Resolution: | Keywords: gcc4 Blocked By: | Blocking: Has a Patch: 0 | Platform: x86 ----------------------------+---------------------------- Comment (by bonefish): I would strongly advise against mixing gcc 2 and gcc 4 executables and libraries even if the runtime loader still supports that. With the introduction of support for weak symbols and symbol preemption gcc 4 shared objects, unlike gcc 2 ones, are no longer linked symbolically. As a result, with such mixing, symbol resolution will be inconsistent. This doesn't necessarily need to lead to problems -- it will probably work just fine in most cases -- but that's virtually impossible to predict. Hence I'd recommend to treat gcc 2 and gcc 4 as separate architectures and build complete library sets for each. Regarding building packages for the hybrid-other compiler, I'm not sure whether the compiler/linker does search the gcc* subdirectories as expected. IIRC I introduced some symlink trickery that should make those directories visible to the compiler, but I don't recall whether there are built-in paths that would be searched first, thus potentially finding the wrong libraries first. The safest way to build gcc 4 libraries is on a gcc4[h] haiku. -- Ticket URL: <http://dev.haiku-os.org/ticket/7203#comment:7> Haiku <http://dev.haiku-os.org> Haiku - the operating system.