#27237: gcc46: checking for -exported_symbols_list linker flag... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gcc46 -------------------------------------+-------------------------------------- Comment(by dports@…): There's also some discussion of this in #31171 which might be worth looking at. Replying to [comment:20 ionic@…]:
You probably are right that the base OS X system (including ld and such) have been built *without* this feature. We may have just gotten lucky with GCC 4.5 working, even though this feature was enabled.
Yes, I agree, that does seem to be the case. I don't see any evidence that the system libstdc++ is built with fully dynamic strings. It doesn't appear that way on my Lion system, and it sounds like it isn't on SL either.
Also, none of this answers how "JOHNW" or the people he's working with could fix their problem by enabling the fully dynamic string option. My best guess is that actually the boost building procedure is "broken" and produces libraries with this setting turned on by default, thus causing those kind of problems.
I suspect the original problem was something else -- possibly related to _GLIBCXX_DEBUG. Unless anyone can come up with a reason not to, and assuming a couple more tests pass, I'll remove the --enable-fully-dynamic-string option. -- Ticket URL: <https://trac.macports.org/ticket/27237#comment:21> MacPorts <http://www.macports.org/> Ports system for Mac OS