[MacPorts] #27237: gcc46: checking for -exported_symbols_list linker flag... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[MacPorts]

#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 ionic@…):

 Oh, sorry wouter, I totally forgot to report back here.

 I've used the GCC mailinglist to shed some light on this bug.

 X referencing http://gcc.gnu.org/ml/gcc-help/2011-10/msg00250.html now.

 tl;dr: see below.

 Yes, I can confirm that disabling the fully dynamic string setting seems
 to fix the problem (on SL.)
 Also, I can confirm that I have *no idea whatsoever* why
   - it fucking works for GCC < 4.6
   - it crashes badly for GCC >= 4.6

 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.

 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.

 tl;dr: confirming that disabling the fully dynamic string option makes GCC
 build just fine on SL.

-- 
Ticket URL: <https://trac.macports.org/ticket/27237#comment:20>
MacPorts <http://www.macports.org/>
Ports system for Mac OS