[MacPorts] #19051: port selfupdate: error in installing new macports base 1.7.1

MacPorts noreply at macports.org
Tue Mar 31 08:54:06 PDT 2009


#19051: port selfupdate: error in installing new macports base 1.7.1
-----------------------------------+----------------------------------------
 Reporter:  senz@…                 |       Owner:  macports-tickets@…                   
     Type:  defect                 |      Status:  new                                  
 Priority:  High                   |   Milestone:  MacPorts Future                      
Component:  base                   |     Version:  1.7.1                                
 Keywords:  port selfupdate error  |        Port:                                       
-----------------------------------+----------------------------------------

Comment(by mlk@…):

 Having the partial or full path to 'gcc' doesn't really matter; what does
 matter is making sure the found 'gcc' is an Apple-variant.  I think
 configure is working as it should be; I think what needs to happen is to
 set "... && CC=/usr/bin/cc && ./configure ...".  Here's my efforts and
 analysis into coming to that conclusion:

 Actually (and, yes, I tested all of these out), the issue is that
 configure sets CC to be (in this case) the -first- version of GCC found in
 PATH.  Let's assume that /opt/local/bin is before /usr/bin in PATH, as is
 typically the case in order to get the MacPorts-provided.  With
 'gcc_select' installed, 'sudo gcc_select gcc40' will set
 /opt/local/bin/gcc to symlink to /usr/bin/gcc, or Apple's GCC 4.0 variant.
 Now if you do 'sudo port selfupdate' it will work.  OTOH, if I have the
 port gcc43 installed, 'sudo gcc_select mp-gcc43' will set
 /opt/local/bin/gcc to symlink to ./gcc-mp-4.3 .  Doing 'sudo port
 selfupdate' not will not work.  Further , even if I do 'export
 CC=/usr/bin/gcc-4.2' then 'sudo port selfupdate', my desired CC
 environment value is ignored (because the update is occurring -through-
 the 'port' command in a shell it is creating) .. this not the case if I do
 'configure' manually from my shell (the CC value I specify is used).

 What needs to happen, I think, is to manually "export CC=/usr/bin/cc" (or
 whatever, so long as CC is set to an Apple-provided compiler) before
 executing the 'configure' command; this is, I think, done at
 /Library/Tcl/macports1.0/macports.tcl:1908 .  This won't work for the
 1.7.1 or 1.7.2 release, but it could be incorporated into the 1.7.2
 release into order to take effect starting with 1.7.3 (assuming those are
 the release numbers for future releases).

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


More information about the macports-tickets mailing list