On Tue, 22 May 2007 08:50:00 -0600, Marc Aurele La France wrote: > Now, is there anything else that you think needs fixing here? I can only remember another patch I put on locally here, as I want to set this in the custom build/config/cf/host.def: >>>>cut-here>>>> --- xc/config/cf/darwin.cf_orig 2007-04-25 09:42:47 -0500 +++ xc/config/cf/darwin.cf 2007-04-25 10:18:58 -0500 @@ -315,7 +315,9 @@ #define BuildLibPathVar DYLD_LIBRARY_PATH +#ifndef DefaultUserPath #define DefaultUserPath /bin:/sbin:/usr/bin:/usr/sbin:$(BINDIR) +#endif #define DefaultSystemPath DefaultUserPath /* include rules to build shared libraries */ <<<<cut-here<<<< In my host.def I specify: #define DefaultUserPath $(PATH):$(BINDIR) to pick up the normal user environment (it's really long). Of course this mod will affect all platforms. But let me try to explain why I do this. This is to be sure we run the new(er) code in /usr/local/bin and other places rather than the vendor's old cruft in /usr/bin during _all_ phases. There are other tricks e.g. to set [DY]LD_ for similar reasons. Specifically for darwin/osx, we mainly do this in the user's ~/.MacOSX/environment.plist as well as root's, so the boot-system, early GUI-related apps, Finder, and all spawned apps including XDarwin.app will get the same long paths and hopefully run with newer bins & libs etc. even during early single-user mode (yes I have modified /etc/rc* scripts as well). I know $(PATH) in host.def will be resolved at build time, but at least this will pick up the same long string, without our having to manually modify any /etc/X11 stuff or in users' hidden $HOME parmfiles. I hope at least. ;) (Since I can't afford $ADC$ account to test Leopard officially, this is the next-best effort to get up on latest code and to override what Apple provides at all levels, hoping to spot any problems before they include it into Leopard. I'm mainly interested in free / open apps, not caring much for any new proprietary gizmos that they are of course adding to Leopard, per se. I'll try to take any problem to the project itself, not to Apple, as I'm doing here. My philosophy is that the project ought to build & function properly straight out of the tarball and without any pkg-mgr "help" even officially from the vendor. ;) ) As a final _final_ test, regardless -- When the public cvs server gets that latest XDarwin.app symlink patch pushed to it, let's do a complete new checkout and build it. Are we getting close to an official 4.7 release? :) Thanks for discussing this. _______________________________________________ Devel mailing list Devel@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/devel
