David R. Morrison wrote: > mv: rename /sw/src/root-xfree86-base-4.2.0.1-1/sw/../Applications to > /sw/src/root-xfree86-rootless-4.2.0.1-1/sw/../Applications: No such > file or directory > > This *is* affected by linking /sw to another location, because of the leading > /sw in the path.
Sorry to contradict you here, Dave, but I think you are wrong. I have several fink installations, all of them with /sw symlinked to somewhere else, and I never had any problem with this, in particular not with the xfree86 packages. If Alan's problem is similar to the one reported a week ago by Eric Oberle (I don't know for sure, Alan doesn't give enough details), then the problems start much earlier in the compilation process, long before the splitoff mechanism tries to move things over from root-xfree86-base to root-xfree86-rootless. "/sw/../Applications" should be OK in any case. The problem is that the /Applications folder did not get created at the right place by the ProjectBuilder procedures. Im my logs I have, for example, a line mkdir -p /sw/src/root-xfree86-base-4.2.0.1-2/Applications/XDarwin.app/Contents/MacOS which comes from inside the xfree86 install process. It seems that this is not present in Eric's (and Alan's?) log. Instead, there is some /sw/src/Applications folder created which is empty (the latter is not surprising, since all things that should be copied inside are aimed at /sw/src/root-xfree86-base-4.2.0.1-2/Applications/ and will drop on the floor). The real reason for the strange behavior is not clear. My bet is on old or broken dev tools that don't work with Jaguar. -- Martin ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
