Re: gperf broken - breaks buildworld
David W. Chapman Jr. wrote: > On Wed, May 22, 2002 at 02:37:34PM -0400, Callum M. Duncan wrote: > >>Ok you've got me all thinking... >> > > Maybe you just cvsup'd this machine in the middle of a commit, if it > exists a few hours after you originally cvsup'd, then I would erase > gperf from /usr/src and try to recvsup. After your problem, I cvsuped RELENG_4 and did everything but an installworld. Kent > > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
subscribe
subscribe Todd Florman Northrop Grumman SBIRS Sustainment Depot Hardware Engineer 6304 Spine RD Boulder, CO 80301 (303) 581-6341 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: xterm title sequence affects icon name too
On Thu, 23 May 2002 12:12, Hanspeter Roth wrote: > On May 20 at 16:29, Hanspeter Roth spoke: > > Some versions (configurations?) of Xterm can be sent 2;...\007 > > to change the title only. And 0;...\007 is used to change both > > the title and icon name. > > But in certain installations (configurations?) 2;...\007 which > > is expected to change only the title also changes the icon name. > > What does it depend on? Are there different versions of Xterms? > > This seems to be an issue of the window manager Icewm 1.0.8, rather > than of xterm. > Under an alternative window manager Twm xterm behaves as expected. > I'm using Icewm 1.0.8. An 1.0.7 installation behaves also as > expected. You might want to bring this up with the developers of icewm then, since this dosn't relate to FreeBSD-stable. - James -- James Pole - www.jamespole.cjb.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gperf broken - breaks buildworld
On Wed, May 22, 2002 at 02:37:34PM -0400, Callum M. Duncan wrote: > Ok you've got me all thinking... Maybe you just cvsup'd this machine in the middle of a commit, if it exists a few hours after you originally cvsup'd, then I would erase gperf from /usr/src and try to recvsup. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gperf broken - breaks buildworld
Ok you've got me all thinking... Here is my cvsup cronjob and cvsupfile: /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile.src FILE: cvsupfile.src --->snip<--- *default host=cvsup.freebsd.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default compress src-all --->snip<--- All of my machines use this. All of my rebuilds before have had kernels that read 4.5-STABLE (which would get me thinking that I was definitely tracking stable) Right now since about the time of the code freeze, my kernels have read read (uname -a) 4.6-RC and/or 4.6-PRERELEASE I haven't been 100% diligent in logging my cvsup transactions so I cannot review when I would have downloaded any particular files unfortunately. However I have been running the same cvsup file for months and months now. I am doing a make clean in /usr/src now. And immediately after that I will cvsup again using that supfile And immediatley after that I will buildworld as usual. Hmm. clean - done cvsup - done buildworld - DIES This is how my buildworld dies exactly: ===> doc c++ -O -pipe -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc c++ -O -pipe -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/gen-perf.cc In file included from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/key-list.h:34, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/gen-perf.h:28, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/gen-perf.cc:26: /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/read-line.h:40: syntax error at end of saved text *** Error code 1 Stop in /usr/src/gnu/usr.bin/gperf. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Strangely though my other machine (which also just downloaded same sources via same cvsup file) does not die when doing a buildworld and is well past that point of the build process. (Still progressing, but it should be fine) What sort of things should I look for in this case? Obviously it is something specific to my one machine if no one else is seeing this and even another of my own machines is ok. Appreciate any suggestions. Cheers, Callum On Wed, May 22, 2002 at 12:54:13PM -0500, David W. Chapman Jr. wrote: > > >Oh, I just noticed this was posted to -stable, I thought it was posted > > >to -current > > > > > >it should work on -stable then. Sorry for the spam. > > > > > > > > > I couldn't find libgp.a in my buildworld logs. You may of hit the > > solution. I wonder if Callum cvsuped -current. > > libgp.a I believe is something that was recently added to -current. > > -- > David W. Chapman Jr. > [EMAIL PROTECTED] Raintree Network Services, Inc. > [EMAIL PROTECTED] FreeBSD Committer > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gperf broken - breaks buildworld
> >Oh, I just noticed this was posted to -stable, I thought it was posted > >to -current > > > >it should work on -stable then. Sorry for the spam. > > > > > I couldn't find libgp.a in my buildworld logs. You may of hit the > solution. I wonder if Callum cvsuped -current. libgp.a I believe is something that was recently added to -current. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gperf broken - breaks buildworld
David W. Chapman Jr. wrote: > Oh, I just noticed this was posted to -stable, I thought it was posted > to -current > > it should work on -stable then. Sorry for the spam. > I couldn't find libgp.a in my buildworld logs. You may of hit the solution. I wonder if Callum cvsuped -current. Kent > - Original Message - > From: "Rahul Siddharthan" <[EMAIL PROTECTED]> > To: "David W. Chapman Jr." <[EMAIL PROTECTED]> > Cc: "Callum M. Duncan" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Wednesday, May 22, 2002 12:43 PM > Subject: Re: gperf broken - breaks buildworld > > > >>David W. Chapman, Jr. wrote: >> >>>gperf is broken because libstdc++(which gperf depends on) is broken. >>> >>I thought that was -current, not -stable? >> >>- Rahul >> >> > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > > . > > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gperf broken - breaks buildworld
Oh, I just noticed this was posted to -stable, I thought it was posted to -current it should work on -stable then. Sorry for the spam. - Original Message - From: "Rahul Siddharthan" <[EMAIL PROTECTED]> To: "David W. Chapman Jr." <[EMAIL PROTECTED]> Cc: "Callum M. Duncan" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 12:43 PM Subject: Re: gperf broken - breaks buildworld > David W. Chapman, Jr. wrote: > > gperf is broken because libstdc++(which gperf depends on) is broken. > > I thought that was -current, not -stable? > > - Rahul > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: gperf broken - breaks buildworld
David W. Chapman, Jr. wrote: > gperf is broken because libstdc++(which gperf depends on) is broken. I thought that was -current, not -stable? - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Nigerian email fraud gang nabbed
Hi folks. Just thought that the following article from The Reg would be a amusing read. Unfortunately this probably won't stop the problem in the long run. http://theregister.co.uk/content/6/25394.html cheers Claus Guttesen _ Yahoo! Grupper Over 4000 grupper at blive medlem af - eller opret helt din egen! www.yahoo.dk/grupper To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Status of upgrades from 4.0 to the recent 4.x (was: Re: cvs commit: src/usr.bin/make Makefile compat.c job.c main.c pathnames.h)
On Wed, May 22, 2002 at 05:28:28PM +0100, Mark Murray wrote: > > I've been able to successfully upgrade a fresh 4.0-RELEASE to > > 4.6-RC2 with this patch applied to RELENG_4's make(1) sources. > > Great! :-) > > > The -DNOPERL is also required as gnu/usr.bin/perl/library/* > > makefiles call /usr/obj Perl's MakeMaker generated makefiles > > which have SHELL set to /bin/sh, and attempt to run shell from > > here. The work-around is to modify the "sh=" setting in the > > gnu/usr.bin/perl/libperl/config.*, but I'm not sure if this > > is the correct fix or not. Mark Murray CC'ed for consultancy. > > When you see MakeMaker being used, run screaming from the room. > It is the single largest cause of breakage in the perl-on-freebsd > build. If there is any other way of doing this, take that route. > > > 2. Merge the C version of makewhatis(1), it works very nice, > > and produces much more sane output than the Perl version. > > I would substantially support this route. > These two problems are different. First one being with MakeMaker and the corresponding makefiles attempting to run /bin/sh (probably some other stuff, didn't check) directly from /bin. The second one (minor) is with Perl version of makewhatis(1) attempting to run perl(1) directly from /usr/bin. Any ``#!/path/name'' hinted scripts are unsafe by definition during the DESTDIR="" installworld. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg45628/pgp0.pgp Description: PGP signature
Re: gperf broken - breaks buildworld
On Wed, May 22, 2002 at 12:30:29PM -0400, Callum M. Duncan wrote: > Kent, > > I do not have anything specified for CFLAGS in /etc/make.conf > therefore it should use the defaults/make.conf entry right? > > #CFLAGS= -O -pipe > > Hmmm... > > I will see if I can try a build on another box I run. > cheers, > Callum gperf is broken because libstdc++(which gperf depends on) is broken. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Status of upgrades from 4.0 to the recent 4.x (was: Re: cvs commit: src/usr.bin/make Makefile compat.c job.c main.c pathnames.h)
> I've been able to successfully upgrade a fresh 4.0-RELEASE to > 4.6-RC2 with this patch applied to RELENG_4's make(1) sources. Great! :-) > The -DNOPERL is also required as gnu/usr.bin/perl/library/* > makefiles call /usr/obj Perl's MakeMaker generated makefiles > which have SHELL set to /bin/sh, and attempt to run shell from > here. The work-around is to modify the "sh=" setting in the > gnu/usr.bin/perl/libperl/config.*, but I'm not sure if this > is the correct fix or not. Mark Murray CC'ed for consultancy. When you see MakeMaker being used, run screaming from the room. It is the single largest cause of breakage in the perl-on-freebsd build. If there is any other way of doing this, take that route. > 2. Merge the C version of makewhatis(1), it works very nice, > and produces much more sane output than the Perl version. I would substantially support this route. M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
