Le 25 mai 2010 à 15:42, Kjell Øyvind Konstali a écrit : > Hello, glad I could help :) > > By logging I mean a way to save all the warning messages to a > textfile, so that I can see clearer what files are considered a > warning. > Because there where many warnings about the NSU/NSinteger vs > unsigned/int (but not serious enough to brake the build) so I want to > go over them too.
make 2> build.log This redirects stderr (warnings and errors) to the given file. You still get the progress of the build in the shell but not the warning and the errors. > And, is Etoile broken? after setup.sh Etoile can't find etoile_system > so I'm not sure what next to do :) It wasn't broken (or rather it got fixed) in the middle of the last week, the last time I tried a full build. Are you sure GNUstep.sh was sourced when you ran setup.sh? Check the content of /usr/local/bin/etoile.sh, it should look like: . <prefix>/System/Library/Makefiles/GNUstep.sh; etoile_system If /usr/local/bin/etoile looks wrong, you can source GNUstep.sh and rerun setup.sh if necessary. To be sure GNUstep.sh is sourced, type 'env', you should get various variables prefixed by 'GNUSTEP' when GNUstep.sh has been sourced. Once /usr/local/bin/etoile.sh looks ok, check also that etoile_system can be found with 'which etoile_system' which should print: <prefix>/System/Tools/etoile_system Then the easiest way to test etoile_system is to use a xterm failsafe session and run 'etoile' or 'etoile_system' here. Cheers, Quentin. _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
