[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu May 26 06:34:08 EDT 2005 If a particular system failed compilation, the logs for that system will be placed at ftp://ftp.gnustep.org/pub/testfarm If you would like to add your machine to this list, set up a cron job (make sure you set up your PATH and other environment variables correctly) to run the Startup/scripts/test-gnustep script (see the script comments for more info). Success Compile i386-unknown-netbsdelf2.0.2 Thu May 26 03:58:17 CEST 2005 Success Compile powerpc-apple-darwin7.9.0 Thu May 26 04:26:40 MDT 2005 Success Compile sparc-sun-solaris2.7 Thu May 26 02:09:04 EDT 2005
[Gnustep-cvs] gnustep/core/gui ChangeLog Source/NSTableView.m
CVSROOT:/cvsroot/gnustep Module name:gnustep Branch: Changes by: Fred Kiefer [EMAIL PROTECTED] 05/05/26 13:38:11 Modified files: core/gui : ChangeLog core/gui/Source: NSTableView.m Log message: Improved mouseDown call handling for table view. CVSWeb URLs: http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/ChangeLog.diff?tr1=1.2528tr2=1.2529r1=textr2=text http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/gui/Source/NSTableView.m.diff?tr1=1.116tr2=1.117r1=textr2=text
Re: Building in a separate directory
On 26/05/2005, at 1:00, Adam Fedor wrote: It might be nice to fix autoconf, but then you'll run into make. 'make' doesn't like spaces in directories either - and this is a fundamental design issue. But doesn't make always run in the same directory? Anyway I'm placing this on the back burner for some time, and it's been a long time since I read the GNU make manual. But I think that this issue needs to be solved someday because directories with spaces are very common this days (Windows' C:\Program Files, for example). I'm now deeply immersed in cross-compiling, though. I'm also reviewing how Autoconf works and how it's applied through GNUstep. My knowledge of Autoconf is somewhat superficial right now. The first problem I've detected is that the macro AC_FUNC_SETPGRP prevents cross-compiling because it always needs to run the test program that it constructs in order to check the signature of setpgrp. I haven't found how to circumvent it yet. Cheers, David. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Building in a separate directory
On May 26, 2005, at 12:04 PM, David Lázaro Saz wrote: On 26/05/2005, at 1:00, Adam Fedor wrote: It might be nice to fix autoconf, but then you'll run into make. 'make' doesn't like spaces in directories either - and this is a fundamental design issue. But doesn't make always run in the same directory? Anyway I'm placing this on the back burner for some time, and it's been a long time since I read the GNU make manual. But I think that this issue needs to be solved someday because directories with spaces are very common this days (Windows' C:\Program Files, for example). I'm now deeply immersed in cross-compiling, though. I'm also reviewing how Autoconf works and how it's applied through GNUstep. My knowledge of Autoconf is somewhat superficial right now. The first problem I've detected is that the macro AC_FUNC_SETPGRP prevents cross-compiling because it always needs to run the test program that it constructs in order to check the signature of setpgrp. I haven't found how to circumvent it yet. if test $cross_compiling = no; then AC_FUNC_SETPGRP else #set a default value fi I was working on that, but the default for MingW is not what the normal default would be, but I wasn't entirely sure. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Building in a separate directory
On May 26, 2005, at 12:36 PM, Adam Fedor wrote: if test $cross_compiling = no; then AC_FUNC_SETPGRP else #set a default value fi I was working on that, but the default for MingW is not what the normal default would be, but I wasn't entirely sure. Actually, now I look at the code, it could probably just be: if test $cross_compiling = no; then AC_FUNC_SETPGRP fi ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Building in a separate directory
On 26/05/2005, at 20:52, Adam Fedor wrote: Actually, now I look at the code, it could probably just be: if test $cross_compiling = no; then AC_FUNC_SETPGRP fi I'll try that; I think that would be sufficient too. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Building in a separate directory
Adam Fedor wrote: On May 26, 2005, at 12:04 PM, David Lázaro Saz wrote: On 26/05/2005, at 1:00, Adam Fedor wrote: It might be nice to fix autoconf, but then you'll run into make. 'make' doesn't like spaces in directories either - and this is a fundamental design issue. But doesn't make always run in the same directory? Anyway I'm placing this on the back burner for some time, and it's been a long time since I read the GNU make manual. But I think that this issue needs to be solved someday because directories with spaces are very common this days (Windows' C:\Program Files, for example). I'm now deeply immersed in cross-compiling, though. I'm also reviewing how Autoconf works and how it's applied through GNUstep. My knowledge of Autoconf is somewhat superficial right now. The first problem I've detected is that the macro AC_FUNC_SETPGRP prevents cross-compiling because it always needs to run the test program that it constructs in order to check the signature of setpgrp. I haven't found how to circumvent it yet. if test $cross_compiling = no; then AC_FUNC_SETPGRP else #set a default value fi I was working on that, but the default for MingW is not what the normal default would be, but I wasn't entirely sure. Autoconf is rather easy to work around, as long as you have the informations on the correct settings for the traget system. Perhaps it would even be possible to run autoconf on the target system and transfer the results to the actual build environment? For simple settings like AC_FNUC_SETGRP it is sufficent to set an environment variable stating the presense/absense of the feature. Here the settings I used to cross compile for an ARM system: export cl_cv_c_longlong=yes export ac_cv_func_setpgrp_void=yes ./configure --prefix=/home/zaurus/gnustep --disable-flattened \ --host=arm-linux --build=ix86-linux \ --libdir=/home/zaurus/gnustep/System/Library/Libraries/arm/linux-gnu \ --includedir=/home/zaurus/gnustep/System/Library/Headers/gnu-gnu-gnu \ --disable-do For me this looks easier than trying to guess the correct default value for all the systems and hard coding that in the .ac file. Fred ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
