Re: [Gnustep-cvs] GNUstep Testfarm Results
Richard Frith-Macdonald schrieb: > > On 14 Aug 2006, at 22:19, Fred Kiefer wrote: > >> Adam Fedor schrieb: >>> >>> On Aug 14, 2006, at 7:22 AM, Fred Kiefer wrote: In the most recent GSString.m version these methods are there only once. The first one is obsolete anyway, see NSString, where it gets defined as calling the second one. As this in now the only remaining usage of substring_c, we could try to do the inlining ourselves and put the code from the function inside the method. If this alone does not resolve the compilation issue, we could try to rework the actual code. Here the interesting question could be why the similar which calls substring_u works. >>> >>> No, both substring_c and substring_u have the problem Removing the >>> inlining or moving the struct definition out of the function block >>> solves the problem. >>> >> >> Great, so now we have a solution. But I think it is better to leave the >> actual implementation to Richard. He has been doing a lot of work in >> this area recently and there may still be more to come. This change >> looks simple, but it might interfere with something he is planing to do. >> >> Richard is it fine for you to do this change? > > OK .. no problem. > Thank you! The last test went through successfully on all three platforms. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On 14 Aug 2006, at 22:19, Fred Kiefer wrote: Adam Fedor schrieb: On Aug 14, 2006, at 7:22 AM, Fred Kiefer wrote: In the most recent GSString.m version these methods are there only once. The first one is obsolete anyway, see NSString, where it gets defined as calling the second one. As this in now the only remaining usage of substring_c, we could try to do the inlining ourselves and put the code from the function inside the method. If this alone does not resolve the compilation issue, we could try to rework the actual code. Here the interesting question could be why the similar which calls substring_u works. No, both substring_c and substring_u have the problem Removing the inlining or moving the struct definition out of the function block solves the problem. Great, so now we have a solution. But I think it is better to leave the actual implementation to Richard. He has been doing a lot of work in this area recently and there may still be more to come. This change looks simple, but it might interfere with something he is planing to do. Richard is it fine for you to do this change? OK .. no problem. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Adam Fedor schrieb: > > On Aug 14, 2006, at 7:22 AM, Fred Kiefer wrote: >> In the most recent GSString.m version these methods are there only once. >> The first one is obsolete anyway, see NSString, where it gets defined as >> calling the second one. As this in now the only remaining usage of >> substring_c, we could try to do the inlining ourselves and put the code >> from the function inside the method. If this alone does not resolve the >> compilation issue, we could try to rework the actual code. Here the >> interesting question could be why the similar which calls substring_u >> works. > > No, both substring_c and substring_u have the problem Removing the > inlining or moving the struct definition out of the function block > solves the problem. > Great, so now we have a solution. But I think it is better to leave the actual implementation to Richard. He has been doing a lot of work in this area recently and there may still be more to come. This change looks simple, but it might interfere with something he is planing to do. Richard is it fine for you to do this change? Fred ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On Aug 14, 2006, at 7:22 AM, Fred Kiefer wrote: In the most recent GSString.m version these methods are there only once. The first one is obsolete anyway, see NSString, where it gets defined as calling the second one. As this in now the only remaining usage of substring_c, we could try to do the inlining ourselves and put the code from the function inside the method. If this alone does not resolve the compilation issue, we could try to rework the actual code. Here the interesting question could be why the similar which calls substring_u works. No, both substring_c and substring_u have the problem Removing the inlining or moving the struct definition out of the function block solves the problem. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Fred,> I would prefer to turn the tone a bit down again. What you wrote may be> regarded as very negative by some.My apologies, if it seemed negative, it wasn't meant that way. I tend tobe direct, so sometimes it comes off that way via email. :)> I don't know about any specific GNUstep feature, we did not implement in> the last year because we actively decided that support for gcc 2.95 was> more important. Until such a case turns up, why not go along with what> Adam and Riccardo suggested: We don't offically support gcc 2.95, but we> try to keep things running in that environment. If we know about issues> and know how to fix them we should do so.My original suggestion was to simply consider it "non-release critical" so that, if something failed to compile in GNUstep under GCC 2.95.x we would would not hold up a release for it. I can see no problem with this, so long as it is a GNUstep-wide policy. If we start making exceptions, as Riccardo suggested for the "core" pieces, it becomes confusing. If you go back to one of his previous posts, you'll see that he suggested *officially* supporting gcc 2.95.x for "core" parts of GS.Official support, to me, implies that we will hold up a release for it.> I remember that from time to time we break compilation for older> compilers by declaring new variable in the middle of the code. Now I> don't see any problem in only declaring variables at the beginning of a> block. Actually we all try to do this, although it old fashioned by now.We all do this because we must support C89, which is what gcc 2.95.xconforms to.> Talking about ancient architecture. Isn't GNustep all about that? We> started off as a step in replacement for NextStep, we just should not> talk too negative about old things :-)Yes, GNUstep started off as a replacement for NeXTSTEP/OpenStep, but ithas grown since then. We have to drop support at some point for things.GCC 2.95.x is quite old, and buggy. I'm simply saying that I think weshould make it non-release critical for all of GNUstep.That being said, as I also said prior, we shouldn't go out of our wayto break things. But, by the same token, we should also not go outof our way to make things work, when and if something does fail.P.S. I am not trying to sound negative, just giving my opinion on thematter. :)Later, GJC--Gregory John Casamento- Original Message From: Fred Kiefer <[EMAIL PROTECTED]>To: Gregory John Casamento <[EMAIL PROTECTED]>Cc: Developer GNUstep Sent: Monday, August 14, 2006 9:04:54 AMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsHi Greg,I would prefer to turn the tone a bit down again. What you wrote may beregarded as very negative by some.I don't know about any specific GNUstep feature, we did not implement inthe last year because we actively decided that support for gcc 2.95 wasmore important. Until such a case turns up, why not go along with whatAdam and Riccardo suggested: We don't offically support gcc 2.95, but wetry to keep things running in that environment. If we know about issuesand know how to fix them we should do so.I remember that from time to time we break compilation for oldercompilers by declaring new variable in the middle of the code. Now Idon't see any problem in only declaring variables at the beginning of ablock. Actually we all try to do this, although it old fashioned by now.Talking about ancient architecture. Isn't GNustep all about that? Westarted off as a step in replacement for NextStep, we just should nottalk too negative about old things :-)CheersFredGregory John Casamento schrieb:> Riccardo,> >> In any case, and I know I think differently than several people here, I>> would prefer to retain gcc 2.95 compatibility at least for the core>> libraries and, if possible, for all "GNUstep supplied" applications. Or,>> at least, the fundamental ones: gorm, project center, system preferences>> and if possible gworkspace.> > So basically all of GNUstep, is what you're saying. This seems to run> counter to what we're discussing. The problem is that there are too> many limitations we must impose on the code in order to maintain that> compatibility, as I described in my previous posting.> >> Of course this does not apply top linux/x86 which almost everyone uses.>> It is just for the 1% of the remaining 1%. But it is one of the reasons>> why I always liked gnustep.> > GNUstep needs to move forward, we can't be held back by the 0.01% of people> who might be using it on an ancient architecture.> > While we should strive to have a wide variety of machines, we shouldn't> go out of our way to make it work on machines which are no longer in common> use.> > --> Gregory John Casamento> > > - Original Me
Re: [Gnustep-cvs] GNUstep Testfarm Results
Adam Fedor schrieb:
> On 2006-08-11 04:27:51 -0600 Fred Kiefer <[EMAIL PROTECTED]> wrote:
>> I agree with all of you that we should not waste to much effort on
>> getting it working, but in this specific case, we have just one method
>> that is failing and we know that up to a certain date this wasn't the
>> case. Perhaps it is not too hard to sort out this method?
>> Adam, which one is this method? And are you willing to test different
>> implementations? BTW which version of gcc 2.95 is installed, 2.95.2 or
>> 2.95.3?
>>
>
> GSString.m compiles if I take out these methods (in two different classes)
>
> - (NSString*) substringFromRange: (NSRange)aRange
> {
> GS_RANGE_CHECK(aRange, _count);
> return substring_c((GSStr)self, aRange);
> }
>
> - (NSString*) substringWithRange: (NSRange)aRange
> {
> GS_RANGE_CHECK(aRange, _count);
> return substring_c((GSStr)self, aRange);
> }
>
> ==
> gcc version 2.95.3 20010315 (release)
>
>
> I haven't really looked into when it changed.
>
In the most recent GSString.m version these methods are there only once.
The first one is obsolete anyway, see NSString, where it gets defined as
calling the second one. As this in now the only remaining usage of
substring_c, we could try to do the inlining ourselves and put the code
from the function inside the method. If this alone does not resolve the
compilation issue, we could try to rework the actual code. Here the
interesting question could be why the similar which calls substring_u works.
Fred
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Hi Greg, I would prefer to turn the tone a bit down again. What you wrote may be regarded as very negative by some. I don't know about any specific GNUstep feature, we did not implement in the last year because we actively decided that support for gcc 2.95 was more important. Until such a case turns up, why not go along with what Adam and Riccardo suggested: We don't offically support gcc 2.95, but we try to keep things running in that environment. If we know about issues and know how to fix them we should do so. I remember that from time to time we break compilation for older compilers by declaring new variable in the middle of the code. Now I don't see any problem in only declaring variables at the beginning of a block. Actually we all try to do this, although it old fashioned by now. Talking about ancient architecture. Isn't GNustep all about that? We started off as a step in replacement for NextStep, we just should not talk too negative about old things :-) Cheers Fred Gregory John Casamento schrieb: > Riccardo, > >> In any case, and I know I think differently than several people here, I >> would prefer to retain gcc 2.95 compatibility at least for the core >> libraries and, if possible, for all "GNUstep supplied" applications. Or, >> at least, the fundamental ones: gorm, project center, system preferences >> and if possible gworkspace. > > So basically all of GNUstep, is what you're saying. This seems to run > counter to what we're discussing. The problem is that there are too > many limitations we must impose on the code in order to maintain that > compatibility, as I described in my previous posting. > >> Of course this does not apply top linux/x86 which almost everyone uses. >> It is just for the 1% of the remaining 1%. But it is one of the reasons >> why I always liked gnustep. > > GNUstep needs to move forward, we can't be held back by the 0.01% of people > who might be using it on an ancient architecture. > > While we should strive to have a wide variety of machines, we shouldn't > go out of our way to make it work on machines which are no longer in common > use. > > -- > Gregory John Casamento > > > - Original Message > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: Fred Kiefer <[EMAIL PROTECTED]>; Developer GNUstep > Sent: Sunday, August 13, 2006 4:26:26 AM > Subject: Re: [Gnustep-cvs] GNUstep Testfarm Results > > Hello, > > On Friday, August 11, 2006, at 12:02 AM, Adam Fedor wrote: > >> I narrowed it down to one method, but that doesn't really help much. On >> the solaris, I'm still using the 2.95 compiler, mostly to check for >> backward compatibility. Perhaps I should just upgrade and start >> deprecating support for gcc 2.95? > > I used to regularly test on gcc 2.95 the core libraries on various > platforms. It is just that lately I was too busy with other important > life tasks. > > In any case, and I know I think differently than several people here, I > would prefer to retain gcc 2.95 compatibility at least for the core > libraries and, if possible, for all "GNUstep supplied" applications. Or, > at least, the fundamental ones: gorm, project center, system preferences > and if possible gworkspace. > > I do not want to enter the eternal gcc 2.9 versus gcc3.x or gcc 4.x > discussion. Mountains of ascii bytes have been spilled about that. I > know 2.95 has many problems. Even Linus Torvalds spoke about the issue. > I just want to remember that newer gcc's are not a good option on more > than one platform (mostly because of C++, not because of obj-c or C > itself) and that gcc guys aren't that happy anymore to fix problems on > arcane platforms as they did on 2.9 series. Furthermore not everybody > may want to upgrade gcc (possibly because the box is managed by others > and 2.95 is the easiest choice) and having more than one compiler > installed (of which some are incomplete, like lacking C++ or in any case > have big api differences like 2.95 and 3.x have) is cumbersome. > > Of course this does not apply top linux/x86 which almost everyone uses. > It is just for the 1% of the remaining 1%. But it is one of the reasons > why I always liked gnustep. > > Regarding solaris and the bug in discussion, I have gcc 3.x installed so > we can check this out too. On Sparc but OpenBSD I have 2.95. > > I will resume testing on more arcane platforms ASAP. > > Have fun, >Riccardo > > > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > http://lists.gnu.org/mailman/listinfo/gnustep-dev > ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Riccardo,> In any case, and I know I think differently than several people here, I > would prefer to retain gcc 2.95 compatibility at least for the core > libraries and, if possible, for all "GNUstep supplied" applications. Or, > at least, the fundamental ones: gorm, project center, system preferences > and if possible gworkspace.So basically all of GNUstep, is what you're saying. This seems to run counter to what we're discussing. The problem is that there are too many limitations we must impose on the code in order to maintain that compatibility, as I described in my previous posting.> Of course this does not apply top linux/x86 which almost everyone uses. > It is just for the 1% of the remaining 1%. But it is one of the reasons > why I always liked gnustep.GNUstep needs to move forward, we can't be held back by the 0.01% of peoplewho might be using it on an ancient architecture.While we should strive to have a wide variety of machines, we shouldn'tgo out of our way to make it work on machines which are no longer in commonuse. --Gregory John Casamento- Original Message From: [EMAIL PROTECTED]To: [EMAIL PROTECTED]Cc: Fred Kiefer <[EMAIL PROTECTED]>; Developer GNUstep Sent: Sunday, August 13, 2006 4:26:26 AMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsHello,On Friday, August 11, 2006, at 12:02 AM, Adam Fedor wrote:> I narrowed it down to one method, but that doesn't really help much. On > the solaris, I'm still using the 2.95 compiler, mostly to check for > backward compatibility. Perhaps I should just upgrade and start > deprecating support for gcc 2.95?I used to regularly test on gcc 2.95 the core libraries on various platforms. It is just that lately I was too busy with other important life tasks.In any case, and I know I think differently than several people here, I would prefer to retain gcc 2.95 compatibility at least for the core libraries and, if possible, for all "GNUstep supplied" applications. Or, at least, the fundamental ones: gorm, project center, system preferences and if possible gworkspace.I do not want to enter the eternal gcc 2.9 versus gcc3.x or gcc 4.x discussion. Mountains of ascii bytes have been spilled about that. I know 2.95 has many problems. Even Linus Torvalds spoke about the issue. I just want to remember that newer gcc's are not a good option on more than one platform (mostly because of C++, not because of obj-c or C itself) and that gcc guys aren't that happy anymore to fix problems on arcane platforms as they did on 2.9 series. Furthermore not everybody may want to upgrade gcc (possibly because the box is managed by others and 2.95 is the easiest choice) and having more than one compiler installed (of which some are incomplete, like lacking C++ or in any case have big api differences like 2.95 and 3.x have) is cumbersome.Of course this does not apply top linux/x86 which almost everyone uses. It is just for the 1% of the remaining 1%. But it is one of the reasons why I always liked gnustep.Regarding solaris and the bug in discussion, I have gcc 3.x installed so we can check this out too. On Sparc but OpenBSD I have 2.95.I will resume testing on more arcane platforms ASAP.Have fun, Riccardo___Gnustep-dev mailing listGnustep-dev@gnu.orghttp://lists.gnu.org/mailman/listinfo/gnustep-dev___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Hello, On Friday, August 11, 2006, at 12:02 AM, Adam Fedor wrote: I narrowed it down to one method, but that doesn't really help much. On the solaris, I'm still using the 2.95 compiler, mostly to check for backward compatibility. Perhaps I should just upgrade and start deprecating support for gcc 2.95? I used to regularly test on gcc 2.95 the core libraries on various platforms. It is just that lately I was too busy with other important life tasks. In any case, and I know I think differently than several people here, I would prefer to retain gcc 2.95 compatibility at least for the core libraries and, if possible, for all "GNUstep supplied" applications. Or, at least, the fundamental ones: gorm, project center, system preferences and if possible gworkspace. I do not want to enter the eternal gcc 2.9 versus gcc3.x or gcc 4.x discussion. Mountains of ascii bytes have been spilled about that. I know 2.95 has many problems. Even Linus Torvalds spoke about the issue. I just want to remember that newer gcc's are not a good option on more than one platform (mostly because of C++, not because of obj-c or C itself) and that gcc guys aren't that happy anymore to fix problems on arcane platforms as they did on 2.9 series. Furthermore not everybody may want to upgrade gcc (possibly because the box is managed by others and 2.95 is the easiest choice) and having more than one compiler installed (of which some are incomplete, like lacking C++ or in any case have big api differences like 2.95 and 3.x have) is cumbersome. Of course this does not apply top linux/x86 which almost everyone uses. It is just for the 1% of the remaining 1%. But it is one of the reasons why I always liked gnustep. Regarding solaris and the bug in discussion, I have gcc 3.x installed so we can check this out too. On Sparc but OpenBSD I have 2.95. I will resume testing on more arcane platforms ASAP. Have fun, Riccardo ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
GCC 2.95 deprecation (Was Re: [Gnustep-cvs] GNUstep Testfarm Results)
Riccardo,I'm not sure if I got that email, what "core" stuff are you referring to? Please send it to the list again.In the meantime, allow me to be clear on this: GCC 2.95.x is an ancient version of the compiler which doesn't support modern conventions in C99 as well such things as namespaces, certain types of foward declarations, -fconstant-string, and it also has problems with spin-lock (mutex locking) and etc. It's silly for us to officially support it anywhere.Also, any architecture which doesn't have GCC 3 support can and probably should be dropped as well. The non-release critical policy, in this case, needs to cover all of GNUstep, not just "core pieces".Later, GJC--Gregory John Casamento- Original Message From: Riccardo <[EMAIL PROTECTED]>To: Fred Kiefer <[EMAIL PROTECTED]>Cc: Developer GNUstep Sent: Sunday, August 13, 2006 4:29:04 AMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsHello,On Friday, August 11, 2006, at 12:27 PM, Fred Kiefer wrote:> I am not that sure about this. gcc 2.95 is a very old version, but it> still has its own merits. It was the most popular release before the> re-architecture and in many cases it is still faster than the later gcc> releases. It also is in some cases the only version of gcc at hand. (I> had to learn this when trying to do cross compilation of GNUstep)I agree here. Sensing the hint of Gregory I would go as far as considering 2.95 bugs non-critical, but trying not to actively break 2.95 and officially supporting it in the core stuff I mentioned in the previous email.Cheers, R___Gnustep-dev mailing listGnustep-dev@gnu.orghttp://lists.gnu.org/mailman/listinfo/gnustep-dev___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On 2006-08-11 04:27:51 -0600 Fred Kiefer <[EMAIL PROTECTED]> wrote:
I agree with all of you that we should not waste to much effort on
getting it working, but in this specific case, we have just one method
that is failing and we know that up to a certain date this wasn't the
case. Perhaps it is not too hard to sort out this method?
Adam, which one is this method? And are you willing to test different
implementations? BTW which version of gcc 2.95 is installed, 2.95.2 or
2.95.3?
GSString.m compiles if I take out these methods (in two different
classes)
- (NSString*) substringFromRange: (NSRange)aRange
{
GS_RANGE_CHECK(aRange, _count);
return substring_c((GSStr)self, aRange);
}
- (NSString*) substringWithRange: (NSRange)aRange
{
GS_RANGE_CHECK(aRange, _count);
return substring_c((GSStr)self, aRange);
}
==
gcc version 2.95.3 20010315 (release)
I haven't really looked into when it changed.
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On 2006-08-13 02:29:04 -0600 Riccardo <[EMAIL PROTECTED]> wrote: Hello, On Friday, August 11, 2006, at 12:27 PM, Fred Kiefer wrote: I am not that sure about this. gcc 2.95 is a very old version, but it still has its own merits. It was the most popular release before the re-architecture and in many cases it is still faster than the later gcc releases. It also is in some cases the only version of gcc at hand. (I had to learn this when trying to do cross compilation of GNUstep) I agree here. Sensing the hint of Gregory I would go as far as considering 2.95 bugs non-critical, but trying not to actively break 2.95 and officially supporting it in the core stuff I mentioned in the previous email. I think that is our plan. We'll try to fix anything we can, but not delay a release if something is broken on 2.95. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GCC 2.95.x deprecation (was Re: [Gnustep-cvs] GNUstep Testfarm Results)
Hey, On Saturday, August 12, 2006, at 09:18 PM, Gregory John Casamento wrote: I believe we've come to the conclusion to deprecate gcc 2.95.x support for GNUstep. To state it succintly, GNUstep shall support only gcc 3.x and greater. Are there any objections, before this becomes official? yes, as I wrote in the previous emails. Sorry if I catched up emails out of sync, but I had some days of vacation. -R ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Hello, On Friday, August 11, 2006, at 12:27 PM, Fred Kiefer wrote: I am not that sure about this. gcc 2.95 is a very old version, but it still has its own merits. It was the most popular release before the re-architecture and in many cases it is still faster than the later gcc releases. It also is in some cases the only version of gcc at hand. (I had to learn this when trying to do cross compilation of GNUstep) I agree here. Sensing the hint of Gregory I would go as far as considering 2.95 bugs non-critical, but trying not to actively break 2.95 and officially supporting it in the core stuff I mentioned in the previous email. Cheers, R ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
GCC 2.95.x deprecation (was Re: [Gnustep-cvs] GNUstep Testfarm Results)
All,I believe we've come to the conclusion to deprecate gcc 2.95.x support for GNUstep. To state it succintly, GNUstep shall support only gcc 3.x and greater.Are there any objections, before this becomes official?Later, GJC--Gregory John Casamento- Original Message From: Helge Hess <[EMAIL PROTECTED]>To: Developer GNUstep Sent: Friday, August 11, 2006 7:59:50 PMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsOn Aug 11, 2006, at 12:27, Fred Kiefer wrote:> and in many cases it is still faster than the later gcc> releases.I don't think thats true anymore for gcc4 and up. Not to mention PCH ...libFoundation recently deprecated 2.95 support because those do not support -fconstant-string-class.Greets, Helge-- Helge Hesshttp://docs.opengroupware.org/Members/helge/___Gnustep-dev mailing listGnustep-dev@gnu.orghttp://lists.gnu.org/mailman/listinfo/gnustep-dev___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On Aug 11, 2006, at 12:27, Fred Kiefer wrote: and in many cases it is still faster than the later gcc releases. I don't think thats true anymore for gcc4 and up. Not to mention PCH ... libFoundation recently deprecated 2.95 support because those do not support -fconstant-string-class. Greets, Helge -- Helge Hess http://docs.opengroupware.org/Members/helge/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
I am not that sure about this. gcc 2.95 is a very old version, but it still has its own merits. It was the most popular release before the re-architecture and in many cases it is still faster than the later gcc releases. It also is in some cases the only version of gcc at hand. (I had to learn this when trying to do cross compilation of GNUstep) I agree with all of you that we should not waste to much effort on getting it working, but in this specific case, we have just one method that is failing and we know that up to a certain date this wasn't the case. Perhaps it is not too hard to sort out this method? Adam, which one is this method? And are you willing to test different implementations? BTW which version of gcc 2.95 is installed, 2.95.2 or 2.95.3? Fred Gregory John Casamento schrieb: > Allow me to clarify, before anyone asks, we should only support gcc 3.0 > and greater. > > -- > Gregory John Casamento > > > - Original Message > From: Gregory John Casamento <[EMAIL PROTECTED]> > To: Andrew Ruder <[EMAIL PROTECTED]>; Developer GNUstep > Sent: Friday, August 11, 2006 1:14:32 AM > Subject: Re: [Gnustep-cvs] GNUstep Testfarm Results > > Adam/Andy, > > Just to add my $0.02... > > The gcc-2.95 compiler is quite old, we should consider problems that > arise because of issues relating to gcc 2.95 to be non-release critical > for GNUstep. > > We shouldn't go out of our way to break GNUstep for gcc 2.95, but we > should not bend over backwards to fix issues related to it either. > > Later, GJC > -- > Gregory John Casamento > > > - Original Message > From: Andrew Ruder <[EMAIL PROTECTED]> > To: Developer GNUstep > Sent: Thursday, August 10, 2006 8:41:53 PM > Subject: Re: [Gnustep-cvs] GNUstep Testfarm Results > > On Thu, Aug 10, 2006 at 04:02:01PM -0600, Adam Fedor wrote: >> I narrowed it down to one method, but that doesn't really help much. >> On the solaris, I'm still using the 2.95 compiler, mostly to check for >> backward compatibility. Perhaps I should just upgrade and start >> deprecating support for gcc 2.95? > > The way I see it, gcc 3.0 was released on June 18, 2001. This is more > than 5 years ago. In the technology world, that is a very long, long > time. If there's really platforms that don't have gcc 3 or higher, > maybe it is just time for those platforms to be depracated (or they can > use an older version of gnustep). ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Allow me to clarify, before anyone asks, we should only support gcc 3.0 and greater. --Gregory John Casamento- Original Message From: Gregory John Casamento <[EMAIL PROTECTED]>To: Andrew Ruder <[EMAIL PROTECTED]>; Developer GNUstep Sent: Friday, August 11, 2006 1:14:32 AMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsAdam/Andy,Just to add my $0.02...The gcc-2.95 compiler is quite old, we should consider problems that arise because of issues relating to gcc 2.95 to be non-release critical for GNUstep. We shouldn't go out of our way to break GNUstep for gcc 2.95, but we should not bend over backwards to fix issues related to it either.Later, GJC--Gregory John Casamento- Original Message From: Andrew Ruder <[EMAIL PROTECTED]>To: Developer GNUstep Sent: Thursday, August 10, 2006 8:41:53 PMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsOn Thu, Aug 10, 2006 at 04:02:01PM -0600, Adam Fedor wrote:> I narrowed it down to one method, but that doesn't really help much. > On the solaris, I'm still using the 2.95 compiler, mostly to check for > backward compatibility. Perhaps I should just upgrade and start > deprecating support for gcc 2.95?The way I see it, gcc 3.0 was released on June 18, 2001. This is morethan 5 years ago. In the technology world, that is a very long, longtime. If there's really platforms that don't have gcc 3 or higher,maybe it is just time for those platforms to be depracated (or they canuse an older version of gnustep).Just my two cents,Andy-- Andrew Ruder <[EMAIL PROTECTED]>http://www.aeruder.net___Gnustep-dev mailing listGnustep-dev@gnu.orghttp://lists.gnu.org/mailman/listinfo/gnustep-dev___Gnustep-dev mailing listGnustep-dev@gnu.orghttp://lists.gnu.org/mailman/listinfo/gnustep-dev___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
Adam/Andy,Just to add my $0.02...The gcc-2.95 compiler is quite old, we should consider problems that arise because of issues relating to gcc 2.95 to be non-release critical for GNUstep. We shouldn't go out of our way to break GNUstep for gcc 2.95, but we should not bend over backwards to fix issues related to it either.Later, GJC--Gregory John Casamento- Original Message From: Andrew Ruder <[EMAIL PROTECTED]>To: Developer GNUstep Sent: Thursday, August 10, 2006 8:41:53 PMSubject: Re: [Gnustep-cvs] GNUstep Testfarm ResultsOn Thu, Aug 10, 2006 at 04:02:01PM -0600, Adam Fedor wrote:> I narrowed it down to one method, but that doesn't really help much. > On the solaris, I'm still using the 2.95 compiler, mostly to check for > backward compatibility. Perhaps I should just upgrade and start > deprecating support for gcc 2.95?The way I see it, gcc 3.0 was released on June 18, 2001. This is morethan 5 years ago. In the technology world, that is a very long, longtime. If there's really platforms that don't have gcc 3 or higher,maybe it is just time for those platforms to be depracated (or they canuse an older version of gnustep).Just my two cents,Andy-- Andrew Ruder <[EMAIL PROTECTED]>http://www.aeruder.net___Gnustep-dev mailing listGnustep-dev@gnu.orghttp://lists.gnu.org/mailman/listinfo/gnustep-dev___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On Thu, Aug 10, 2006 at 04:02:01PM -0600, Adam Fedor wrote: > I narrowed it down to one method, but that doesn't really help much. > On the solaris, I'm still using the 2.95 compiler, mostly to check for > backward compatibility. Perhaps I should just upgrade and start > deprecating support for gcc 2.95? The way I see it, gcc 3.0 was released on June 18, 2001. This is more than 5 years ago. In the technology world, that is a very long, long time. If there's really platforms that don't have gcc 3 or higher, maybe it is just time for those platforms to be depracated (or they can use an older version of gnustep). Just my two cents, Andy -- Andrew Ruder <[EMAIL PROTECTED]> http://www.aeruder.net ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] GNUstep Testfarm Results
On 2006-08-10 15:09:50 -0600 Fred Kiefer <[EMAIL PROTECTED]> wrote: Adam Fedor schrieb: Test results for GNUstep as of Thu Aug 10 06:34:25 EDT 2006 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-netbsdelf3.0 Thu Aug 10 03:58:53 CEST 2006 Fail Compile i686-pc-linux-gnu Wed Aug 9 22:24:18 CEST 2006 Success Compile powerpc-apple-darwin7.9.0 Thu Aug 10 03:27:47 MDT 2006 Fail Compile sparc-sun-solaris2.7 Thu Aug 10 01:58:16 EDT 2006 For three months we have been getting this notice that GNustep no longer passes the tests for the solaris platform. Did anybody ever look into what is causing the problem? I narrowed it down to one method, but that doesn't really help much. On the solaris, I'm still using the 2.95 compiler, mostly to check for backward compatibility. Perhaps I should just upgrade and start deprecating support for gcc 2.95? ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
[Gnustep-cvs] GNUstep Testfarm Results (fwd)
FYI, sparc fails with the latest change in RTFConsumer because a variable is declared in the middle of a block. Currently, we're still maintaining compatibility with gcc 2.95, which does not allow that. -- Forwarded message -- Date: 2006-05-12 04:34:17 -0600 From: Adam Fedor <[EMAIL PROTECTED]> Subject: [Gnustep-cvs] GNUstep Testfarm Results Test results for GNUstep as of Fri May 12 06:34:17 EDT 2006 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-netbsdelf3.0 Fri May 12 03:58:43 CEST 2006 Fail Compile i686-pc-linux-gnu Fri May 12 00:07:05 CEST 2006 Success Compile powerpc-apple-darwin7.9.0 Fri May 12 03:29:32 MDT 2006 Fail Compile sparc-sun-solaris2.7 Fri May 12 02:09:03 EDT 2006 == Making all for bundle RTFConverter... Compiling file rtfGrammer.tab.c ... Compiling file rtfScanner.c ... Compiling file RTFConsumer.m ... RTFConsumer.m: In function `-[RTFDConsumer appendImage:]': RTFConsumer.m:432: parse error before `*' RTFConsumer.m:440: `str' undeclared (first use in this function) RTFConsumer.m:440: (Each undeclared identifier is reported only once RTFConsumer.m:440: for each function it appears in.) RTFConsumer.m:440: `attributes' undeclared (first use in this function) RTFConsumer.m: In function `GSRTFNeXTGraphic': RTFConsumer.m:1096: warning: `RTFDConsumer' does not respond to `appendImage:' make[3]: *** [shared_obj/RTFConsumer.o] Error 1 make[2]: *** [RTFConverter.all.bundle.variables] Error 2 make[2]: Leaving directory `/raid0/ps0/fedor/src/gstep/testing/core/gui/TextConverters/RTF' make[1]: *** [internal-all] Error 2 make[1]: Leaving directory `/raid0/ps0/fedor/src/gstep/testing/core/gui/TextConverters' make: *** [internal-all] Error 2 ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Jan 29 06:34:12 EST 2006 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-netbsdelf3.0 Sun Jan 29 03:58:36 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sun Jan 29 03:27:11 MST 2006 Success Compile sparc-sun-solaris2.7 Sun Jan 29 02:10:48 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Jan 28 06:34:15 EST 2006 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-netbsdelf3.0 Sat Jan 28 03:58:34 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sat Jan 28 03:26:18 MST 2006 Success Compile sparc-sun-solaris2.7 Sat Jan 28 02:09:50 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Jan 27 06:34:16 EST 2006 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-netbsdelf3.0 Fri Jan 27 03:58:37 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Fri Jan 27 03:26:12 MST 2006 Success Compile sparc-sun-solaris2.7 Fri Jan 27 02:08:00 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Jan 26 06:34:18 EST 2006 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-netbsdelf3.0 Thu Jan 26 03:58:32 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Thu Jan 26 03:28:06 MST 2006 Success Compile sparc-sun-solaris2.7 Thu Jan 26 02:07:54 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Jan 25 06:34:18 EST 2006 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-netbsdelf3.0 Wed Jan 25 03:58:31 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Wed Jan 25 03:26:19 MST 2006 Success Compile sparc-sun-solaris2.7 Wed Jan 25 02:07:57 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Jan 24 06:34:16 EST 2006 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-netbsdelf3.0 Tue Jan 24 03:58:33 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Tue Jan 24 03:30:18 MST 2006 Success Compile sparc-sun-solaris2.7 Tue Jan 24 02:07:57 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Jan 23 06:34:13 EST 2006 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-netbsdelf3.0 Mon Jan 23 03:58:31 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Mon Jan 23 03:24:38 MST 2006 Success Compile sparc-sun-solaris2.7 Mon Jan 23 02:08:49 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Jan 22 06:34:13 EST 2006 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-netbsdelf3.0 Sun Jan 22 03:58:20 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sun Jan 22 03:24:29 MST 2006 Success Compile sparc-sun-solaris2.7 Sun Jan 22 02:10:45 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Jan 21 06:34:20 EST 2006 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-netbsdelf3.0 Sat Jan 21 03:58:33 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sat Jan 21 03:26:54 MST 2006 Success Compile sparc-sun-solaris2.7 Sat Jan 21 02:07:57 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Jan 20 06:34:17 EST 2006 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-netbsdelf3.0 Fri Jan 20 03:58:36 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Fri Jan 20 03:31:14 MST 2006 Success Compile sparc-sun-solaris2.7 Fri Jan 20 02:07:49 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Jan 19 06:34:18 EST 2006 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-netbsdelf3.0 Thu Jan 19 03:58:37 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Thu Jan 19 03:26:42 MST 2006 Success Compile sparc-sun-solaris2.7 Thu Jan 19 02:08:02 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Jan 18 06:34:16 EST 2006 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-netbsdelf3.0 Wed Jan 18 03:58:26 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Wed Jan 18 03:25:51 MST 2006 Success Compile sparc-sun-solaris2.7 Wed Jan 18 02:08:01 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Jan 17 06:34:21 EST 2006 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-netbsdelf3.0 Tue Jan 17 03:58:33 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Tue Jan 17 03:22:10 MST 2006 Success Compile sparc-sun-solaris2.7 Tue Jan 17 02:10:50 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Jan 16 06:34:12 EST 2006 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-netbsdelf3.0 Mon Jan 16 03:58:20 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Mon Jan 16 03:21:29 MST 2006 Success Compile sparc-sun-solaris2.7 Mon Jan 16 02:09:20 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Jan 15 06:34:20 EST 2006 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-netbsdelf3.0 Sun Jan 15 03:58:35 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sun Jan 15 03:22:22 MST 2006 Success Compile sparc-sun-solaris2.7 Sun Jan 15 02:12:29 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Jan 14 06:34:16 EST 2006 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-netbsdelf3.0 Sat Jan 14 03:58:29 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sat Jan 14 03:32:48 MST 2006 Success Compile sparc-sun-solaris2.7 Sat Jan 14 02:08:30 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Jan 13 06:34:12 EST 2006 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-netbsdelf3.0 Fri Jan 13 03:58:32 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Fri Jan 13 03:26:21 MST 2006 Success Compile sparc-sun-solaris2.7 Fri Jan 13 02:08:34 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Jan 12 06:34:15 EST 2006 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-netbsdelf3.0 Thu Jan 12 03:58:30 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Thu Jan 12 03:30:36 MST 2006 Success Compile sparc-sun-solaris2.7 Thu Jan 12 02:11:22 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Jan 11 06:34:14 EST 2006 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-netbsdelf3.0 Wed Jan 11 03:58:30 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Wed Jan 11 03:29:50 MST 2006 Success Compile sparc-sun-solaris2.7 Wed Jan 11 02:09:44 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Jan 10 06:34:12 EST 2006 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-netbsdelf3.0 Tue Jan 10 03:58:34 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Tue Jan 10 03:26:25 MST 2006 Success Compile sparc-sun-solaris2.7 Tue Jan 10 02:08:31 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Jan 9 06:34:12 EST 2006 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-netbsdelf3.0 Mon Jan 9 03:58:37 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Mon Jan 9 03:32:07 MST 2006 Success Compile sparc-sun-solaris2.7 Mon Jan 9 02:08:08 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Jan 8 06:34:15 EST 2006 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-netbsdelf3.0 Sun Jan 8 03:58:27 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sun Jan 8 03:31:54 MST 2006 Success Compile sparc-sun-solaris2.7 Sun Jan 8 02:12:39 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Jan 7 06:34:14 EST 2006 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-netbsdelf3.0 Sat Jan 7 03:58:29 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sat Jan 7 03:31:18 MST 2006 Success Compile sparc-sun-solaris2.7 Sat Jan 7 02:08:01 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Jan 6 06:34:16 EST 2006 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-netbsdelf3.0 Fri Jan 6 03:58:28 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Fri Jan 6 03:42:21 MST 2006 Success Compile sparc-sun-solaris2.7 Fri Jan 6 02:08:08 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Jan 5 06:34:20 EST 2006 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-netbsdelf3.0 Thu Jan 5 03:58:29 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Thu Jan 5 03:25:03 MST 2006 Success Compile sparc-sun-solaris2.7 Thu Jan 5 02:08:08 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Jan 4 06:34:15 EST 2006 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-netbsdelf3.0 Wed Jan 4 03:58:28 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Wed Jan 4 03:28:17 MST 2006 Success Compile sparc-sun-solaris2.7 Wed Jan 4 02:08:01 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Jan 3 06:34:17 EST 2006 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-netbsdelf3.0 Tue Jan 3 03:58:26 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Tue Jan 3 03:24:37 MST 2006 Success Compile sparc-sun-solaris2.7 Tue Jan 3 02:07:52 EST 2006 Fail Compile sparc64-unknown-netbsd3.0 Tue Jan 3 00:38:21 CET 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Jan 2 06:34:19 EST 2006 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-netbsdelf3.0 Mon Jan 2 03:58:18 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Mon Jan 2 03:24:41 MST 2006 Success Compile sparc-sun-solaris2.7 Mon Jan 2 02:08:30 EST 2006 Fail Compile sparc64-unknown-netbsd3.0 Sun Jan 1 19:29:23 CET 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Jan 1 06:34:13 EST 2006 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-netbsdelf3.0 Sun Jan 1 03:58:10 CET 2006 Success Compile powerpc-apple-darwin7.9.0 Sun Jan 1 03:22:41 MST 2006 Success Compile sparc-sun-solaris2.7 Sun Jan 1 02:10:17 EST 2006
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Dec 31 06:34:16 EST 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-netbsdelf3.0 Sat Dec 31 03:58:12 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Dec 31 03:22:26 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Dec 31 02:07:55 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Dec 30 06:34:13 EST 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.1.0. Fri Dec 30 03:58:18 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Dec 30 03:22:19 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Dec 30 02:07:57 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Dec 29 06:34:14 EST 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.1.0. Thu Dec 29 03:58:16 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Dec 29 03:22:16 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Dec 29 02:07:55 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Dec 28 06:34:16 EST 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.1.0. Wed Dec 28 03:58:17 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Dec 28 03:23:26 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Dec 28 02:07:53 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Dec 27 06:34:16 EST 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.1.0. Tue Dec 27 03:58:41 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Dec 27 03:22:47 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Dec 27 02:07:53 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Dec 26 06:34:13 EST 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.1.0. Mon Dec 26 03:58:16 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Dec 26 03:24:16 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Dec 26 02:10:12 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Dec 25 06:34:16 EST 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.1.0. Sun Dec 25 03:58:17 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Dec 25 03:22:43 MST 2005 Success Compile sparc-sun-solaris2.7 Sun Dec 25 02:10:06 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Dec 24 06:34:12 EST 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.1.0. Sat Dec 24 03:58:05 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Dec 24 03:27:33 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Dec 24 02:07:53 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Dec 23 06:34:17 EST 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.1.0. Fri Dec 23 03:58:05 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Dec 23 03:28:56 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Dec 23 02:08:33 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Dec 22 06:34:13 EST 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.1.0. Thu Dec 22 03:58:14 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Dec 22 03:29:01 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Dec 22 02:07:51 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Dec 21 06:34:13 EST 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.1.0. Wed Dec 21 03:58:15 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Dec 21 03:27:24 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Dec 21 02:09:47 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Dec 20 06:34:24 EST 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.1.0. Tue Dec 20 03:58:20 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Dec 20 03:26:03 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Dec 20 02:09:21 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Dec 19 06:34:16 EST 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.1.0. Mon Dec 19 03:58:15 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Dec 19 03:23:56 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Dec 19 02:07:48 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Dec 18 06:34:14 EST 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.1.0. Sun Dec 18 03:58:15 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Dec 18 03:22:34 MST 2005 Success Compile sparc-sun-solaris2.7 Sun Dec 18 02:10:34 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Dec 17 06:34:12 EST 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.1.0. Sat Dec 17 03:59:58 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Dec 17 03:22:54 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Dec 17 02:08:01 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Dec 16 06:34:17 EST 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.1.0. Fri Dec 16 04:00:08 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Dec 16 03:25:04 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Dec 16 02:07:52 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Dec 15 06:34:22 EST 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.1.0. Thu Dec 15 03:59:17 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Dec 15 03:25:01 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Dec 15 02:07:54 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Dec 14 06:34:38 EST 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.1.0. Wed Dec 14 03:59:12 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Dec 14 03:22:49 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Dec 14 02:08:26 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Dec 13 06:34:18 EST 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.1.0. Tue Dec 13 03:59:12 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Dec 13 03:22:23 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Dec 13 02:07:58 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Dec 12 06:34:14 EST 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.1.0. Mon Dec 12 03:59:07 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Dec 12 03:24:00 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Dec 12 02:08:53 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Dec 11 06:34:13 EST 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.1.0. Sun Dec 11 03:59:21 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Dec 11 03:22:36 MST 2005 Success Compile sparc-sun-solaris2.7 Sun Dec 11 02:13:59 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Dec 10 06:34:13 EST 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.1.0. Sat Dec 10 03:59:26 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Dec 10 03:26:24 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Dec 10 02:08:40 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Dec 9 06:34:13 EST 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.1.0. Fri Dec 9 03:58:49 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Dec 9 03:24:06 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Dec 9 02:08:13 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Dec 8 06:34:26 EST 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.1.0. Thu Dec 8 03:58:31 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Dec 8 03:21:56 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Dec 8 02:08:22 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Dec 7 06:34:14 EST 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.1.0. Wed Dec 7 03:58:14 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Dec 7 03:21:54 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Dec 7 02:08:06 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Dec 6 06:34:14 EST 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.1.0. Tue Dec 6 03:58:30 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Dec 6 03:21:49 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Dec 6 02:08:47 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Dec 5 06:34:16 EST 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.1.0. Mon Dec 5 03:58:18 CET 2005 Fail Compile powerpc-apple-darwin7.9.0 Mon Dec 5 03:02:20 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Dec 5 02:08:58 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Dec 4 06:34:14 EST 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.1.0. Sun Dec 4 03:58:21 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Dec 4 03:21:51 MST 2005 Success Compile sparc-sun-solaris2.7 Sun Dec 4 02:10:28 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Dec 3 06:34:14 EST 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.1.0. Sat Dec 3 03:58:16 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Dec 3 03:21:58 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Dec 3 02:08:16 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Dec 2 06:34:15 EST 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.1.0. Fri Dec 2 03:58:23 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Dec 2 03:21:58 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Dec 2 02:08:25 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Dec 1 06:34:26 EST 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.1.0. Thu Dec 1 03:58:23 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Dec 1 03:21:46 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Dec 1 02:08:05 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Nov 30 06:34:14 EST 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.1.0. Wed Nov 30 03:58:28 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Nov 30 03:21:37 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Nov 30 02:07:58 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Nov 29 06:34:13 EST 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.1.0. Tue Nov 29 03:58:28 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Nov 29 03:22:05 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Nov 29 02:10:38 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Nov 28 06:34:13 EST 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.1.0. Mon Nov 28 03:58:26 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Nov 28 03:25:46 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Nov 28 02:08:34 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Nov 27 06:34:13 EST 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.1.0. Sun Nov 27 03:58:31 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Nov 27 03:27:35 MST 2005 Success Compile sparc-sun-solaris2.7 Sun Nov 27 02:09:50 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Nov 26 06:34:25 EST 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.1.0. Sat Nov 26 03:58:21 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Nov 26 03:27:43 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Nov 26 02:08:03 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Nov 25 06:34:15 EST 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.1.0. Fri Nov 25 03:58:34 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Nov 25 03:26:38 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Nov 25 02:07:53 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Nov 24 06:34:16 EST 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.1.0. Thu Nov 24 03:58:41 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Nov 24 03:26:20 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Nov 24 02:08:18 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Nov 23 06:34:14 EST 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.1.0. Wed Nov 23 03:58:28 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Nov 23 03:28:22 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Nov 23 02:08:15 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Nov 22 06:34:29 EST 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.1.0. Tue Nov 22 03:58:20 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Nov 22 03:44:32 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Nov 22 02:09:42 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Nov 21 06:34:28 EST 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.1.0. Mon Nov 21 03:58:37 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Nov 21 03:25:57 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Nov 21 02:09:15 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Nov 20 06:34:14 EST 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.1.0. Sun Nov 20 03:58:31 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Nov 20 03:27:24 MST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sat Nov 19 06:34:17 EST 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.1.0. Sat Nov 19 03:58:28 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sat Nov 19 03:27:49 MST 2005 Success Compile sparc-sun-solaris2.7 Sat Nov 19 02:08:54 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Fri Nov 18 06:34:13 EST 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.1.0. Fri Nov 18 03:58:22 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Fri Nov 18 03:27:18 MST 2005 Success Compile sparc-sun-solaris2.7 Fri Nov 18 02:08:27 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Thu Nov 17 06:34:16 EST 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.1.0. Thu Nov 17 03:58:36 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Thu Nov 17 03:24:02 MST 2005 Success Compile sparc-sun-solaris2.7 Thu Nov 17 02:09:47 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Wed Nov 16 06:34:17 EST 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.1.0. Wed Nov 16 03:58:32 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Wed Nov 16 03:24:16 MST 2005 Success Compile sparc-sun-solaris2.7 Wed Nov 16 02:08:57 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Tue Nov 15 06:34:12 EST 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.1.0. Tue Nov 15 03:59:26 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Tue Nov 15 03:27:54 MST 2005 Success Compile sparc-sun-solaris2.7 Tue Nov 15 02:09:18 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Mon Nov 14 06:34:18 EST 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.1.0. Mon Nov 14 03:58:46 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Mon Nov 14 03:26:25 MST 2005 Success Compile sparc-sun-solaris2.7 Mon Nov 14 02:09:38 EST 2005
[Gnustep-cvs] GNUstep Testfarm Results
Test results for GNUstep as of Sun Nov 13 06:34:22 EST 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.1.0. Sun Nov 13 03:59:08 CET 2005 Success Compile powerpc-apple-darwin7.9.0 Sun Nov 13 03:25:32 MST 2005 Success Compile sparc-sun-solaris2.7 Sun Nov 13 02:10:49 EST 2005
