Re: make release fails...
On Fri, Sep 13, 2013 at 11:21:43AM +0900, Lundberg, Johannes wrote: Trying to create a custom install image which has been successful before but suddenly fails during make release/memstick. Procedure 1) cd /usr/src 2) make buildworld 3) make buildkernel 4) cd release 5) make release and I get the error ... gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg make[8]: exec(gencat) failed (no such file or directory) This is not enough context. Also, what is output of 'sysctl -n kern.osreldate' on the build host, and which branch and revision are you trying to build? Glen pgpWdgLPdVDMT.pgp Description: PGP signature
make release fails...
Hi Trying to create a custom install image which has been successful before but suddenly fails during make release/memstick. Procedure 1) cd /usr/src 2) make buildworld 3) make buildkernel 4) cd release 5) make release and I get the error ... gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg make[8]: exec(gencat) failed (no such file or directory) -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: make release fails...
# sysctl -n kern.osreldate 145 The system is 10.0. I used it before to build custom distribution. What I've done since last time is basically removing /usr/src and grabbing a new one from head. -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:27 AM, Glen Barber g...@freebsd.org wrote: On Fri, Sep 13, 2013 at 11:21:43AM +0900, Lundberg, Johannes wrote: Trying to create a custom install image which has been successful before but suddenly fails during make release/memstick. Procedure 1) cd /usr/src 2) make buildworld 3) make buildkernel 4) cd release 5) make release and I get the error ... gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg make[8]: exec(gencat) failed (no such file or directory) This is not enough context. Also, what is output of 'sysctl -n kern.osreldate' on the build host, and which branch and revision are you trying to build? Glen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: make release fails...
On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote: # sysctl -n kern.osreldate 145 The system is 10.0. I used it before to build custom distribution. What I've done since last time is basically removing /usr/src and grabbing a new one from head. Recent changes in head/ (unfortunately) require the build system revision to be at least 155 or greater, due to some backward compatibility issues introduced recently. If you upgrade the build environment and retry the build, you should be fine. (And yes, I am serious, as I've just spent several hours on exactly these types of issues...) Glen pgpMRrq2veMKk.pgp Description: PGP signature
Re: make release fails...
Is this perhaps related to the 20130905 post in UPDATING, regarding the Capsicum framework? -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:37 AM, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Oh.. Thanks a lot! But please tell me, how can I upgrade the build environment? Do I have to rebuild world and kernel on the host system? -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber g...@freebsd.org wrote: On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote: # sysctl -n kern.osreldate 145 The system is 10.0. I used it before to build custom distribution. What I've done since last time is basically removing /usr/src and grabbing a new one from head. Recent changes in head/ (unfortunately) require the build system revision to be at least 155 or greater, due to some backward compatibility issues introduced recently. If you upgrade the build environment and retry the build, you should be fine. (And yes, I am serious, as I've just spent several hours on exactly these types of issues...) Glen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: make release fails...
Oh.. Thanks a lot! But please tell me, how can I upgrade the build environment? Do I have to rebuild world and kernel on the host system? -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber g...@freebsd.org wrote: On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote: # sysctl -n kern.osreldate 145 The system is 10.0. I used it before to build custom distribution. What I've done since last time is basically removing /usr/src and grabbing a new one from head. Recent changes in head/ (unfortunately) require the build system revision to be at least 155 or greater, due to some backward compatibility issues introduced recently. If you upgrade the build environment and retry the build, you should be fine. (And yes, I am serious, as I've just spent several hours on exactly these types of issues...) Glen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: make release fails...
Yes, the buildworld/buildkernel. Glen On Fri, Sep 13, 2013 at 11:37:38AM +0900, Lundberg, Johannes wrote: Oh.. Thanks a lot! But please tell me, how can I upgrade the build environment? Do I have to rebuild world and kernel on the host system? -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber g...@freebsd.org wrote: On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote: # sysctl -n kern.osreldate 145 The system is 10.0. I used it before to build custom distribution. What I've done since last time is basically removing /usr/src and grabbing a new one from head. Recent changes in head/ (unfortunately) require the build system revision to be at least 155 or greater, due to some backward compatibility issues introduced recently. If you upgrade the build environment and retry the build, you should be fine. (And yes, I am serious, as I've just spent several hours on exactly these types of issues...) Glen pgpivCirxcKq9.pgp Description: PGP signature
Re: make release fails...
In part, yes. Glen On Fri, Sep 13, 2013 at 11:41:54AM +0900, Lundberg, Johannes wrote: Is this perhaps related to the 20130905 post in UPDATING, regarding the Capsicum framework? -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:37 AM, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: Oh.. Thanks a lot! But please tell me, how can I upgrade the build environment? Do I have to rebuild world and kernel on the host system? -- Johannes Lundberg Project leader and lead developer of Mirama OS (previously Viking OS) BRILLIANTSERVICE CO., LTD. My blog http://brilliantobjc.blogspot.com Mirama homepage http://www.brilliantservice.co.jp/viking/ bloghttp://hmdviking.blogspot.jp Company homepage http://www.brilliantservice.co.jp On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber g...@freebsd.org wrote: On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote: # sysctl -n kern.osreldate 145 The system is 10.0. I used it before to build custom distribution. What I've done since last time is basically removing /usr/src and grabbing a new one from head. Recent changes in head/ (unfortunately) require the build system revision to be at least 155 or greater, due to some backward compatibility issues introduced recently. If you upgrade the build environment and retry the build, you should be fine. (And yes, I am serious, as I've just spent several hours on exactly these types of issues...) Glen pgppIC6i58N_J.pgp Description: PGP signature
make release fails building floppies ...
I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: if [ -d /R/stage/driversfd ]; then sh -e /usr/local/5.0/src/release/scripts/doFS.sh /R/stage/floppies/drivers.flp /R/stage /mnt 1440 /R/stage/driversfd 4 fd1440; cd /R/stage/driversfd awk -f /usr/local/5.0/src/release/scripts/driver-desc.awk *.dsc /R/stage/floppies/DRIVERS.TXT; fi /dev/md3c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 2 cylinder groups of 1.22MB, 312 blks, 32 inodes. super-block backups (for fsck -b #) at: 32, 2528 1871 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md3c 1391 987 40471% 3329 53% /mnt *** Filesystem is 1440 K, 404 left *** 4 bytes/inode, 29 left sh -e /usr/local/5.0/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 4320 /R/stage/mfsfd 8000 minimum3 /dev/md3c: 4.2MB (8640 sectors) block size 4096, fragment size 512 using 4 cylinder groups of 1.06MB, 271 blks, 160 inodes. super-block backups (for fsck -b #) at: 32, 2200, 4368, 6536 6496 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/md3c 4175 3309 86679% 96 542 15% /mnt *** Filesystem is 4320 K, 866 left *** 8000 bytes/inode, 542 left mfsroot: 67.4% /dev/md3c: 1.4MB (2880 sectors) block size 4096, fragment size 512 using 1 cylinder groups of 1.41MB, 360 blks, 32 inodes. super-block backups (for fsck -b #) at: 32 /mnt: write failed, filesystem is full cp: /mnt/mfsroot.gz: No space left on device *** Error code 1 I ran 'make release' as: make relesae \ CHROOTDIR=/usr/local/release \ BUILDNAME=vaio \ [EMAIL PROTECTED]:/home/ncvs \ RELEASETAG=RELENG_5_0 \ NODOC=YES \ KERNEL_FLAGS=-j 5 \ NOPORTS=YES \ WORLD_FLAGS=-j 5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release fails building floppies ...
* De: Marc G. Fournier [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: make release fails building floppies ... ] I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: This is probably my fault, since tunefs(8) needs libufs now. Converting other things that could use it that are on the floppies to use libufs would be a start. My newfs changes might be enough. -- Juli Mallett [EMAIL PROTECTED] AIM: BSDFlata -- IRC: juli on EFnet. OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release fails building floppies ...
got it ... figured out how the mfsfd/modules is generated, and just trim'd down the driver.conf file to the bare essentials ... On Thu, 23 Jan 2003, Juli Mallett wrote: * De: Marc G. Fournier [EMAIL PROTECTED] [ Data: 2003-01-23 ] [ Subjecte: make release fails building floppies ... ] I'm slowly getting closer, but am not quite there yet :( I'm at the stage where its building teh floppies, but its telling me that the md devices are out of disk space: This is probably my fault, since tunefs(8) needs libufs now. Converting other things that could use it that are on the floppies to use libufs would be a start. My newfs changes might be enough. -- Juli Mallett [EMAIL PROTECTED] AIM: BSDFlata -- IRC: juli on EFnet. OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make release fails
Hiho, I'm using a 3.1-STABLE system, up to date with a current CVS-tree. No I would like to install a few other boxes as well, so I thought 'make release' would be the thing. I set the RELEASETAG to RELENG_3, make release then seems to run fine, until it wants to build kerberosIV. This fails with 'don't know how to make k_getpwuid.c' (or similar). Now the thing is, I'm not USA_RESDIDENT, so I don't have Kerberos installed, and I don't want it in the release anyway. I tried to set 'NOKERBEROS', 'NOCRYPT', etc, but it doesn't seem to work. But I have to admit, that I made a 'make rerelease' after the build broke down. I didn't want it to remove the whole chroot-tree and check the whole stuff out again, since this takes AGES (even on my sort of fast machine). If anyone has any hints, how to avoid building kerberos, preferrably without having to do a 'make release' and set the trees up from scratch again, I would be grateful. Any other general hints for 'make release' or some more documentation apart from /usr/src/release/Makefile would be nice, as well. Btw, I'm not subscribed to any of the mailing-lists, I'd rather browse the archives. So if anyone likes to answer, please include a cc: to my personal address, or at least give me hint like 'Watch the ...-list' or 'You _should_ be subscribed to ...'. Cheers, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - RL: Daniel Lang * d...@leo.org * +49 89 8540017 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release fails
Daniel, I'm guessing here, but check your existing make.conf file in /etc against the one in /usr/src/etc/make.conf. I know the newer one has an option MAKE_KERBEROSIV. See if that helps... As far as how to start where it failed, I have no idea..SORRY. I would like to know that myself. later Michael Mercer Daniel Lang wrote: Hiho, I'm using a 3.1-STABLE system, up to date with a current CVS-tree. No I would like to install a few other boxes as well, so I thought 'make release' would be the thing. I set the RELEASETAG to RELENG_3, make release then seems to run fine, until it wants to build kerberosIV. This fails with 'don't know how to make k_getpwuid.c' (or similar). Now the thing is, I'm not USA_RESDIDENT, so I don't have Kerberos installed, and I don't want it in the release anyway. I tried to set 'NOKERBEROS', 'NOCRYPT', etc, but it doesn't seem to work. But I have to admit, that I made a 'make rerelease' after the build broke down. I didn't want it to remove the whole chroot-tree and check the whole stuff out again, since this takes AGES (even on my sort of fast machine). If anyone has any hints, how to avoid building kerberos, preferrably without having to do a 'make release' and set the trees up from scratch again, I would be grateful. Any other general hints for 'make release' or some more documentation apart from /usr/src/release/Makefile would be nice, as well. Btw, I'm not subscribed to any of the mailing-lists, I'd rather browse the archives. So if anyone likes to answer, please include a cc: to my personal address, or at least give me hint like 'Watch the ...-list' or 'You _should_ be subscribed to ...'. Cheers, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - RL: Daniel Lang * d...@leo.org * +49 89 8540017 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make release fails to build floppies.... (no space left)
mv /R/stage/kernels/BOOTMFS /R/stage/image.boot/kernel Getting symbols from /R/stage/image.boot/kernel for mfsroot Writing MFS image into kernel for boot floppy /R/stage/image.boot/kernel: 54.7% -- replaced with /R/stage/image.boot/kern el.gz disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 4. Warning: 2880 sector(s) in last cylinder unallocated /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 Stop. *** Error code 1 (ignored) *** Error code 1 Stop. *** Error code 1 -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make release fails to build floppies.... (no space left)
From: Andreas Klemm andr...@klemm.gtn.com Subject: make release fails to build floppies (no space left) Date: Mon, 18 Jan 1999 06:38:27 +0100 mv /R/stage/kernels/BOOTMFS /R/stage/image.boot/kernel Getting symbols from /R/stage/image.boot/kernel for mfsroot Writing MFS image into kernel for boot floppy /R/stage/image.boot/kernel: 54.7% -- replaced with /R/stage/image.boot/kern el.gz disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 4. Warning: 2880 sector(s) in last cylinder unallocated /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 5760 sectors 1.4MB in 1 cyl groups (4 c/g, 11.25MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 Stop. *** Error code 1 (ignored) *** Error code 1 Stop. *** Error code 1 When did you last CVSup? Jordan made that mistake last week but I'm sure he backed it out. Are you using version src/release/Makefile version 1.459? Good Luck, Jerry Hicks wghi...@bellsouth.net -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
