On 2010-6-18 06:04 , Ryan Schmidt wrote: > > On Jun 17, 2010, at 14:50, Joshua Root wrote: > >> On 2010-6-18 05:45 , Ryan Schmidt wrote: >>> >>> On Jun 17, 2010, at 14:29, Joshua Root wrote: >>> >>>> On 2010-6-18 05:14 , Ryan Schmidt wrote: >>>>> >>>>> You made the changes described in UsingTheRightCompiler to discover when >>>>> ports are not using the configure.cc etc. variables. You have now >>>>> discovered that MacPorts itself does not use configure.cc when >>>>> selfupdating. See: >>>>> >>>>> http://trac.macports.org/ticket/23095 >>>>> >>>>> That ticket says this was supposed to have been fixed.... If it's not, >>>>> the ticket should be re-opened. >>>>> >>>>> Until it's fixed, you will need to undo the changes described in >>>>> UsingTheRightCompiler in order to proceed. (I generally just edit the >>>>> binpath and change /opt/local/bin/no_default_gcc by one character, e.g. >>>>> change it to /opt/local/bin/no_default_gccx (a path that doesn't exist) >>>>> so that when I later want to re-enable it again I just have to change one >>>>> character to do so. >>>> >>>> The base configure script removes $prefix from its PATH. When it's >>>> running from within MacPorts, 'gcc' *is* the right compiler for it to >>>> use, so #23095 is a complete non-issue unless you've messed with >>>> extra_env (unsupported) or actually changed what /usr/bin/gcc points to >>>> (also unsupported). >>> >>> Well it doesn't seem to remove "/opt/local/bin/no_default_gcc" from the >>> path (nor would I expect it to), >> >> Exactly. Doing precisely what you asked it to. > > Yes exactly. So #23095 is completely the relevant ticket, since it causes > selfupdate to not use "gcc" anymore but to use the specific appropriate > compiler.
My point is that 'gcc' would be fine had you not intentionally sabotaged it using binpath. - Josh _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
