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