Re: Buildworld fails on today 3.1-STABLE!
Mike Smith m...@smith.net.au writes: I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -O2 works fine too. -O3 does not. We'll probably see the newer version of compiler before this is fixed. No, -O2 does not work fine; we've seen reports of it breaking things before. Maybe that's an explantation for the strange things I have seen with gnome a while ago ? I frequently got floating point exceptions in libgtk, (especially when running the pager applet), but I wasn't able to find anything. Recompiling everthing with pgcc did solve this for me. -- # /AS/# To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
On Tue, 16 Feb 1999, Mikhail Teterin wrote: I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -O2 works fine too. -O3 does not. We'll probably see the newer version of compiler before this is fixed. -O2 does *not* work for the alpha build (at least with gcc 2.7.2.x). It might work with a newer compiler if and when that happens. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
At 8:05 pm -0800 16/2/99, Mike Smith wrote: [...] No, -O2 does not work fine; we've seen reports of it breaking things before. I've been using -O2 building -current for over a year with no problems. I haven't dared try it for the kernel though... -- Bob Bishop (0118) 977 4017 international code +44 118 r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Bob Bishop wrote: At 8:05 pm -0800 16/2/99, Mike Smith wrote: [...] No, -O2 does not work fine; we've seen reports of it breaking things before. I've been using -O2 building -current for over a year with no problems. I haven't dared try it for the kernel though... Lucky you. -O2 *does* break world for many people. Eventually, it might break your world too, and there is a great chance you'll first spam -current before changing -O2 to -O and trying again. Or there would, if we stopped hitting on this nail. :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
:At 8:05 pm -0800 16/2/99, Mike Smith wrote: :[...] :No, -O2 does not work fine; we've seen reports of it breaking things :before. : :I've been using -O2 building -current for over a year with no problems. I :haven't dared try it for the kernel though... : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK I've been using -O2 kernels for over a year. Works fine as far as I can tell. makeoptions COPTFLAGS=-O2 -pipe -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
On Thu, 18 Feb 1999, Daniel C. Sobral wrote: Lucky you. -O2 *does* break world for many people. Eventually, it might break your world too, and there is a great chance you'll first spam -current before changing -O2 to -O and trying again. Or there would, if we stopped hitting on this nail. :-) Odd..I've been running -O2 -mno-486 -pipe for at least a year now, without noticing any world problems (or weird behaviour from binaries) other than the commit-related breakage everyone else has seen due to legitimate bugs. What would cause some people to have problems with -O2 and others not? I also run my kernels -O3 because they work for me, but I understand the potential problems with this and drop it back if I ever have problems. This reminds me of something I need to benchmark a bit more: I was testing the optimization of egcs 1.1.1 and found that -O3 produced executables which were significantly slower than -O2, no matter what architecture settings I used. From memory, for -O2 binaries I was getting ~20% speed improvements on my simple test suite compiling with -mpentium -march=pentium compared to -mno-486 on GCC 2.7.2.3 Kris -- Daniel C. Sobral (8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Matthew Dillon wrote: I've been using -O2 kernels for over a year. Works fine as far as I can tell. I've had a few failures with -O2 ages ago, though I can't guess how long ages was - I definitely remember tracing one problem down to '-O' vs. '-O2', I stick to '-0' now religiously... (at least it rules it out of the equation - I hope g) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Buildworld fails on today 3.1-STABLE!
Here is output (checked 2 times) :( ? === share/doc/psd/title touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1- /usr/obj/src/share/doc/psd/title/Title) |? gzip -cn Title.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/contents touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/contents; groff -mtty-char -Tascii -ms -o1- /usr/obj/src/share/doc/psd/contents/contents.ms) |? gzip -cn contents.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/05.sysman touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/05.sysman; groff -mtty-char -Tascii -t -ms -o1- /usr/obj/src/share/doc/psd/05.sysman/0.t /usr/obj/src/share/doc/psd/05.sysman/1.0.t /usr/obj/src/share/doc/psd/05.sysman/1.1.t /usr/obj/src/share/doc/psd/05.sysman/1.2.t /usr/obj/src/share/doc/psd/05.sysman/1.3.t /usr/obj/src/share/doc/psd/05.sysman/1.4.t /usr/obj/src/share/doc/psd/05.sysman/1.5.t /usr/obj/src/share/doc/psd/05.sysman/1.6.t /usr/obj/src/share/doc/psd/05.sysman/1.7.t /usr/obj/src/share/doc/psd/05.sysman/2.0.t /usr/obj/src/share/doc/psd/05.sysman/2.1.t /usr/obj/src/share/doc/psd/05.sysman/2.2.t /usr/obj/src/share/doc/psd/05.sysman/2.3.t /usr/obj/src/share/doc/psd/05.sysman/2.4.t /usr/obj/src/share/doc/psd/05.sysman/2.5.t /usr/obj/src/share/doc/psd/05.sysman/a.t) |? gzip -cn paper.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/12.make touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc; groff -mtty-char -Tascii -ms -o1- /usr/obj/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc/tutorial.ms) |? gzip -cn paper.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/13.rcs === share/doc/psd/13.rcs/rcs touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/13.rcs/rcs/../../../../../gnu/usr.bin/rcs/doc; groff -mtty-char -Tascii -p -ms -o1- /usr/obj/src/share/doc/psd/13.rcs/rcs/../../../../../gnu/usr.bin/rcs/doc/rcs.ms) |? gzip -cn paper.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/13.rcs/rcs_func touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/13.rcs/rcs_func/../../../../../gnu/usr.bin/rcs/doc; groff -mtty-char -Tascii -ms -o1- /usr/obj/src/share/doc/psd/13.rcs/rcs_func/../../../../../gnu/usr.bin/rcs/doc/rcs_func.ms) |? gzip -cn rcs_func.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/18.gprof touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc; groff -mtty-char -Tascii -e -t -p -s -me -o1- /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/header.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/abstract.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/intro.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/profiling.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/gathering.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/postp.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/present.me /usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/refs.me) |? gzip -cn paper.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' === share/doc/psd/19.curses /usr/libexec/vfontedpr /usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/ex1.c | grep -v ^'wh ex1.gr /usr/libexec/vfontedpr /usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/twinkle1.c | grep -v ^'wh twinkle1.gr tbl /usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/intro.2 intro.2.tbl tbl:/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/intro.2:40: `tab' option requires argument in parentheses touch _stamp.extraobjs sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(Master\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(intro.0\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(intro.1\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(intro.3\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(intro.4\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(intro.5\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(intro.6\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(macros\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:' -e\ 's:\(\.so[\ \ ][\ \
RE: Buildworld fails on today 3.1-STABLE!
=== share/doc/psd/title touch _stamp.extraobjs (cd /usr/obj/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1- /usr/obj/src/share/doc/psd/title/Title) |_ gzip -cn Title.ascii.gz groff: can't find `DESC' file groff:fatal error: invalid device `ascii' This has happened to me many times with various versions of current and 3.x , and its always fixed by lowering the -O# # , I don't know why I just know it works :). I re cvsupped several times once, and erased obj, and it always did it until i lowered the -O. --- E-Mail: Luke l...@aus.org Sent by XFMail -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Luke wrote: === share/doc/psd/title [snip] groff: can't find `DESC' file groff:fatal error: invalid device `ascii' This has happened to me many times with various versions of current and 3.x , and its always fixed by lowering the -O# # , I don't know why I just know it works :). I re cvsupped several times once, and erased obj, and it always did it until i lowered the -O. Thanks! - That just fixed my problem... I was going to post a similar message along the lines of -current broken? - but you just saved me the embarassment! :)... I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -O2 works fine too. -O3 does not. We'll probably see the newer version of compiler before this is fixed. -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Maxim Sobolev wrote: Here is output (checked 2 times) :( groff: can't find `DESC' file groff:fatal error: invalid device `ascii' [super-snip] | groff -mtty-char -Tascii -t -s -me -o1- /dev/null groff: can't find `DESC' file groff:fatal error: invalid device `ascii' Ugh, did you have to send so much output? :-) - What -O setting are you using to build with? - Someone reported (and I've seen myself) - upping it will cause the problems above... (I'm not saying it's the only cause, but it got me :) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -O2 works fine too. -O3 does not. We'll probably see the newer version of compiler before this is fixed. No, -O2 does not work fine; we've seen reports of it breaking things before. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
