RE: buildworld errors
I just did a buildworld on a clean, freshly installed 6.1-RELEASE
system with no problems using the source tree that came on disk 1.
I've seen gcc bugs like this as a result of setting an optimization
flag too agressively. There's a good chance your prior make world
created a gcc binary that is broken. Now your in a catch-22.
Nuke and repave.
Ted
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Mark Busby
>Sent: Wednesday, May 17, 2006 12:46 PM
>To: help help
>Subject: buildworld errors
>
>
>While upgrading from 6.1 pr1 to 6.1 release, I got this msg 3
>days ago, waited, csvup again this morning but still the same
>error on buildworld.
> Thanks for the flames!
>
>
> ===> gnu/usr.bin/cc/cc (all)
>cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_CONFIG_H
>-DPREFIX=\"/usr\"
>-I/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_tools
>-I/usr/src/gnu/usr.bin/cc/cc/../cc_tools
>-I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc
>-I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/config
>-DDEFAULT_TARGET_VERSION=\"3.4.4\"
>-DDEFAULT_TARGET_MACHINE=\"\" -c
>/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gcc.c
>/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gcc.c: In
>function `fatal_error':
>/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gcc.c:5974:
>internal compiler error: in print_reg, at config/i386/i386.c:7116
>Please submit a full bug report,
>with preprocessed source if appropriate.
>{standard input}: Assembler messages:
>{standard input}:3778: Warning: end of file not at end of a
>line; newline inserted
>{standard input}:4088: Error: unbalanced parenthesis in operand 1.
>*** Error code 1
> Stop in /usr/src/gnu/usr.bin/cc/cc.
>*** Error code 1
> Stop in /usr/src/gnu/usr.bin/cc.
>*** Error code 1
> Stop in /usr/src/gnu/usr.bin.
>*** Error code 1
> Stop in /usr/src/gnu.
>*** Error code 1
> Stop in /usr/src.
>*** Error code 1
> Stop in /usr/src.
>*** Error code 1
> Stop in /usr/src.
>
>___
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to
>"[EMAIL PROTECTED]"
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.392 / Virus Database: 268.6.0/341 - Release Date: 5/16/2006
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
re buildworld errors
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of Mark Busby
> Sent: Wednesday, May 17, 2006 2:46 PM
> To: help help
> Subject: buildworld errors
>
> While upgrading from 6.1 pr1 to 6.1 release, I got this msg 3 days
ago,
> waited, csvup again this morning but still the same error on
buildworld.
> Thanks for the flames!
>
>>Did you try
>>cd /usr/src
>>make clean
>>make cleanworld
>>And then retry the build?
>>Maybe you have some old cruft hanging around
Cleaning the old stuff out changed where the error msg occurs and it errors
out sooner "lol"
It's nice not to wait 5 hours before the error msg. = ^ )
gcc version
muz# gcc -v
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.4 [FreeBSD] 20050518
New error msg
-DGENERATOR_FILE -I/usr/obj/usr/src/tmp/legacy/usr/include -c
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/getruntime.c
cc -O2 -fno-strict-aliasing -pipe -I. -DIN_GCC -DHAVE_CONFIG_H
-DPREFIX=\"/usr/obj/usr/src/tmp/usr\"
-I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools
-I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config
-DGENERATOR_FILE -I/usr/obj/usr/src/tmp/legacy/usr/include -c
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/hashtab.c
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/hashtab.c: In function
`htab_elements':
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/hashtab.c:663:
internal compiler error: in print_reg, at config/i386/i386.c:7116
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
{standard input}: Assembler messages:
{standard input}:0: Warning: end of file not at end of a line; newline inserted
{standard input}:1046: Error: unbalanced parenthesis in operand 1.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/cc/cc_tools.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/cc.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: buildworld errors
> -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] On Behalf Of Mark Busby > Sent: Wednesday, May 17, 2006 2:46 PM > To: help help > Subject: buildworld errors > > While upgrading from 6.1 pr1 to 6.1 release, I got this msg 3 days ago, > waited, csvup again this morning but still the same error on buildworld. > Thanks for the flames! > Did you try cd /usr/src make clean make cleanworld And then retry the build? Maybe you have some old cruft hanging around ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: buildworld errors on clean 4.9 install
It's stange though because without that option, everything went fine, I finished my build and installed, and I have found the same thing happened with others... I used the -j option at home no problem, but this laptop didn't like it for some reason. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kris Kennaway Sent: Thursday, January 29, 2004 12:59 PM To: Richard Hogben Cc: [EMAIL PROTECTED]; 'Kris Kennaway' Subject: Re: buildworld errors on clean 4.9 install On Thu, Jan 29, 2004 at 09:55:23AM -0800, Richard Hogben wrote: > Thanks, some searching on Google pointed to the same thing, seems the -j > option is not always a good idea for single processor computers. I have > been building since this morning, and no errors as of yet! -j shouldn't cause errors (I use it all the time), it's just the wrong thing to use when you're trying to get help with a build error. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld errors on clean 4.9 install
On Thu, Jan 29, 2004 at 09:55:23AM -0800, Richard Hogben wrote: > Thanks, some searching on Google pointed to the same thing, seems the -j > option is not always a good idea for single processor computers. I have > been building since this morning, and no errors as of yet! -j shouldn't cause errors (I use it all the time), it's just the wrong thing to use when you're trying to get help with a build error. Kris pgp0.pgp Description: PGP signature
RE: buildworld errors on clean 4.9 install
Thanks, some searching on Google pointed to the -j option I used, seems the -j option is not always a good idea for single processor computers. I have been building since this morning, and no errors as of yet! -Original Message- From: Sergey 'DoubleF' Zaharchenko [mailto:[EMAIL PROTECTED] Sent: Thursday, January 29, 2004 1:19 AM To: Richard Hogben Subject: Re: buildworld errors on clean 4.9 install On Wed, 28 Jan 2004 17:37:51 -0800 "Richard Hogben" <[EMAIL PROTECTED]> probably wrote: > /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/tree.c > cc: Internal compiler error: program cpp0 got fatal signal 11 > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error It looks like a memory problem, and it walks like a memory problem. It must be a memory problem:(. -- DoubleF With a gentleman I try to be a gentleman and a half, and with a fraud I try to be a fraud and a half. -- Otto von Bismarck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: buildworld errors on clean 4.9 install
Thanks, some searching on Google pointed to the same thing, seems the -j option is not always a good idea for single processor computers. I have been building since this morning, and no errors as of yet! -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 7:02 PM To: Richard Hogben Cc: [EMAIL PROTECTED] Subject: Re: buildworld errors on clean 4.9 install On Wed, Jan 28, 2004 at 05:37:51PM -0800, Richard Hogben wrote: > # make -j4 buildworld Rerun make without -j, which obscures the actual error. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld errors on clean 4.9 install
On Wed, Jan 28, 2004 at 05:37:51PM -0800, Richard Hogben wrote: > # make -j4 buildworld Rerun make without -j, which obscures the actual error. Kris pgp0.pgp Description: PGP signature
Re: buildworld errors
On Thu, Jul 03, 2003 at 11:23:19AM -0400 or thereabouts, quadrant wrote: > I did a cvsupit from FreeBSD 4.8 to current ( =. ) > I did a make buildworld 3 times so far with different > errors each time. Between each buildworld, I did the rm -rf /usr/obj > and started over again. It goes for about 4 hours each time, > and this is now the error I received while doing a make buildworld. > What is it that is going wrong here? > Any help would be greatly appreciated... > > ===> sbin/gbde ... > cc1: warnings being treated as errors Check if you have -Werror in CFLAGS in /etc/make.conf; if so, remove it. Check if you have WARNS or WARNS_WERROR in /etc/make.conf; if so, remove them. Check if either of these flags were specified on the command line; if so, remove them. Build world again. Or just cvsup again in a few days; might be a transient -current build failure. > /usr/src/sys/crypto/rijndael/rijndael-api-fst.c: In function > `rijndael_padEncrypt': > /usr/src/sys/crypto/rijndael/rijndael-api-fst.c:222: warning: implicit > declaration of function `panic' ^ Don't panic! :-) -- Josh > *** Error code 1 > > Stop in /usr/src/sbin/gbde. > *** Error code 1 > > Stop in /usr/src/sbin. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > apex# > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld errors
On Thu, 3 Jul 2003 11:23:19 -0400 quadrant <[EMAIL PROTECTED]> wrote: > I did a cvsupit from FreeBSD 4.8 to current ( =. ) > I did a make buildworld 3 times so far with different > errors each time. Between each buildworld, I did the rm -rf /usr/obj > and started over again. It goes for about 4 hours each time, > and this is now the error I received while doing a make buildworld. > What is it that is going wrong here? > Any help would be greatly appreciated... > > ===> sbin/gbde > cc -O -pipe -march=pentiumpro -I/usr/src/sbin/gbde/../../sys > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W$ > cc -O -pipe -march=pentiumpro -I/usr/src/sbin/gbde/../../sys > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W$ > cc -O -pipe -march=pentiumpro -I/usr/src/sbin/gbde/../../sys > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W$ > cc -O -pipe -march=pentiumpro -I/usr/src/sbin/gbde/../../sys > -Wsystem-headers -Werror -Wall -Wno-format-y2k -W$ > cc1: warnings being treated as errors > /usr/src/sys/crypto/rijndael/rijndael-api-fst.c: In function > `rijndael_padEncrypt': > /usr/src/sys/crypto/rijndael/rijndael-api-fst.c:222: warning: implicit > declaration of function `panic' > *** Error code 1 > > Stop in /usr/src/sbin/gbde. > *** Error code 1 > > Stop in /usr/src/sbin. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > apex# It's not wise going from 4.x to 5.x.. so many changes (gcc, etc).. I'd backup & do a clean install of 5.1-RELEASE if I were you. :-) -- Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
