#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