Re: buildworld error 8.2-STABLE amd64
On Mon, 02 Jan 2012 07:18:53 +0100 Marco Steinbach c...@executive-computing.de wrote: Janos Dohanics wrote on 31.12.2011 19:56: Buildworld stopped with this error (with updated source): [...] cc -O3 -DNEED_SOLARIS_BOOLEAN [...] I have posted the build log at http://wwwp.3dresearch.com/ALMAVIVA2011123101_buildworld Would you please advise? Quoting /usr/share/examples/etc/make.conf: # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings other than -O and -O2 are not # recommended or supported for compiling the world or the kernel - # please revert any nonstandard optimization settings to -O or -O2 # -fno-strict-aliasing before submitting bug reports without patches # to the developers. The error you're seeing is a result from using O3 for building the source in question -- At least my 8.2-STABLE ran into the same problem, once I used O3, instead of the default '-O2 -pipe'. MfG CoCo Thank you, there was indeed the line CFLAGS=-O3 in make.conf, after I have commented it out, I could build world. I'm wondering how was my make.conf changed though; I'm sure I did not add CFLAGS=-O3 - is it possible that one of the ports have added this? -- Janos Dohanics ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld error 8.2-STABLE amd64
Janos Dohanics wrote on 02.01.2012 11:04: On Mon, 02 Jan 2012 07:18:53 +0100 Marco Steinbach c...@executive-computing.de wrote: Janos Dohanics wrote on 31.12.2011 19:56: Buildworld stopped with this error (with updated source): [...] cc -O3 -DNEED_SOLARIS_BOOLEAN [...] I have posted the build log at http://wwwp.3dresearch.com/ALMAVIVA2011123101_buildworld Would you please advise? Quoting /usr/share/examples/etc/make.conf: # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings other than -O and -O2 are not # recommended or supported for compiling the world or the kernel - # please revert any nonstandard optimization settings to -O or -O2 # -fno-strict-aliasing before submitting bug reports without patches # to the developers. The error you're seeing is a result from using O3 for building the source in question -- At least my 8.2-STABLE ran into the same problem, once I used O3, instead of the default '-O2 -pipe'. MfG CoCo Thank you, there was indeed the line CFLAGS=-O3 in make.conf, after I have commented it out, I could build world. I'm wondering how was my make.conf changed though; I'm sure I did not add CFLAGS=-O3 - is it possible that one of the ports have added this? Although, as far as I can tell, not explicitly forbidden in the porter's handbook, I think that to be highly unlikely in the case of CFLAGS. The least I'd expect would be some kind notice, if so intrusive a change is done deliberately. If I'd suspect a port fiddling with /etc/make.conf, I'd probably go looking for entries carrying a timestamp close to /etc/make.confs in /var/db/pkg. Of course, this largely depends on what happened in between the time of actual modification and me noticing, but I think that's the first thing I'd do. MfG CoCo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld error 8.2-STABLE amd64
On Mon, 02 Jan 2012 13:15:59 +0100 Marco Steinbach c...@executive-computing.de wrote: Janos Dohanics wrote on 02.01.2012 11:04: On Mon, 02 Jan 2012 07:18:53 +0100 Marco Steinbach c...@executive-computing.de wrote: Janos Dohanics wrote on 31.12.2011 19:56: Buildworld stopped with this error (with updated source): [...] cc -O3 -DNEED_SOLARIS_BOOLEAN [...] I have posted the build log at http://wwwp.3dresearch.com/ALMAVIVA2011123101_buildworld Would you please advise? Quoting /usr/share/examples/etc/make.conf: # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings other than -O and -O2 are not # recommended or supported for compiling the world or the kernel - # please revert any nonstandard optimization settings to -O or # -O2 -fno-strict-aliasing before submitting bug reports without # patches to the developers. The error you're seeing is a result from using O3 for building the source in question -- At least my 8.2-STABLE ran into the same problem, once I used O3, instead of the default '-O2 -pipe'. MfG CoCo Thank you, there was indeed the line CFLAGS=-O3 in make.conf, after I have commented it out, I could build world. I'm wondering how was my make.conf changed though; I'm sure I did not add CFLAGS=-O3 - is it possible that one of the ports have added this? Although, as far as I can tell, not explicitly forbidden in the porter's handbook, I think that to be highly unlikely in the case of CFLAGS. The least I'd expect would be some kind notice, if so intrusive a change is done deliberately. If I'd suspect a port fiddling with /etc/make.conf, I'd probably go looking for entries carrying a timestamp close to /etc/make.confs in /var/db/pkg. Of course, this largely depends on what happened in between the time of actual modification and me noticing, but I think that's the first thing I'd do. MfG CoCo Thanks again, unfortunately, I have edited /etc/make.conf and did not make note of the time stamp... -- Janos Dohanics ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld error 8.2-STABLE amd64
Janos Dohanics wrote on 31.12.2011 19:56: Buildworld stopped with this error (with updated source): [...] cc -O3 -DNEED_SOLARIS_BOOLEAN [...] I have posted the build log at http://wwwp.3dresearch.com/ALMAVIVA2011123101_buildworld Would you please advise? Quoting /usr/share/examples/etc/make.conf: # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings other than -O and -O2 are not recommended # or supported for compiling the world or the kernel - please revert any # nonstandard optimization settings to -O or -O2 -fno-strict-aliasing # before submitting bug reports without patches to the developers. The error you're seeing is a result from using O3 for building the source in question -- At least my 8.2-STABLE ran into the same problem, once I used O3, instead of the default '-O2 -pipe'. MfG CoCo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Buildworld error
Terry ( 1stKMH ) te...@firstkmh.co.uk writes: Hi Glen the error seems randomized I did a fresh cvsup and moved make.conf out of the way and did all the clean up steps as per the handbook this morning and it still failed. The only thing the error has in common each time is internal compiler error: in find_idf, If the errors are different each time, it's probably not a software problem. Test your RAM. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Buildworld error
On Sun, Jan 25, 2009 at 1:56 PM, Terry te...@bluelight.org.uk wrote: I am trying to upgrade from 7.0-STABLE to 7.1 Release. I used RELENG_7_1 as my cvsup tag. But no matter what I try I get error's during make buildworld --- /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/sched-ebb.c: In function 'schedule_ebbs': /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/sched-ebb.c:542: internal compiler error: in find_idf, at tree-into-ssa.c:1040 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 -- I did read on google that one person got around it by installing ccache but it didnt work for me also the error is not all ways the same -- /include -c asn1_HostAddress.c -o asn1_HostAddress.So asn1_HostAddress.c: In function 'decode_HostAddress': asn1_HostAddress.c:52: internal compiler error: in find_idf, at tree-into-ssa.c:1040 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/kerberos5/lib/libasn1. Do you have anything obscure in make.conf ? When it fails in succession, does it fail *after* the last point of failure, or is it randomized? When was your last c(v)sup? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: buildworld error with 7.1 BETA
make -j 4 buildworld gives after a while the following gzip -cn /usr/src/usr.sbin/zic/zdump/../zdump.8 zdump.8.gz cc -O2 -fno-strict-aliasing -pipe -DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\/usr/share/zoneinfo\ -Demkdir=mkdir -I/usr/src/usr.sbin/zic/zdump/.. -I/usr/src/usr.sbin/zic/zdump/../../../lib/libc/stdtime -o zdump zdump.o ialloc.o scheck.o === usr.sbin/zzz (all) gzip -cn /usr/src/usr.sbin/zzz/zzz.8 zzz.8.gz 1 error *** Error code 2 1 error *** Error code 2 1 error Suggestions? /Leslie i could almost see this coming. seems pretty much like hardware. just try to run make one more time. not cleaning anything just type the same make command after fail without extra activity. if it fails again check if you have filled your disks up and you might want to `ls /usr/src/usr.sbin/zzz/zzz.8` to see if its really there ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error with 7.1 BETA
Nash Nipples skrev: make -j 4 buildworld gives after a while the following gzip -cn /usr/src/usr.sbin/zic/zdump/../zdump.8 zdump.8.gz cc -O2 -fno-strict-aliasing -pipe -DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\/usr/share/zoneinfo\ -Demkdir=mkdir -I/usr/src/usr.sbin/zic/zdump/.. -I/usr/src/usr.sbin/zic/zdump/../../../lib/libc/stdtime -o zdump zdump.o ialloc.o scheck.o === usr.sbin/zzz (all) gzip -cn /usr/src/usr.sbin/zzz/zzz.8 zzz.8.gz 1 error *** Error code 2 1 error *** Error code 2 1 error Suggestions? /Leslie i could almost see this coming. seems pretty much like hardware. just try to run make one more time. not cleaning anything just type the same make command after fail without extra activity. if it fails again check if you have filled your disks up and you might want to `ls /usr/src/usr.sbin/zzz/zzz.8` to see if its really there It fails again! Disks are not full and the file is there. :df -H Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s4a520M224M254M47%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad4s4g 33G1.3G 29G 4%/home /dev/ad4s4e520M 14k478M 0%/tmp /dev/ad4s4f 52G5.5G 42G11%/usr /dev/ad4s4d5.2G177M4.6G 4%/var I had 7.0 on the machine before and when upgrading to 7.0-p4 everything went smootly. Do you really think it's hardware? /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error with 7.1 BETA
just try to run make one more time. not cleaning anything just type the same make command after fail without extra activity. if it fails again check if you have filled your disks up and you might want to `ls /usr/src/usr.sbin/zzz/zzz.8` to see if its really there It fails again! Disks are not full and the file is there. no its less likely to be a hardware error. there are cases when it breaks into an error and then after you restart the whole procedure it goes fine and breaks somewhere closer to finish. i think you can try to update the source code once again. maybe the fix is coming. or you can try to run make in /usr/src/usr.sbin/zzz/ to make sure there is no errors or you can try to run make in /usr/src/etc/ which should be the next bus stop in the building world proccess. hope someone else knows (probably from [EMAIL PROTECTED]) nash original message: -- make -j 4 buildworld gives after a while the following gzip -cn /usr/src/usr.sbin/zic/zdump/../zdump.8 zdump.8.gz cc -O2 -fno-strict-aliasing -pipe -DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\/usr/share/zoneinfo\ -Demkdir=mkdir -I/usr/src/usr.sbin/zic/zdump/.. -I/usr/src/usr.sbin/zic/zdump/../../../lib/libc/stdtime -o zdump zdump.o ialloc.o scheck.o === usr.sbin/zzz (all) gzip -cn /usr/src/usr.sbin/zzz/zzz.8 zzz.8.gz 1 error *** Error code 2 1 error *** Error code 2 1 error Suggestions? /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error with 7.1 BETA
2008/9/19 Leslie Jensen [EMAIL PROTECTED]: make -j 4 buildworld gives after a while the following gzip -cn /usr/src/usr.sbin/zic/zdump/../zdump.8 zdump.8.gz cc -O2 -fno-strict-aliasing -pipe -DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\/usr/share/zoneinfo\ -Demkdir=mkdir -I/usr/src/usr.sbin/zic/zdump/.. -I/usr/src/usr.sbin/zic/zdump/../../../lib/libc/stdtime -o zdump zdump.o ialloc.o scheck.o === usr.sbin/zzz (all) gzip -cn /usr/src/usr.sbin/zzz/zzz.8 zzz.8.gz 1 error *** Error code 2 1 error *** Error code 2 1 error Suggestions? Build without -j so the error message is sensible. That should always be the first thing you strip out on failure, and before you even bother to report. :) -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error with 7.1 BETA
Nash Nipples skrev: just try to run make one more time. not cleaning anything just type the same make command after fail without extra activity. if it fails again check if you have filled your disks up and you might want to `ls /usr/src/usr.sbin/zzz/zzz.8` to see if its really there It fails again! Disks are not full and the file is there. no its less likely to be a hardware error. there are cases when it breaks into an error and then after you restart the whole procedure it goes fine and breaks somewhere closer to finish. i think you can try to update the source code once again. maybe the fix is coming. or you can try to run make in /usr/src/usr.sbin/zzz/ to make sure there is no errors or you can try to run make in /usr/src/etc/ which should be the next bus stop in the building world proccess. When doing make in /usr/src/etc/ I got an error stating that it could not build /etc/mail/.submit.mc. It turned out that I had made a typo in /etc/make.conf. Sorry! Thanks for all your suggestions, it helped me find the error. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld error
Schiz0 [EMAIL PROTECTED] writes: I'm following the handbook to rebuild world. I updated via csup (Supfile: http://pastebin.ca/427631 ) right before I ran make buildworld. Now I'm getting this error: http://pastebin.ca/427605 I just installed the system before doing this, so the /usr/src dir should be fresh. Any ideas? Thanks in advance to everyone. Without IRC and the mailing lists, I would be using Windows ;-) Is there anything non-standard in your make.conf? Are you using Kerberos? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld error
On 4/7/07, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I'm following the handbook to rebuild world. I updated via csup (Supfile: http://pastebin.ca/427631 ) right before I ran make buildworld. Now I'm getting this error: http://pastebin.ca/427605 I just installed the system before doing this, so the /usr/src dir should be fresh. Any ideas? Thanks in advance to everyone. Without IRC and the mailing lists, I would be using Windows ;-) Is there anything non-standard in your make.conf? Are you using Kerberos? No, I'm not using Kerberos. Also, I went through the entire make.conf man page and added the appropriate settings for my system. My make.conf is pasted at: http://pastebin.ca/428698 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld error
On 07/04/07, Schiz0 [EMAIL PROTECTED] wrote: On 4/7/07, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I'm following the handbook to rebuild world. I updated via csup (Supfile: http://pastebin.ca/427631 ) right before I ran make buildworld. Now I'm getting this error: http://pastebin.ca/427605 I just installed the system before doing this, so the /usr/src dir should be fresh. Any ideas? Thanks in advance to everyone. Without IRC and the mailing lists, I would be using Windows ;-) Is there anything non-standard in your make.conf? Are you using Kerberos? No, I'm not using Kerberos. Also, I went through the entire make.conf man page and added the appropriate settings for my system. My make.conf is pasted at: http://pastebin.ca/428698 For the first part, I do not believe that make checks what the NO_* variable is set to, only that it is set, so false is the same as true (I think I remember reading that somewhere). Try building world without any /etc/make.conf Obviously if it succeeds you have narrowed down your problems. If that fails, csup and try again. Sometimes you catch the server with partially updated sources. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld error
Schiz0 [EMAIL PROTECTED] writes: On 4/7/07, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I'm following the handbook to rebuild world. I updated via csup (Supfile: http://pastebin.ca/427631 ) right before I ran make buildworld. Now I'm getting this error: http://pastebin.ca/427605 I just installed the system before doing this, so the /usr/src dir should be fresh. Any ideas? Thanks in advance to everyone. Without IRC and the mailing lists, I would be using Windows ;-) Is there anything non-standard in your make.conf? Are you using Kerberos? No, I'm not using Kerberos. Also, I went through the entire make.conf man page and added the appropriate settings for my system. My make.conf is pasted at: http://pastebin.ca/428698 That is a *big* configuration file; I'm not going to go through all of it to debug it. You have a lot of variables set to false, which is the same as setting them to true; see make.conf(5) for details. I recommend building with an empty make.conf to be sure that you are able to build without any special settings, and *then* try tuning it (if you want to; there is rarely any strong reason to do so). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld error
On 4/7/07, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: On 4/7/07, Lowell Gilbert [EMAIL PROTECTED] wrote: Schiz0 [EMAIL PROTECTED] writes: I'm following the handbook to rebuild world. I updated via csup (Supfile: http://pastebin.ca/427631 ) right before I ran make buildworld. Now I'm getting this error: http://pastebin.ca/427605 I just installed the system before doing this, so the /usr/src dir should be fresh. Any ideas? Thanks in advance to everyone. Without IRC and the mailing lists, I would be using Windows ;-) Is there anything non-standard in your make.conf? Are you using Kerberos? No, I'm not using Kerberos. Also, I went through the entire make.confman page and added the appropriate settings for my system. My make.conf is pasted at: http://pastebin.ca/428698 That is a *big* configuration file; I'm not going to go through all of it to debug it. You have a lot of variables set to false, which is the same as setting them to true; see make.conf(5) for details. I recommend building with an empty make.conf to be sure that you are able to build without any special settings, and *then* try tuning it (if you want to; there is rarely any strong reason to do so). It seems I read through make.conf(5) a bit to fast and missed the part about it ignoring the value of bool vars. I'll redo my make.conf and try rebuilding and see if that works. If it doesn't, I'll clear out make.confand try again. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error in Makefile.inc1
Kris Kennaway said the following on 2/3/2005 12:29 AM: On Wed, Feb 02, 2005 at 10:25:38PM -0500, Glenn Sieb wrote: Stop in /usr/src. # So, should this upgrade be this painful? 5.1-RELEASE-p17 isn't _that_ old.. I kind of wonder now what's going to happen when I upgrade one of my boxes from 4.11-RELEASE to 5.3-RELEASE? :-/ Typically we only support source upgrades from systems after a certain point. Talk to [EMAIL PROTECTED] about the status of upgrading from 5.1-RELEASE. Thanks, Kris.. it appears that doing make -DALWAYS_CHECK_MAKE did the trick for me (which would have happened had I just done a buildworld, from what Ruslan said). Great appreciation from me to everyone who helped out on this issue. This makes my life MUCH easier tonight. :) Best, --Glenn -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error in Makefile.inc1
On Thu, Feb 03, 2005 at 10:53:24AM -0500, Glenn Sieb wrote: Kris Kennaway said the following on 2/3/2005 12:29 AM: On Wed, Feb 02, 2005 at 10:25:38PM -0500, Glenn Sieb wrote: Stop in /usr/src. # So, should this upgrade be this painful? 5.1-RELEASE-p17 isn't _that_ old.. I kind of wonder now what's going to happen when I upgrade one of my boxes from 4.11-RELEASE to 5.3-RELEASE? :-/ Typically we only support source upgrades from systems after a certain point. Talk to [EMAIL PROTECTED] about the status of upgrading from 5.1-RELEASE. Thanks, Kris.. it appears that doing make -DALWAYS_CHECK_MAKE did the trick for me (which would have happened had I just done a buildworld, from what Ruslan said). Great appreciation from me to everyone who helped out on this issue. This makes my life MUCH easier tonight. :) Don't ask me why ALWAYS_CHECK_MAKE was invented, I pathologically hate it. :-) Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgp20z2buH81k.pgp Description: PGP signature
RE: buildworld error in Makefile.inc1
on WEDS 2-2-05, Glenn Sieb wrote (paraphrased): (quoting the error): error in Makefile.inc1, cannot continue... I ran into this problem last July doing a 5.1 5.2.1 upgrade, during each cvsup the Makefile.inc1 would be re downloaded because after each cvsup, I corrected the syntax (using #edit) 501101)) TO: 501101 )) in this case line 830, in my case I think it was line 137 iirc, maybe someone should permanently comment that code: # leave a space after the releasedir checking code # number and before the closing parenth PLEASE!!! I had found the solution after much time searching on the web... Jeff __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error in Makefile.inc1
On Wed, Feb 02, 2005 at 05:59:11PM -0800, Jeffrey Bouquet wrote: on WEDS 2-2-05, Glenn Sieb wrote (paraphrased): (quoting the error): error in Makefile.inc1, cannot continue... I ran into this problem last July doing a 5.1 5.2.1 upgrade, during each cvsup the Makefile.inc1 would be re downloaded because after each cvsup, I corrected the syntax (using #edit) 501101)) TO: 501101 )) in this case line 830, in my case I think it was line 137 iirc, maybe someone should permanently comment that code: # leave a space after the releasedir checking code # number and before the closing parenth PLEASE!!! make was fixed some time ago to not treat this as syntax error. Kris pgpKChNDWw1Xp.pgp Description: PGP signature
Re: buildworld error in Makefile.inc1
Kris Kennaway said the following on 2/2/2005 9:14 PM: On Wed, Feb 02, 2005 at 05:59:11PM -0800, Jeffrey Bouquet wrote: on WEDS 2-2-05, Glenn Sieb wrote (paraphrased): (quoting the error): error in Makefile.inc1, cannot continue... I ran into this problem last July doing a 5.1 5.2.1 upgrade, during each cvsup the Makefile.inc1 would be re downloaded because after each cvsup, I corrected the syntax (using #edit) 501101)) TO: 501101 )) in this case line 830, in my case I think it was line 137 iirc, maybe someone should permanently comment that code: # leave a space after the releasedir checking code # number and before the closing parenth PLEASE!!! make was fixed some time ago to not treat this as syntax error. Kris I changed the end of line 830... and now when I do make: # make +for: not found *** Error code 127 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # So, should this upgrade be this painful? 5.1-RELEASE-p17 isn't _that_ old.. I kind of wonder now what's going to happen when I upgrade one of my boxes from 4.11-RELEASE to 5.3-RELEASE? :-/ Thanks in advance, everyone, Best, --Glenn -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error in Makefile.inc1
On Wed, Feb 02, 2005 at 10:25:38PM -0500, Glenn Sieb wrote: Stop in /usr/src. # So, should this upgrade be this painful? 5.1-RELEASE-p17 isn't _that_ old.. I kind of wonder now what's going to happen when I upgrade one of my boxes from 4.11-RELEASE to 5.3-RELEASE? :-/ Typically we only support source upgrades from systems after a certain point. Talk to [EMAIL PROTECTED] about the status of upgrading from 5.1-RELEASE. Kris pgpDwXhw41niZ.pgp Description: PGP signature
RE: buildworld error
Hey people, I just had this problem. Here's what worked for me: rm -r /usr/obj cd /usr/src make world HTH Eric F Crist President AdTech Integrated Systems, Inc (952) 403-9000 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Stewart Sent: Saturday, November 08, 2003 2:27 PM To: Jason; [EMAIL PROTECTED] Subject: Re: buildworld error On Saturday 08 November 2003 12:10 pm, Jason wrote: Last night I updated all my source files to buildworld, but ran into a problem. I tried to build it 3 times, and each time it stops at the same spot. If I retype the last commands show letter for letter they work. It stops at something like $gzip -cn cvs.info cvs.info.gz. If I immediately enter this command after the error it does not work, but above it is a 3 line command for makeinfo. If I renter this command then the gzip works. If this just some small glitch in some config file that has already been fixed? If it has not been fixed, or no one knows, what file show I look into to correct this myself? I am running 5.1 with my cvs tag set to current. The error occurs about 38 minutes into the build, so I would be glad to try suggestions but I don't want to waste a day on this. Thanks, Jason First rule of thumb is to re-cvsup src-all after you have waited awhile. If that doesn't work, include the error messages. If you are following -current, you should also be subscribed to the lists that deal with problems, such as cvs-all, hackers, -current, and etc. You can see the problem being addressed and then fixed. This used to be part of the suggested requirements for following stable and they definitely apply to current. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [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 error
On Sunday 09 November 2003 03:11 pm, Minnesota Slinky wrote: Hey people, I just had this problem. Here's what worked for me: rm -r /usr/obj cd /usr/src make world It has only been a few weeks since doing a world was dangerous. If you had certain USB components, the system would completely lock up at boot time. If you tested your installkernel before you did the installworld, you could boot kernel.old and run as if nothing was wrong. In a few days, the problem was fixed but until then, they had to unplug their USB components and after the system had booted, they could plug them back in. The sequence in UPDATING is there for a reason. FWIW, Jason removed both obj and src and it didn't help. Kent HTH Eric F Crist President AdTech Integrated Systems, Inc (952) 403-9000 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Stewart Sent: Saturday, November 08, 2003 2:27 PM To: Jason; [EMAIL PROTECTED] Subject: Re: buildworld error On Saturday 08 November 2003 12:10 pm, Jason wrote: Last night I updated all my source files to buildworld, but ran into a problem. I tried to build it 3 times, and each time it stops at the same spot. If I retype the last commands show letter for letter they work. It stops at something like $gzip -cn cvs.info cvs.info.gz. If I immediately enter this command after the error it does not work, but above it is a 3 line command for makeinfo. If I renter this command then the gzip works. If this just some small glitch in some config file that has already been fixed? If it has not been fixed, or no one knows, what file show I look into to correct this myself? I am running 5.1 with my cvs tag set to current. The error occurs about 38 minutes into the build, so I would be glad to try suggestions but I don't want to waste a day on this. Thanks, Jason First rule of thumb is to re-cvsup src-all after you have waited awhile. If that doesn't work, include the error messages. If you are following -current, you should also be subscribed to the lists that deal with problems, such as cvs-all, hackers, -current, and etc. You can see the problem being addressed and then fixed. This used to be part of the suggested requirements for following stable and they definitely apply to current. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error
Ok, here is the last section of output and the error. After this if I do ethier gzip command I get an error, but if I enter the makeinfo commands first the gzip command then works. Could this be some kind of schedualling problem because I normally use the command $time make -j4 buildworld. But it always stops at this point, so it must be something specific to the cvs/doc files. I have emailed the maintiner listed in the make files and have gotten no response. Anyone else have this experience? Thanks, Jason === gnu/usr.bin/cvs/doc makeinfo --no-split -I /usr/src/gnu/usr.bin/cvs/doc -I /usr/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc /usr/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvs.texinfo -o cvs.info makeinfo --no-split -I /usr/src/gnu/usr.bin/cvs/doc -I /usr/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc /usr/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvsclient.texi -o cvsclient.info gzip -cn cvsclient.info cvsclient.info.gz gzip -cn cvs.info cvs.info.gz 1 error *** Error code 2 1 error *** Error code 2 1 error ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error
On Sun, Nov 09, 2003 at 07:32:57PM -0500, Jason wrote: Ok, here is the last section of output and the error. After this if I do ethier gzip command I get an error, but if I enter the makeinfo commands first the gzip command then works. Could this be some kind of schedualling problem because I normally use the command $time make -j4 buildworld. But it always stops at this point, so it must be something specific to the cvs/doc files. I have emailed the maintiner listed in the make files and have gotten no response. Anyone else have this experience? Thanks, Jason Don't use -j when posting buildworld errors, because they are obscured amongst other output. Please retry without -j and post the actual error. Kris pgp0.pgp Description: PGP signature
Re: buildworld error
On Saturday 08 November 2003 12:10 pm, Jason wrote: Last night I updated all my source files to buildworld, but ran into a problem. I tried to build it 3 times, and each time it stops at the same spot. If I retype the last commands show letter for letter they work. It stops at something like $gzip -cn cvs.info cvs.info.gz. If I immediately enter this command after the error it does not work, but above it is a 3 line command for makeinfo. If I renter this command then the gzip works. If this just some small glitch in some config file that has already been fixed? If it has not been fixed, or no one knows, what file show I look into to correct this myself? I am running 5.1 with my cvs tag set to current. The error occurs about 38 minutes into the build, so I would be glad to try suggestions but I don't want to waste a day on this. Thanks, Jason First rule of thumb is to re-cvsup src-all after you have waited awhile. If that doesn't work, include the error messages. If you are following -current, you should also be subscribed to the lists that deal with problems, such as cvs-all, hackers, -current, and etc. You can see the problem being addressed and then fixed. This used to be part of the suggested requirements for following stable and they definitely apply to current. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld error
On Saturday 08 November 2003 12:27 pm, Kent Stewart wrote: On Saturday 08 November 2003 12:10 pm, Jason wrote: Last night I updated all my source files to buildworld, but ran into a problem. I tried to build it 3 times, and each time it stops at the same spot. If I retype the last commands show letter for letter they work. It stops at something like $gzip -cn cvs.info cvs.info.gz. If I immediately enter this command after the error it does not work, but above it is a 3 line command for makeinfo. If I renter this command then the gzip works. If this just some small glitch in some config file that has already been fixed? If it has not been fixed, or no one knows, what file show I look into to correct this myself? I am running 5.1 with my cvs tag set to current. The error occurs about 38 minutes into the build, so I would be glad to try suggestions but I don't want to waste a day on this. Thanks, Jason First rule of thumb is to re-cvsup src-all after you have waited awhile. If that doesn't work, include the error messages. As a follow up, I cvsuped using a mirror what was updated at 1820UTC and had no problem doing a buildworld with 5-current. Kent If you are following -current, you should also be subscribed to the lists that deal with problems, such as cvs-all, hackers, -current, and etc. You can see the problem being addressed and then fixed. This used to be part of the suggested requirements for following stable and they definitely apply to current. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: buildworld error
Hey people, I just had this problem. Here's what worked for me: rm -r /usr/obj cd /usr/src make world HTH Eric F Crist President AdTech Integrated Systems, Inc (952) 403-9000 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Stewart Sent: Saturday, November 08, 2003 2:27 PM To: Jason; [EMAIL PROTECTED] Subject: Re: buildworld error On Saturday 08 November 2003 12:10 pm, Jason wrote: Last night I updated all my source files to buildworld, but ran into a problem. I tried to build it 3 times, and each time it stops at the same spot. If I retype the last commands show letter for letter they work. It stops at something like $gzip -cn cvs.info cvs.info.gz. If I immediately enter this command after the error it does not work, but above it is a 3 line command for makeinfo. If I renter this command then the gzip works. If this just some small glitch in some config file that has already been fixed? If it has not been fixed, or no one knows, what file show I look into to correct this myself? I am running 5.1 with my cvs tag set to current. The error occurs about 38 minutes into the build, so I would be glad to try suggestions but I don't want to waste a day on this. Thanks, Jason First rule of thumb is to re-cvsup src-all after you have waited awhile. If that doesn't work, include the error messages. If you are following -current, you should also be subscribed to the lists that deal with problems, such as cvs-all, hackers, -current, and etc. You can see the problem being addressed and then fixed. This used to be part of the suggested requirements for following stable and they definitely apply to current. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [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 error
Eric F Crist President AdTech Integrated Systems, Inc (952) 403-9000 -Original Message- From: Minnesota Slinky [mailto:[EMAIL PROTECTED] Sent: Saturday, November 08, 2003 9:38 PM To: 'Kent Stewart'; 'Jason'; '[EMAIL PROTECTED]' Subject: RE: buildworld error Hey people, I just had this problem. Here's what worked for me: rm -r /usr/obj cd /usr/src make world HTH Eric F Crist President AdTech Integrated Systems, Inc (952) 403-9000 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Stewart Sent: Saturday, November 08, 2003 2:27 PM To: Jason; [EMAIL PROTECTED] Subject: Re: buildworld error On Saturday 08 November 2003 12:10 pm, Jason wrote: Last night I updated all my source files to buildworld, but ran into a problem. I tried to build it 3 times, and each time it stops at the same spot. If I retype the last commands show letter for letter they work. It stops at something like $gzip -cn cvs.info cvs.info.gz. If I immediately enter this command after the error it does not work, but above it is a 3 line command for makeinfo. If I renter this command then the gzip works. If this just some small glitch in some config file that has already been fixed? If it has not been fixed, or no one knows, what file show I look into to correct this myself? I am running 5.1 with my cvs tag set to current. The error occurs about 38 minutes into the build, so I would be glad to try suggestions but I don't want to waste a day on this. Thanks, Jason First rule of thumb is to re-cvsup src-all after you have waited awhile. If that doesn't work, include the error messages. If you are following -current, you should also be subscribed to the lists that deal with problems, such as cvs-all, hackers, -current, and etc. You can see the problem being addressed and then fixed. This used to be part of the suggested requirements for following stable and they definitely apply to current. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [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 ERROR CODE 2
Thanks guys, I'm going to try again. (fortunately this is not a production server) 1 noteable incident. When I tried to install the system the first time I selected Linux Compat. I just started the install again and when it tries to install the Linux~~.bz the installer crashes and says it had a build error. I click OK and it finishes the installaion. My mind is a bit foggy but it seems like that happened the first time too. So I reinstall select install everything no error... next I load cvsup from the ports. now I will try and buildworld again. this time without the -j option. wish me luck. -Original Message- From: Kent Stewart [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:16 PM To: Duke, Brian; [EMAIL PROTECTED] Subject: Re: Buildworld ERROR CODE 2 This looks like one of those problems they have been dealing with on -current. They changed the -std option and I think you need to re-cvsup and start over. The old rule on make.conf is that if you add something and it doesn't work. Comment it out and start over. I think you have dug a deep hole and fell in. I don't have any idea on the solution. Kent -Original Message- From: Joshua Oreman [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 10:35 PM To: Duke, Brian Subject: Re: Buildworld ERROR CODE 2 I am in single user mode. Someone please help. I am NOT good enough to troubleshoot this. Try re-running your buildworld without any -j option. -- Josh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Buildworld ERROR CODE 2
I think you may have the answer Kent... in my make.conf I did allow the SUP = YES directives from the example file /usr/share/examples/etc/make.conf I just took that section out based on your recommendation below. So the only things in my make is now: PERL5 module stuff that was already enabled in make.conf after FTP intallation and CPUTYPE=i586. The config seems to be working. Thanks for your help. I would have never suspected the CVSUP section. I'll run cvsup again in the future when I don't need sleep. -Original Message- From: Kent Stewart [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:16 PM To: Duke, Brian; [EMAIL PROTECTED] Subject: Re: Buildworld ERROR CODE 2 On Monday 16 June 2003 09:02 pm, Duke, Brian wrote: ok I didn't get an answer on my first email so I tried to do a complete buildworld here is a transcript of the output: install -C -o root -g wheel -m 444 libc_pic.a /usr/obj/usr/src/i386/usr/lib 1 error I made only moderate changes to the make.conf...like my CPUBuild=i586. This looks like one of those problems they have been dealing with on -current. They changed the -std option and I think you need to re-cvsup and start over. The old rule on make.conf is that if you add something and it doesn't work. Comment it out and start over. I think you have dug a deep hole and fell in. I don't have any idea on the solution. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld ERROR CODE 2
On Tue, Jun 17, 2003 at 04:23:10AM -0600 or thereabouts, Duke, Brian seemed to write: I think you may have the answer Kent... in my make.conf I did allow the SUP = YES directives from the example file /usr/share/examples/etc/make.conf I just took that section out based on your recommendation below. So the only things in my make is now: PERL5 module stuff that was already enabled in make.conf after FTP intallation and CPUTYPE=i586. The config seems to be working. Thanks for your help. I would have never suspected the CVSUP section. I'll run cvsup again in the future when I don't need sleep. People often feel that they need to reinstall in cases such as this. YOU DON'T HAVE TO. Just rm -rf /usr/obj, re-cvsup, and make buildworld again. -- Josh -Original Message- From: Kent Stewart [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 11:16 PM To: Duke, Brian; [EMAIL PROTECTED] Subject: Re: Buildworld ERROR CODE 2 On Monday 16 June 2003 09:02 pm, Duke, Brian wrote: ok I didn't get an answer on my first email so I tried to do a complete buildworld here is a transcript of the output: install -C -o root -g wheel -m 444 libc_pic.a /usr/obj/usr/src/i386/usr/lib 1 error I made only moderate changes to the make.conf...like my CPUBuild=i586. This looks like one of those problems they have been dealing with on -current. They changed the -std option and I think you need to re-cvsup and start over. The old rule on make.conf is that if you add something and it doesn't work. Comment it out and start over. I think you have dug a deep hole and fell in. I don't have any idea on the solution. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [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 ERROR CODE 2
On Monday 16 June 2003 09:02 pm, Duke, Brian wrote: ok I didn't get an answer on my first email so I tried to do a complete buildworld here is a transcript of the output: ranlib libc_pic.a ranlib libc_p.a ranlib libc.a install -C -C -o root -g wheel -m 444 libc.a /usr/obj/usr/src/i386/usr/lib install -C -C -o root -g wheel -m 444 libc_p.a /usr/obj/usr/src/i386/usr/lib install -C -s -o root -g wheel -m 444 libc.so.5 /usr/obj/usr/src/i386/usr/lib ln -fs libc.so.5 /usr/obj/usr/src/i386/usr/lib/libc.so install -C -o root -g wheel -m 444 libc_pic.a /usr/obj/usr/src/i386/usr/lib 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 I made only moderate changes to the make.conf...like my CPUBuild=i586. I am in single user mode. Someone please help. I am NOT good enough to troubleshoot this. -Original Message- From: Duke, Brian Sent: Monday, June 16, 2003 2:57 AM To: '[EMAIL PROTECTED]' Subject:/usr/src/sys/dev/en/midway.c:1607: dereferencing pointer to incomplete type I cannot seem to rebuild my kernel. I wanted to get my sound card working so I included the device pcm directive in my kernel config and I got an error as below.. I could use a hand here if somone has seen this kind of error. Here is the end of the output of the failed compile rain# cd /usr/src rain# make buildkernel KERNCONF=RAINBUILD error: === en cc -O -pipe -mcpu=pentiumpro -DENABLE_BPF -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast- qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev This looks like one of those problems they have been dealing with on -current. They changed the -std option and I think you need to re-cvsup and start over. The old rule on make.conf is that if you add something and it doesn't work. Comment it out and start over. I think you have dug a deep hole and fell in. I don't have any idea on the solution. Kent -I@/../include -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffre estanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/ src/sys/pci/if_en_pci.c cc -O -pipe -mcpu=pentiumpro -DENABLE_BPF -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast- qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffre estanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/ src/sys/dev/en/midway.c /usr/src/sys/dev/en/midway.c: In function `en_get_vccs': /usr/src/sys/dev/en/midway.c:1474: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1474: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1479: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1480: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1488: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1492: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1493: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1493: `ATMIO_FLAG_PVC' undeclared (first use in this function) /usr/src/sys/dev/en/midway.c:1493: (Each undeclared identifier is reported only once /usr/src/sys/dev/en/midway.c:1493: for each function it appears in.) /usr/src/sys/dev/en/midway.c:1494: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1495: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1497: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1497: `ATMIO_AAL_5' undeclared (first use in this function) /usr/src/sys/dev/en/midway.c:1499: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1499: `ATMIO_AAL_0' undeclared (first use in this function) /usr/src/sys/dev/en/midway.c:1500: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1500: `ATMIO_TRAFFIC_UBR' undeclared (first use in this function) /usr/src/sys/dev/en/midway.c:1501: dereferencing pointer to incomplete type /usr/src/sys/dev/en/midway.c:1502: increment of pointer to unknown structure /usr/src/sys/dev/en/midway.c:1502: arithmetic on pointer to an incomplete type /usr/src/sys/dev/en/midway.c: In function `en_ioctl': /usr/src/sys/dev/en/midway.c:1591: `SIOCATMGETVCCS' undeclared (first use in this function) /usr/src/sys/dev/en/midway.c:1600: `SIOCATMGVCCS' undeclared (first use in this function) /usr/src/sys/dev/en/midway.c:1606: dereferencing pointer to incomplete type
Re: Buildworld Error
On Thu, Jan 30, 2003 at 09:19:20AM -0500, Justin P. Michel wrote: The system in question is a lousy Cyrix 6x86 PR166+, with 64MB RAM, and a 4GB HDD. The error it shoots out is: -- cc: Internal compiler error: Program cc1 got fatal signal 11 That's a FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 but considering the rest of your post and the age of your equipment, I'd say it's probably hardware failure. Try running memtest86 (http://www.memtest86.com/) against your system to see if it can confirm what I think. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Buildworld Error
On Thursday 30 January 2003 06:37 am, Matthew Seaman wrote: On Thu, Jan 30, 2003 at 09:19:20AM -0500, Justin P. Michel wrote: The system in question is a lousy Cyrix 6x86 PR166+, with 64MB RAM, and a 4GB HDD. The error it shoots out is: -- cc: Internal compiler error: Program cc1 got fatal signal 11 That's a FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.htm l#SIGNAL11 but considering the rest of your post and the age of your equipment, I'd say it's probably hardware failure. Try running memtest86 (http://www.memtest86.com/) against your system to see if it can confirm what I think. There is nothing there at the moment. You have an empty directory for webalizer and that is it. Kent Cheers, Matthew -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: buildworld error
Dear/Beste Daniel, Thursday, January 9, 2003, 3:34:37 PM, you wrote: I see no error here...so I'm sort of at a loss...anyone seen this before? Any help greatly appreciated, I'm leaving town today, and want to leave the box in top shape. Did you compile using the j option? (like make -j4) If so remove this this one time. -- Best regards/Met vriendelijke groet, Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Buildworld error
On Wed, 16 Oct 2002, Bryce Newall wrote: I checked on vgrind and only the Makefile has changed in the last year. I wonder if you have corrupted sources for it. You could always cd /usr/src/usr.bin/vgrind and try rebuilding it and see if that helps. Otherwise, I would remove everything in the vgrind directory, re-cvsup 4-stable, and try doing a buildworld again. I'll give that a try and let you know what happens. Thanks! Just a follow-up...after a lot of experimenting with different versions of FreeBSD, I ended up doing 4.7 again. I must have gotten a bad install the first time, because the second time around everything worked great. Thanks for the help! * *Bryce Newall*Email: [EMAIL PROTECTED]* * www.dreamhaven.org/~data* * Computers make very fast, very accurate mistakes. * * To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Buildworld error
Bryce Newall wrote: Hi all, I am running into some difficulty trying to upgrade my system (a freshly-installed FreeBSD 4.7-RELEASE system) to 4.7-STABLE. About 45 minutes into the buildworld process, it bombs out with the following: === share/doc/papers/fsinterface touch _stamp.extraobjs (cd /usr/src/share/doc/papers/fsinterface; groff -mtty-char -Tascii -t -ms -o1- /usr/src/share/doc/papers/fsinterface/fsinterface.ms) | gzip -cn fsinterface.ascii.gz === share/doc/papers/jail touch _stamp.extraobjs (cd /usr/src/share/doc/papers/jail; groff -mtty-char -Tascii -ms -o1- /usr/src/share/doc/papers/jail/paper.ms) | gzip -cn jail.ascii.gz === share/doc/papers/kernmalloc (cd /usr/src/share/doc/papers/kernmalloc; soelim kernmalloc.t) kernmalloc.ms vgrind -f /usr/src/share/doc/papers/kernmalloc/appendix.t appendix.ms elf_load_section: truncated ELF file Abort trap *** Error code 134 Stop in /usr/src/share/doc/papers/kernmalloc. *** Error code 1 Stop in /usr/src/share/doc/papers. *** Error code 1 Stop in /usr/src/share/doc. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. That truncated ELF file is what is concerning me, but I don't know what to check for. Any help will be greatly appreciated. Thanks!! FWIW, the kernmalloc.ms line appears 92% of the way into the build. You could have some sort of hardware failure that is dying with the truncation error instead of giving you a signal error and dying. An HD that is overheating or something similar. Did you try the buildworld more than once? I checked on vgrind and only the Makefile has changed in the last year. I wonder if you have corrupted sources for it. You could always cd /usr/src/usr.bin/vgrind and try rebuilding it and see if that helps. Otherwise, I would remove everything in the vgrind directory, re-cvsup 4-stable, and try doing a buildworld again. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Buildworld error
On Wed, 16 Oct 2002, Kent Stewart wrote: FWIW, the kernmalloc.ms line appears 92% of the way into the build. Doh! Hate when it dies so close to the end... You could have some sort of hardware failure that is dying with the truncation error instead of giving you a signal error and dying. An HD that is overheating or something similar. Did you try the buildworld more than once? 3 times, actually, and it failed in the same place every time. With that in mind, I'm pretty sure it's not a hardware problem (though I've run into those before, too... usually I get a signal 10 or 11 with that). I checked on vgrind and only the Makefile has changed in the last year. I wonder if you have corrupted sources for it. You could always cd /usr/src/usr.bin/vgrind and try rebuilding it and see if that helps. Otherwise, I would remove everything in the vgrind directory, re-cvsup 4-stable, and try doing a buildworld again. I'll give that a try and let you know what happens. Thanks! * *Bryce Newall*Email: [EMAIL PROTECTED]* * www.dreamhaven.org/~data* * Computers make very fast, very accurate mistakes. * * To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
