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

MacPorts noreply at macports.org
Sat Nov 19 13:22:31 PST 2011


#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 wouter+macports@…):

 This problem is caused by the newly-built libstdc++ having a different
 value for the _GLIBCXX_FULLY_DYNAMIC_STRING macro than the system
 libstdc++ (against which ld and friends are built), and during stage2 and
 further compilation the environment being set to prefer the newly-built
 libstdc++ as opposed to the system libstdc++, ''even for ld''.

 This causes the problem explained here:

 [http://newartisans.com/2009/10/a-c-gotcha-on-snow-leopard/#comment-893]

 To add to the confusion, the conclusion made in the linked explanation
 above is wrong: on Snow Leopard, _GLIBCXX_FULLY_DYNAMIC_STRING is ''not''
 defined:

 {{{
 $ grep FULLY_DYNAMIC_STRING /usr/include/c++/4.2.1/i686-apple-
 darwin10/bits/c++config.h
 /* #undef _GLIBCXX_FULLY_DYNAMIC_STRING */
 }}}

 Therefore, this problem is fixed by:

 {{{
 --- Portfile.orig       2011-11-19 22:09:53.000000000 +0100
 +++ Portfile    2011-11-19 22:17:45.000000000 +0100
 @@ -119,7 +119,6 @@
         configure.args-append --with-dwarf2
  }
  platform darwin 10 {
 -       configure.args-append --enable-fully-dynamic-string
  }

  platform darwin 11 {
 }}}

 With this change, gcc46 builds and installs successfully for me. I have no
 idea what should be done for Lion, as I have no access to such a system.

 Hope that helps.

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


More information about the macports-tickets mailing list