Selon Pete French <[EMAIL PROTECTED]>: > > thing, I must always use 'cvs co' instead of 'cvs update'. If I use 'cvs > > update', my Headers/Foundation directory is almost empty (I can't remember > > That does not sound good. What happens if you delete everything, do a cvs co > from scratch and then a cvs update ? Does that work as expected ? What > is your CVS string ? Well I've done a 'cvs co' few weeks ago and I do cvs update from that. I can't tell you what is my CVS string because I'm at work and by the way, don't have my computer with me.
> Maybe you have a corrupt 4.8 installation and cvs isnt working properly ? ?? I stay updated with cvsup for stable and cvs works fine with GNUMail. > > Usually, I make a 'gmake distclean && ./configure && gmake install" > > ....dont you need a 'CC=gcc33 ./configure' there ? I do it by hand in > each directory - and after I install 'make' I *always* resource the shell > script as I ahve had big proiblems in the past by not doing this. I prefer 'setenv CC "gcc33 -fno-strict-aliasing' and I make 'source ...' for every directory except 'make' > > I am using gcc 3.3 from ports. > > I never got 33 to work so I went back to using 32. But it does sound like > the problem is elsewhere - i.e. getting corrupt source from CVS. It worked perfectly in the past. Well I'll do a complete 'cvs co' tonight for core (with my dial-up modem :-(). > -bat. > _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
