Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
Thus spake Garance A Drosihn ([EMAIL PROTECTED]) [06/12/03 03:31]: From the above description, it sounds like you are running on a 5.1 system, and you are trying to compile a 5.2 kernel. Is this true? If the system you are on is 5.1, then you are going to have to do a 'make buildworld' of the 5.2-source before you can do a 'make buildkernel' of a 5.2 kernel. It's not clear from what you're saying, but will this cause problems with the statfs stuff? I've been under the impression that a 5.1-5.2 upgrade requires me to build and boot a new kernel before I can install a new world -- it's not clear if you're saying I need to build /and install/ a new world before building a kernel, or if I just need to build world... - Damian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
On Mon, Dec 08, 2003 at 12:41:26PM -0500, Damian Gerow wrote: Thus spake Garance A Drosihn ([EMAIL PROTECTED]) [06/12/03 03:31]: From the above description, it sounds like you are running on a 5.1 system, and you are trying to compile a 5.2 kernel. Is this true? If the system you are on is 5.1, then you are going to have to do a 'make buildworld' of the 5.2-source before you can do a 'make buildkernel' of a 5.2 kernel. It's not clear from what you're saying, but will this cause problems with the statfs stuff? I've been under the impression that a 5.1-5.2 upgrade requires me to build and boot a new kernel before I can install a new world -- it's not clear if you're saying I need to build /and install/ a new world before building a kernel, or if I just need to build world... Just build, as all the documentation (UPDATING, handbook, ...) says. buildworld builds a copy of any updated tools that are needed to bootstrap the rest of the upgrade process, for example a new make. Kris pgp0.pgp Description: PGP signature
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
Thus spake Kris Kennaway ([EMAIL PROTECTED]) [08/12/03 13:18]: It's not clear from what you're saying, but will this cause problems with the statfs stuff? I've been under the impression that a 5.1-5.2 upgrade requires me to build and boot a new kernel before I can install a new world -- it's not clear if you're saying I need to build /and install/ a new world before building a kernel, or if I just need to build world... Just build, as all the documentation (UPDATING, handbook, ...) says. Thanks for clearing that up. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
At 12:41 PM -0500 12/8/03, Damian Gerow wrote: Thus spake Garance A Drosihn ([EMAIL PROTECTED]) [06/12/03 03:31]: From the above description, it sounds like you are running on a 5.1 system, and you are trying to compile a 5.2 kernel. Is this true? If the system you are on is 5.1, then you are going to have to do a 'make buildworld' of the 5.2-source before you can do a 'make buildkernel' of a 5.2 kernel. It's not clear from what you're saying, but will this cause problems with the statfs stuff? I've been under the impression that a 5.1-5.2 upgrade requires me to build and boot a new kernel before I can install a new world -- it's not clear if you're saying I need to build /and install/ a new world before building a kernel, or if I just need to build world... My comments were not trying to cover the installation steps. All I said was that you have to do a BUILDworld before you do a BUILDkernel, because it sounded to me like you might have been building a 5.2 kernel without doing any matching buildworld. You can get through the statfs changes by following the standard recommended buildinstall order. The standard recommended order is: make buildworld make buildkernel make installkernel reboot into single user mode mergemaster -p make installworld mergemaster reboot into nicely-upgraded system Many developers have gotten away with shortening this list, or with an alternate order. For the statfs change, it is particularly important that the proper order be followed. For this change, you really need to do that installkernel and *reboot* before doing the installworld. depressing aside Oh, and due to a small-but-significant bug in one of the makefiles, you would be well advised to make sure that you do not set the 'DISTDIR' variable. You might have that set in /etc/make.conf, expecting it to be used by the *ports* collection. Right now there is a problem where it is also checked during installworld, and the makefile will not do the right thing if that is set. We hope to have that sorted out very soon... /depressing -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
Thus spake Garance A Drosihn ([EMAIL PROTECTED]) [08/12/03 13:40]: It's not clear from what you're saying, but will this cause problems with the statfs stuff? I've been under the impression that a 5.1-5.2 upgrade requires me to build and boot a new kernel before I can install a new world -- it's not clear if you're saying I need to build /and install/ a new world before building a kernel, or if I just need to build world... My comments were not trying to cover the installation steps. All I said was that you have to do a BUILDworld before you do a BUILDkernel, because it sounded to me like you might have been building a 5.2 kernel without doing any matching buildworld. And my request for clarification was as a result of you not mentioning any of the install steps -- I (having recently botched a 5.1-5.2-BETA upgrade) didn't know if you were /insinuating/ an installworld, or if you left it out because it wasn't to be done. Hence my request. But this has all been cleared up now -- thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
* Damian Gerow [EMAIL PROTECTED] [031208 12:43]: Thus spake Garance A Drosihn ([EMAIL PROTECTED]) [06/12/03 03:31]: From the above description, it sounds like you are running on a 5.1 system, and you are trying to compile a 5.2 kernel. Is this true? If the system you are on is 5.1, then you are going to have to do a 'make buildworld' of the 5.2-source before you can do a 'make buildkernel' of a 5.2 kernel. It's not clear from what you're saying, but will this cause problems with the statfs stuff? I've been under the impression that a 5.1-5.2 upgrade requires me to build and boot a new kernel before I can install a new world -- it's not clear if you're saying I need to build /and install/ a new world before building a kernel, or if I just need to build world... You basically need to follow the recommended procedure to the letter, as opposed to skipping some of the reboot steps in the middle. with a 5.2 /usr/src: * make buildworld * make buildkernel * make installkernel * reboot to single-user * make installkernel * mergemaster * reboot The issue is, your kernel will continue handing out old file system structures until you reboot with a new one. Rather early in the installworld process, you will stop being able to use fundamental system commands like ls and cp, which expect the new structures. Also, a small number of ports break as well. Between the mergemaster and reboot steps you may wish to rebuild any critical ports. postfix, for example, refuses to start it's smtpd until you rebuild it. Any other ports which behave oddly, particularly those which die with a signal 11, probably need a rebuild. --Mike pgp0.pgp Description: PGP signature
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
Thus spake Michael Edenfield ([EMAIL PROTECTED]) [08/12/03 17:28]: with a 5.2 /usr/src: * make buildworld * make buildkernel * make installkernel * reboot to single-user * make installkernel * mergemaster * reboot I think you want that second 'installkernel' to actually be an 'installkernel'. The issue is, your kernel will continue handing out old file system structures until you reboot with a new one. Rather early in the installworld process, you will stop being able to use fundamental system commands like ls and cp, which expect the new structures. According to the posts by Mr. McKusick, the new kernel should be able to understand both the old and the new structures -- so cp should *not* break. So long as you follow his instructions, and reboot with the new kernel before doing the installworld. Also, a small number of ports break as well. Between the mergemaster and reboot steps you may wish to rebuild any critical ports. postfix, for example, refuses to start it's smtpd until you rebuild it. Any other ports which behave oddly, particularly those which die with a signal 11, probably need a rebuild. Yes, I ran into that as well. I gave up on guessing which ports needed to be re-compiled, and just did a portupgrade -fa, and went to bed. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
On 2003-12-08 at 23:50:03 Damian Gerow wrote: * make buildworld * make buildkernel * make installkernel * reboot to single-user * make installkernel * mergemaster * reboot I think you want that second 'installkernel' to actually be an 'installkernel'. I'd advise some more coffee, you probably meant 'installworld' on the second instance. ;) Btw, I've also seen some reports, and experienced, that the first make installkernel can also fail with signal 12's, probably due to the new 'install' executable using some not-yet-available system calls. If you are stuck in this case, you can manually copy the kernel file to its destination, boot from it in single user mode, and run installkernel from there. That saved my neck, at least... pgp0.pgp Description: PGP signature
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
Thus spake Dimitry Andric ([EMAIL PROTECTED]) [08/12/03 18:01]: I think you want that second 'installkernel' to actually be an 'installkernel'. I'd advise some more coffee, you probably meant 'installworld' on the second instance. ;) Oh wow. Thanks. I'll go find my caffeine drip... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
FBSD 5-CURRENT: Kernel Makefile.inc1 Error
Hey there! I'm having a slight problem performing a build on my FreeBSD 5.1
machine. I downloaded the 5-CURRENT source code and only added the line,
device pcm to the GENERIC kernel, renaming it to ZEUS.
Then, I went into /usr/src and typed make buildkernel KERNCONF=ZEUS, and it
immediately came up with the errors:
--
-su-2.05b# make buildkernel
/usr/src/Makefile.inc1, line 745: warning: String comparison operator should be
either == or !=
/usr/src/Makefile.inc1, line 745: Malformed conditional ((!defined(NO_RESCUE) ||
defined(RELEASEDIR)) (${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING}
501101))
/usr/src/Makefile.inc1, line 745: Need an operator
/usr/src/Makefile.inc1, line 747: if-less endif
/usr/src/Makefile.inc1, line 747: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1
Stop in /usr/src.
--
The problem is with ${BOOTSTRAPING} 501101). For some reason, it is
suddenly expecting BOOSTRAPPING to be a string, when it is apparent earlier in
the Makefile.inc1 that it is not.
I tried patching this on my own but failed; would someone more experienced
be able to patch this for me?
I have attached my dmesg and Makefile.inc1 to this as well just in case
someone wishes to view them.
--
William Michael Grim
Student, Southern Illinois University at Edwardsville
Unix Network Administrator, SIUE, Computer Science dept.
Phone: (217) 341-6552
Email: [EMAIL PROTECTED]
#
# $FreeBSD: src/Makefile.inc1,v 1.397 2003/11/16 21:17:43 gordon Exp $
#
# Make command line options:
# -DNO_DYNAMICROOT do not link /bin and /sbin dynamically
# -DNO_KERBEROS Do not build Heimdal (Kerberos 5)
# -DNO_RESCUE do not build rescue binaries
# -DNOCLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir
# -DNOCLEAN do not clean at all
# -DNOCRYPT will prevent building of crypt versions
# -DNOMAN do not build the manual pages
# -DNOPROFILE do not build profiled libraries
# -DNOGAMES do not go into games subdir
# -DNOSHARE do not go into share subdir
# -DNOINFO do not make or install info files
# -DNOLIBC_R do not build libc_r.
# -DNO_FORTRAN do not build g77 and related libraries.
# -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel
# -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel
# -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel
# -DNO_PORTSUPDATE do not update ports in ${MAKE} update
# -DNO_DOCUPDATE do not update doc in ${MAKE} update
# LOCAL_DIRS=list of dirs to add additional dirs to the SUBDIR list
# TARGET_ARCH=arch to crossbuild world to a different arch
#
# The intended user-driven targets are:
# buildworld - rebuild *everything*, including glue to help do upgrades
# installworld- install everything built by buildworld
# update - convenient way to update your source tree (eg: sup/cvs)
#
# Standard targets (not defined here) are documented in the makefiles in
# /usr/share/mk. These include:
# obj depend all install clean cleandepend cleanobj
# Put initial settings here.
SUBDIR=
# We must do share/info early so that installation of info `dir'
# entries works correctly. Do it first since it is less likely to
# grow dependencies on include and lib than vice versa.
.if exists(${.CURDIR}/share/info)
SUBDIR+= share/info
.endif
.if exists(${.CURDIR}/include)
SUBDIR+= include
.endif
.if exists(${.CURDIR}/lib)
SUBDIR+= lib
.endif
# When upgrading to a dynamically linked root, install the runtime
# linker early into its new location before make(1) has a chance
# to run the dynamically linked /bin/sh.
.if !defined(NO_DYNAMICROOT) !defined(NOPIC) \
(!defined(TARGET_ARCH) || ${TARGET_ARCH} == ${MACHINE_ARCH}) \
!defined(DISTDIR) \
(!defined(DESTDIR) || empty(DESTDIR) || ${DESTDIR} == /) \
!exists(/libexec/ld-elf.so.1)
SUBDIR+= libexec/rtld-elf
.endif
.if exists(${.CURDIR}/bin)
SUBDIR+= bin
.endif
.if exists(${.CURDIR}/games) !defined(NOGAMES)
SUBDIR+= games
.endif
.if exists(${.CURDIR}/gnu)
SUBDIR+= gnu
.endif
.if exists(${.CURDIR}/kerberos5) exists(${.CURDIR}/crypto) \
!defined(NOCRYPT) !defined(NO_OPENSSL) !defined(NO_KERBEROS)
SUBDIR+= kerberos5
.endif
.if exists(${.CURDIR}/libexec)
SUBDIR+= libexec
.endif
.if exists(${.CURDIR}/rescue) !defined(NO_RESCUE)
SUBDIR+= rescue
.endif
.if exists(${.CURDIR}/sbin)
SUBDIR+= sbin
.endif
.if exists(${.CURDIR}/secure) !defined(NOCRYPT)
SUBDIR+= secure
.endif
.if exists(${.CURDIR}/share) !defined(NOSHARE)
SUBDIR+= share
.endif
.if exists(${.CURDIR}/sys)
SUBDIR+= sys
.endif
.if exists(${.CURDIR}/usr.bin)
SUBDIR+= usr.bin
.endif
.if exists(${.CURDIR}/usr.sbin)
SUBDIR+= usr.sbin
.endif
# etc must be last for distribute to work
.if exists(${.CURDIR}/etc)
SUBDIR+= etc
.endif
# These are last, since it is nice to at least get the base system
# rebuilt
Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error
At 1:45 AM -0600 12/6/03, William M. Grim wrote: Hey there! I'm having a slight problem performing a build on my FreeBSD 5.1 machine. I downloaded the 5-CURRENT source code and only added the line, device pcm to the GENERIC kernel, renaming it to ZEUS. Then, I went into /usr/src and typed make buildkernel KERNCONF=ZEUS, and it immediately came up with the errors [...] From the above description, it sounds like you are running on a 5.1 system, and you are trying to compile a 5.2 kernel. Is this true? If the system you are on is 5.1, then you are going to have to do a 'make buildworld' of the 5.2-source before you can do a 'make buildkernel' of a 5.2 kernel. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
