#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: -----------------------------------+---------------------------------------- Changes (by blb@…): * cc: blb@… (added) Comment: The basic issue is that configure does set CC to compile, but it only sets it to 'gcc' instead of the full path; we need to either keep the modified PATH from configure during the build or to get the AC_PROG_CC to give us a full path. -- Ticket URL: <http://trac.macports.org/ticket/19051#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#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

#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@…): Ah, yes, I think I understand the real issue now. I didn't know that configure removed ${prefix}/bin and ${prefix}/sbin from PATH before doing anything else, but reading through configure.ac and aclocal.m4 makes that clear. So, Yes, I also think the proposed solution should work. Assuming that these proposed changes are used, my question is then: Should 'configure' be changed, or 'configure.ac'? If I execute './regen.sh' then I end up with a new 'configure' which would override the proposed changes to that file; hence I think the latter is the appropriate place for those particular changes. I think another way to do this would be to set the PATH before executing 'configure' in /Library/Tcl/macports1.0/macports.tcl:1908 ... since commands are chained within the same system call (cd ... && export PATH=... && configure ... && make && make install), the PATH would be properly carried over, and used just for that system call. This method would use a Tcl routine to modify the incoming PATH and pass that knowledge to the system command, as opposed to the proposed method that does it inside 'configure' and then passing the knowledge on to the top- level 'Makefile'. -- Ticket URL: <http://trac.macports.org/ticket/19051#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#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@…): Ah. Good points all around; I obviously hadn't thought through enough angles for how to accomplish this change. If your patches work as is, then I, for one, am all for them. -- Ticket URL: <http://trac.macports.org/ticket/19051#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS