Re: make release: how utilise filemon?

2017-05-11 Thread Bryan Drewery
( $(( $(sysctl -n hw.ncpu) + 1 )) / 2 ))" > > without any noticable effect - make release always build release fully, no > matter wether there has been new sources checked out or not. It takes a lot of > time compiling llvm/clang. Using 11-stable on a NanoBSD installation, &g

make release: how utilise filemon?

2017-05-10 Thread O. Hartmann
is 11-STABLE. In release.conf, I tried setting ## Set to use world- and kernel-specific make(1) flags. WORLD_FLAGS="-DNO_CLEAN -j $(sysctl -n hw.ncpu)" KERNEL_FLAGS="-DNO_CLEAN -j $(( $(( $(sysctl -n hw.ncpu) + 1 )) / 2 ))" without any noticable effect - make release always

make release vs jenkins

2016-05-11 Thread Roger Marquis
We use jenkins to build, test and release 11.0-CURRENT using jenkin's uid:gid. Everything works well up to "install -o root -g wheel" in "make release". Anyone know what the use case is for requiring release to be built as root? Roger ___

Re: make release fails...

2013-09-12 Thread Glen Barber
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

make release fails...

2013-09-12 Thread Lundberg, Johannes
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

Re: make release fails...

2013-09-12 Thread Lundberg, Johannes
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

Re: make release fails...

2013-09-12 Thread Glen Barber
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/

Re: make release fails...

2013-09-12 Thread Lundberg, Johannes
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

Re: make release fails...

2013-09-12 Thread Lundberg, Johannes
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

Re: make release fails...

2013-09-12 Thread Glen Barber
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

Re: make release fails...

2013-09-12 Thread Glen Barber
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

Re: make release recursion

2012-07-30 Thread Glen Barber
Alexander Pyhalov a...@rsu.ru wrote: Hello. On 07/28/2012 00:09, Glen Barber wrote: Hello, On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote: Hello. I've tried to do make cdrom on recent 10-current (svn revision 238763) and got after day of work: [...] Could you please

Re: make release recursion

2012-07-27 Thread Oliver Brandmueller
Hi, On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote: Hello. I've tried to do make cdrom on recent 10-current (svn revision 238763) and got after day of work: [...] It seems, it continued to add files to some archive recursively... Is it a bug or maybe I just can't cook it

Re: make release recursion

2012-07-27 Thread Garrett Cooper
On Fri, Jul 27, 2012 at 7:26 AM, Oliver Brandmueller o...@e-gitt.net wrote: Hi, On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote: Hello. I've tried to do make cdrom on recent 10-current (svn revision 238763) and got after day of work: [...] It seems, it continued to add

Re: make release recursion

2012-07-27 Thread Garrett Cooper
On Fri, Jul 27, 2012 at 8:37 AM, Garrett Cooper yaneg...@gmail.com wrote: On Fri, Jul 27, 2012 at 7:26 AM, Oliver Brandmueller o...@e-gitt.net wrote: Hi, On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote: Hello. I've tried to do make cdrom on recent 10-current (svn revision

Re: make release recursion

2012-07-27 Thread Glen Barber
Hello, On Fri, Jul 27, 2012 at 09:35:13AM +0400, Alexander Pyhalov wrote: Hello. I've tried to do make cdrom on recent 10-current (svn revision 238763) and got after day of work: [...] Could you please retry the cdrom build with NOSRC=yes set? If this does not succeed, could you please

make release recursion

2012-07-26 Thread Alexander Pyhalov
Hello. I've tried to do make cdrom on recent 10-current (svn revision 238763) and got after day of work: a

CURRENT as of 5/8/2012 make release

2012-05-08 Thread Outback Dingo
Ive noticed trying a make release on CURRENT that it appears to be looping deeper and deeper, does this appear normal to anyone else??? a usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/malo/if_malohal.h a usr/src/release/dist/usr/src/release/dist/usr/src/release

Re: make release: doesn't work for me, getting

2011-06-24 Thread Kim Culhan
Attempting to run: make release resulted in 'looping' until a kernel compile directory sys/amd64/compile/* was removed. Maybe I missed something in the docs. -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

Re: make release: doesn't work for me, getting

2011-06-24 Thread Ryan Stone
On Fri, Jun 24, 2011 at 8:47 AM, Kim Culhan w8hd...@gmail.com wrote: Attempting to run: make release resulted in 'looping' until a kernel compile directory sys/amd64/compile/* was removed. Maybe I missed something in the docs. -kim ___ freebsd

make release: doesn't work for me, getting recursive looping

2011-06-18 Thread Hartmann, O.
Try to build a cdrom from most recent CURRENT/amd64 sources. Issuing the follwing command fails the build process looping recursively and indefinitely within the source folder /usr/src/release: make release cdrom CHROOTDIR=/unused/release/9.0/ SVNROOT/usr/src BUILDNAME=9.0-CURRENT

Re: make release: doesn't work for me, getting recursive looping

2011-06-18 Thread Nathan Whitehorn
On 06/18/11 05:15, Hartmann, O. wrote: Try to build a cdrom from most recent CURRENT/amd64 sources. Issuing the follwing command fails the build process looping recursively and indefinitely within the source folder /usr/src/release: make release cdrom CHROOTDIR=/unused/release/9.0/ SVNROOT

Re: make release: doesn't work for me, getting recursive looping

2011-06-18 Thread Hartmann, O.
On 06/18/11 17:35, Nathan Whitehorn wrote: On 06/18/11 05:15, Hartmann, O. wrote: Try to build a cdrom from most recent CURRENT/amd64 sources. Issuing the follwing command fails the build process looping recursively and indefinitely within the source folder /usr/src/release: make release

make release

2011-04-12 Thread George Kontostanos
I am trying to make a release with the following arguments: make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES however /usr/home/current is being ignored completely and everything ends up in /usr/obj/usr/src. Am I doing something wrong

Re: make release

2011-04-12 Thread Daniel O'Connor
On 12/04/2011, at 17:02, George Kontostanos wrote: I am trying to make a release with the following arguments: make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES however /usr/home/current is being ignored completely and everything

Re: make release

2011-04-12 Thread Nathan Whitehorn
On 04/12/11 10:02, George Kontostanos wrote: I am trying to make a release with the following arguments: make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT EXTSRCDIR=/usr/src NOPORTS=YES MAKE_ISOS=YES however /usr/home/current is being ignored completely and everything ends up

Re: make release

2011-04-12 Thread George Kontostanos
sh generate-release.sh head /local3/release On Tue, Apr 12, 2011 at 6:14 PM, Nathan Whitehorn nwhiteh...@freebsd.orgwrote: On 04/12/11 10:02, George Kontostanos wrote: I am trying to make a release with the following arguments: make release CHROOTDIR=/usr/home/current BUILDNAME=9-CURRENT

Re: make release problems (amd64)

2011-03-26 Thread Daniel O'Connor
On 26/03/2011, at 18:42, O. Hartmann wrote: Yes, I tried and I ran into the same problems. But I didn't run into problems lately, the problem resists for me now for approx. three weeks or so and I reported this in questions@ once. Try 'make obj' before 'make release' - that fixed it for me

Re: make release problems (amd64)

2011-03-26 Thread O. Hartmann
On 26.03.2011 05:32, Daniel O'Connor wrote: Has anyone done one recently? I note there aren't any snapshots for this month, so perhaps I'm not alone. I tried this :- RELNAME=9.0 BUILDNAME=${RELNAME}-GENESIS make release CHROOTDIR=/tmp/${RELNAME}-release BUILDNAME=$BUILDNAME HTTP_PROXY=http

Re: make release problems (amd64)

2011-03-26 Thread Nathan Whitehorn
' before 'make release' - that fixed it for me. Thanks for reporting this! I just modified src/release/Makefile so that 'make release' causes the obj target to be run first, so this shouldn't happen anymore. -Nathan ___ freebsd-current@freebsd.org

make release problems (amd64)

2011-03-25 Thread Daniel O'Connor
Has anyone done one recently? I note there aren't any snapshots for this month, so perhaps I'm not alone. I tried this :- RELNAME=9.0 BUILDNAME=${RELNAME}-GENESIS make release CHROOTDIR=/tmp/${RELNAME}-release BUILDNAME=$BUILDNAME HTTP_PROXY=http://proxy:3128 FTP_PROXY=http://proxy:3128

Re: make release problems (amd64)

2011-03-25 Thread Daniel O'Connor
On 26/03/2011, at 15:02, Daniel O'Connor wrote:

Re: ports/150265: [patch] print/ghostscript8 disable bogus port conflicts in make release

2010-09-05 Thread Rob Farmer
! [adding a mailing list per your suggestion] I think you are misunderstanding the issue here. This is not a ghostscript issue and the maintainer of ghostscript isn't the right person to look at it. The same issue can appear with other ports used by make release, such as perl. In fact, there isn't any

Re: make release broken

2010-05-24 Thread James R. Van Artsdalen
On 5/22/2010 8:25 PM, Rob Farmer wrote: make release is still broken on amd64 as of svn 208373 (2010-05-21 04:52:49 -0500) That patch seems unrelated? What needs done is /src/release/$ARCH/boot_crunch.conf files need the relevant libraries added to the libs section. I haven't tested

Re: make release broken

2010-05-24 Thread Rob Farmer
On Sun, May 23, 2010 at 11:02 PM, James R. Van Artsdalen james-freebsd-curr...@jrv.org wrote: On 5/22/2010 8:25 PM, Rob Farmer wrote: make release is still broken on amd64 as of svn 208373 (2010-05-21 04:52:49 -0500) That patch seems unrelated? What needs done is /src/release/$ARCH

Re: make release broken

2010-05-22 Thread James R. Van Artsdalen
On 5/18/2010 2:34 AM, jhell wrote: On Mon, May 17, 2010 at 10:35 PM, Rob Farmer rfar...@predatorlabs.net wrote: make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo test.lo

Re: make release broken

2010-05-22 Thread Rob Farmer
On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen james-freebsd-curr...@jrv.org wrote: On 5/18/2010 2:34 AM, jhell wrote: On Mon, May 17, 2010 at 10:35 PM, Rob Farmer rfar...@predatorlabs.net wrote: make release is broken on current. Seems to be related to the lzma import

Re: make release broken

2010-05-18 Thread jhell
On 5/18/2010 1:39 AM, Garrett Cooper wrote: On Mon, May 17, 2010 at 10:35 PM, Rob Farmer rfar...@predatorlabs.net wrote: Hi, make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo

Re: make release broken

2010-05-18 Thread Julian H. Stacey
Rob Farmer wrote: Hi, make release is broken on current. Seems to be related to the lzma import. This is on i386: .. : undefined reference to `lzma_end' /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_read_support_compression_xz.o)(.text+0x567): In function `xz_filter_read

make release broken

2010-05-17 Thread Rob Farmer
Hi, make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo

Re: make release broken

2010-05-17 Thread Garrett Cooper
On Mon, May 17, 2010 at 10:35 PM, Rob Farmer rfar...@predatorlabs.net wrote: Hi, make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo test.lo camcontrol.lo dhclient.lo fsck_ffs.lo

Re: make release...

2003-10-22 Thread Anthony Fajri
thanks alot for your reply... but, after patched my FreeBSD with your patch, i still get errors root pwd /home/fajri/data/usr/src/release root patch genesis-patch-ae root make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI CVSROOT=/home/fajri/data/usr RELEASETAG

Re: make release...

2003-10-22 Thread Daniel O'Connor
email. root pwd /home/fajri/data/usr/src/release root patch genesis-patch-ae root make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4_8_RELEASE cd /home/fajri/data/root/usr rm -rf src cvs -R -d /home/fajri/data/usr co -P

make release...

2003-10-21 Thread Anthony Fajri
fajri more stable-supfile|grep release *default release=cvs tag=RELENG_4 == # make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4 if [ -f /etc/resolv.conf ]; then cp -p /etc/resolv.conf

Re: make release...

2003-10-21 Thread Daniel O'Connor
On Tuesday 21 October 2003 16:31, Anthony Fajri wrote: fajri more stable-supfile|grep release *default release=cvs tag=RELENG_4 You aren't syncing the repo with cvsup so the check out in make release doesn't work. Either apply the patch I attached and add CPNOTCVS= to your make release

Re: make release...

2003-10-21 Thread Ruslan Ermilov
On Tue, Oct 21, 2003 at 04:51:22PM +0930, Daniel O'Connor wrote: [...] Either apply the patch I attached and add CPNOTCVS= to your make release options, or check out the repository. In HEAD, a similar functionality is already provided through the use of the EXTSRCDIR variable. JFYI. Cheers

Re: make release...

2003-10-21 Thread Daniel O'Connor
On Tue, Oct 21, 2003 at 04:51:22PM +0930, Daniel O'Connor wrote: [...] Either apply the patch I attached and add CPNOTCVS= to your make release options, or check out the repository. In HEAD, a similar functionality is already provided through the use of the EXTSRCDIR variable. JFYI. Ahh

make release and md(4) problem

2003-09-21 Thread Bjoern A. Zeeb
Hi, when doing my first make release I noticed it stopped somewhere and hung :( 74830 p2 D+ 0:01.12 cpio -dump /mnt The host is i386 and TARGET ist sparc64 just to confuse. The base system runs a HEAD world/kernel from mid july. The above cpio must be from src/release/sparc64

Bug in make release regarding install.cfg

2003-09-14 Thread Maxim Sobolev
Folks, I've noted that the following inconsistency exists in make release. If there is a install.cfg file in /usr/src/release when executing make release (the file which if exists is placed into the root of mfs and customises behaviour of sysinstall), /usr/src/release/install.cfg takes

fbsd 4.8 make release question ?

2003-08-14 Thread NIkolay Kalev
How can the values for BIGBOOT image can be changed so if there is source patch for the system like ssp make release won;t fail when buidling release.9 stage ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd

RE: fbsd 4.8 make release question ?

2003-08-14 Thread John Baldwin
On 14-Aug-2003 NIkolay Kalev wrote: How can the values for BIGBOOT image can be changed so if there is source patch for the system like ssp make release won;t fail when buidling release.9 stage ? Use a local patch via LOCAL_PATCHES. -- John Baldwin [EMAIL PROTECTED]http

-current 'make release' status?

2003-07-29 Thread John
Hi, I'm currently down to this patch to allow a make release to complete for -current: === RCS file: /home/ncvs/src/release/Makefile,v retrieving revision 1.801 diff -u -r1.801 Makefile --- Makefile26 Jul 2003 06:47:40 -

Re: -current 'make release' status?

2003-07-29 Thread Ruslan Ermilov
On Tue, Jul 29, 2003 at 06:30:54AM -0400, John wrote: Hi, I'm currently down to this patch to allow a make release to complete for -current: [...] Try setting the KERNEL_FLAGS=-DNO_WERROR instead. without it, the following causes BOOTMFS to abort: cc -c -Os -pipe -Wall

Re: -current 'make release' status? [SOLVED]

2003-07-29 Thread Ruslan Ermilov
calls the command above. I'm currently in the middle of the make release and will see if this is reproduceable. # chroot /vol/vol0/work/5-current-chrootdir /bin/sh # env A few things not needed that are inherited from my normal account, but nothing that should have a negative

Re: -current 'make release' status? [SOLVED]

2003-07-29 Thread Bruce Evans
On Tue, 29 Jul 2003, Ruslan Ermilov wrote: ... Forget what I've said about NO_WERROR, it (unfortunately) only applies to the userland. Still, running make rerelease KERNEL_FLAGS=WERROR= gets the release done. I wondered why I get it, and similarly my nigthly buildkernel completed without

Re: -current 'make release' status? [SOLVED]

2003-07-29 Thread Ruslan Ermilov
On Wed, Jul 30, 2003 at 06:14:17AM +1000, Bruce Evans wrote: On Tue, 29 Jul 2003, Ruslan Ermilov wrote: ... Forget what I've said about NO_WERROR, it (unfortunately) only applies to the userland. Still, running make rerelease KERNEL_FLAGS=WERROR= gets the release done. I

Re: -current 'make release' status? [SOLVED]

2003-07-29 Thread Dan Nelson
In the last episode (Jul 29), Ruslan Ermilov said: Hm, I always thought that -O2 and -Os are just useful aliases that in effect only turn a few dozens of -f optimization flags, and that switching some of them off later is allowed. I.e., -Os -fno-strict-aliasing should work. That does work,

Re: -current 'make release' status? [SOLVED]

2003-07-29 Thread Bruce Evans
On Tue, 29 Jul 2003, Ruslan Ermilov wrote: On Wed, Jul 30, 2003 at 06:14:17AM +1000, Bruce Evans wrote: On Tue, 29 Jul 2003, Ruslan Ermilov wrote: ... Forget what I've said about NO_WERROR, it (unfortunately) only applies to the userland. Still, running make rerelease

Re: make release broken [FIX]

2003-07-25 Thread David O'Brien
On Tue, Jul 22, 2003 at 02:26:34PM -0400, John Baldwin wrote: On 22-Jul-2003 Ruslan Ermilov wrote: Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc

Re: make release broken [FIX]

2003-07-25 Thread Ruslan Ermilov
release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also fixes another issue with this telnet commit: it ensures that crypto telnet[d] do not end up in the base distribution. Why not simply enable 'NO_FLOPPIES

Re: make release broken [FIX]

2003-07-23 Thread Ruslan Ermilov
On Tue, Jul 22, 2003 at 03:07:01PM -0400, John Baldwin wrote: Are you eliminating the mfsroot? Yes. Ugh. How does sysinstall work with this change? You do realize that we mount the MFS as /, then mount the disk under /mnt, chroot to /mnt, then mount the CD in /dist in the chroot

Re: make release broken [FIX]

2003-07-23 Thread Ruslan Ermilov
On Tue, Jul 22, 2003 at 07:42:33PM +0300, Ruslan Ermilov wrote: Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached

Re: make release broken [FIX]

2003-07-23 Thread Mark Murray
probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also fixes another issue with this telnet commit: it ensures that crypto

Re: make release broken [FIX]

2003-07-23 Thread Ruslan Ermilov
On Wed, Jul 23, 2003 at 11:33:50AM +0100, Mark Murray wrote: Hi Please do not commit this. Please stop repeating this endlessly. This patch is only for those who need a working make release urgently, like me. You made it clear that you're working on a better fix. -- Ruslan Ermilov

make release broken [FIX]

2003-07-22 Thread Ruslan Ermilov
Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also fixes another issue with this telnet commit

Re: make release broken [FIX]

2003-07-22 Thread Mark Murray
: inline Content-Transfer-Encoding: quoted-printable Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also

RE: make release broken [FIX]

2003-07-22 Thread John Baldwin
On 22-Jul-2003 Ruslan Ermilov wrote: Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also fixes

Re: make release broken [FIX]

2003-07-22 Thread Ruslan Ermilov
On Tue, Jul 22, 2003 at 02:26:34PM -0400, John Baldwin wrote: On 22-Jul-2003 Ruslan Ermilov wrote: Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc

Re: make release broken [FIX]

2003-07-22 Thread John Baldwin
On 22-Jul-2003 Ruslan Ermilov wrote: On Tue, Jul 22, 2003 at 02:26:34PM -0400, John Baldwin wrote: On 22-Jul-2003 Ruslan Ermilov wrote: Hi! As many of you probably know, recent telnet commit broke snapshot building. Since I needed a working make release to go on with my task

Re: make release broken [FIX]

2003-07-22 Thread Ruslan Ermilov
building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also fixes another issue with this telnet commit: it ensures that crypto telnet[d] do not end up in the base distribution

Re: make release broken [FIX]

2003-07-22 Thread John Baldwin
telnet commit broke snapshot building. Since I needed a working make release to go on with my task on floppy-less make release (for AMD64, etc.), I had to just fix it. Attached is the patch. It also fixes another issue with this telnet commit: it ensures that crypto telnet[d] do

Re: make release broken [FIX]

2003-07-22 Thread Ruslan Ermilov
On Tue, Jul 22, 2003 at 03:07:01PM -0400, John Baldwin wrote: Why not simply enable 'NO_FLOPPIES' on the arch's that don't want floppies? Are you eliminating the mfsroot? Yes. Ugh. Yes, after looking into this a bit deeper, I must agree that preserving the mfsroot is much

Re: make release of CURRENT on 4.7 broken again ?

2003-07-21 Thread Andrey Elperin
On Sun, Jul 20, 2003 at 02:44:23PM +0300, Ruslan Ermilov wrote: A few days ago I've noticed such messages in CURRENT buildlog (on 4.7 box, building without -jsomething) : cc -Os -pipe -c chown_stub.c ld -dc -r -o chown.lo chown_stub.o /usr/obj//usr/src/usr.sbin/chown/chown.o

Re: make release of CURRENT on 4.7 broken again ?

2003-07-21 Thread Ruslan Ermilov
On Mon, Jul 21, 2003 at 02:13:45PM +0300, Andrey Elperin wrote: On Sun, Jul 20, 2003 at 02:44:23PM +0300, Ruslan Ermilov wrote: A few days ago I've noticed such messages in CURRENT buildlog (on 4.7 box, building without -jsomething) : cc -Os -pipe -c chown_stub.c ld -dc -r -o

Re: make release of CURRENT on 4.7 broken again ?

2003-07-21 Thread Ruslan Ermilov
On Mon, Jul 21, 2003 at 06:08:43PM +0300, Ruslan Ermilov wrote: On Mon, Jul 21, 2003 at 02:13:45PM +0300, Andrey Elperin wrote: On Sun, Jul 20, 2003 at 02:44:23PM +0300, Ruslan Ermilov wrote: A few days ago I've noticed such messages in CURRENT buildlog (on 4.7 box, building without

i386 'make release' broken

2003-07-20 Thread Scott Long
Just got the following from a 'make release BUILDNAME=5.1-CURRENT CHROOTDIR=/usr/release CVSROOT=/usr/ncvs NOPORTS= NODOC= . My world was up to date to within a day. The full log is at http://people.freebsd.org/~scottl/current-release-i386.log.gz. Note that while this is an SMP machine, -j

Re: i386 'make release' broken

2003-07-20 Thread Ruslan Ermilov
On Sun, Jul 20, 2003 at 02:18:42AM -0600, Scott Long wrote: Just got the following from a 'make release BUILDNAME=5.1-CURRENT CHROOTDIR=/usr/release CVSROOT=/usr/ncvs NOPORTS= NODOC= . My world was up to date to within a day. The full log is at http://people.freebsd.org/~scottl/current

make release of CURRENT on 4.7 broken again ?

2003-07-20 Thread Andrey Elperin
Hi, A few days ago I've noticed such messages in CURRENT buildlog (on 4.7 box, building without -jsomething) : cc -Os -pipe -c chown_stub.c ld -dc -r -o chown.lo chown_stub.o /usr/obj//usr/src/usr.sbin/chown/chown.o crunchide -k _crunched_chown_stub chown.lo echo int

Re: make release of CURRENT on 4.7 broken again ?

2003-07-20 Thread Ruslan Ermilov
On Sun, Jul 20, 2003 at 02:04:28PM +0300, Andrey Elperin wrote: Hi, A few days ago I've noticed such messages in CURRENT buildlog (on 4.7 box, building without -jsomething) : cc -Os -pipe -c chown_stub.c ld -dc -r -o chown.lo chown_stub.o /usr/obj//usr/src/usr.sbin/chown/chown.o

Re: make release of CURRENT on 4.7 box

2003-07-14 Thread Juli Mallett
* Bruce Evans [EMAIL PROTECTED] [ Date: 2003-07-13 ] [ w.r.t. Re: make release of CURRENT on 4.7 box ] On Sun, 13 Jul 2003, Tim Kientzle wrote: Bruce Evans wrote: I think splitting it or making it exit after just setting variables in the userland case is the right fix

Re: make release of CURRENT on 4.7 box

2003-07-13 Thread Tim Kientzle
Bruce Evans wrote: On Sat, 12 Jul 2003, Tim Kientzle wrote: In particular, newvers.sh is being run with the current directory being ${.OBJDIR}, and ${.OBJDIR} doesn't contain a Makefile, ... ... `make -V FOO' doesn't require a Makefile in -current. ... A-HA! I don't know the right way to fix

Re: make release of CURRENT on 4.7 box

2003-07-13 Thread Bruce Evans
On Sun, 13 Jul 2003, Tim Kientzle wrote: Bruce Evans wrote: I think splitting it or making it exit after just setting variables in the userland case is the right fix. ... [it == newvers.sh] I think you're right, but don't see a very simple way to make that work, especially given the

make release of CURRENT on 4.7 box

2003-07-12 Thread Andrey Elperin
Hi, Tell me, please, is it a possible to make release of CURRENT on 4.7 box at present ? I see that make release stops with a such messages for a couple of days : -- stage 4: populating /usr/obj/usr/src/i386/usr/include

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Tim Kientzle
Andrey Elperin wrote: Tell me, please, is it a possible to make release of CURRENT on 4.7 box at present ? I see that make release stops with a such messages for a couple of days : === include cd /usr/src/include; /usr/obj/usr/src/make.i386/make buildincludes; /usr/obj/usr/src/make.i386/make

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Terry Lambert
Tim Kientzle wrote: Andrey Elperin wrote: Tell me, please, is it a possible to make release of CURRENT on 4.7 box at present ? I see that make release stops with a such messages for a couple of days : === include cd /usr/src/include; /usr/obj/usr/src/make.i386/make buildincludes

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Tim Kientzle
Terry Lambert wrote: Tim Kientzle wrote: Andrey Elperin wrote: Tell me, please, is it a possible to make release of CURRENT on 4.7 box at present ? I see that make release stops with a such messages for a couple of days : === include cd /usr/src/include; /usr/obj/usr/src/make.i386/make

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Andrey Elperin
On Sat, Jul 12, 2003 at 10:50:41AM -0700, Tim Kientzle wrote: I see that make release stops with a such messages for a couple of days : === include cd /usr/src/include; /usr/obj/usr/src/make.i386/make buildincludes; /usr/obj/usr/src/make.i386/make installincludes creating osreldate.h from

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Bruce Evans
On Sat, 12 Jul 2003, Tim Kientzle wrote: Terry Lambert wrote: Does this damage CURRENT on CURRENT or anything like that? Don't know, haven't had a chance to try it. To be honest, I was never able to understand how the previous version was supposed to work, since the newvers.sh script was

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Tim Kientzle
Bruce Evans wrote: On Sat, 12 Jul 2003, Tim Kientzle wrote: Terry Lambert wrote: Does this damage CURRENT on CURRENT or anything like that? Don't know, haven't had a chance to try it. To be honest, I was never able to understand how the previous version was supposed to work, since the

Re: make release of CURRENT on 4.7 box

2003-07-12 Thread Bruce Evans
On Sat, 12 Jul 2003, Tim Kientzle wrote: Bruce Evans wrote: On Sat, 12 Jul 2003, Tim Kientzle wrote: To be honest, I was never able to understand how the previous version was supposed to work, since the newvers.sh script was run with a very odd current directory. Looks like it was

Broken make release

2003-06-17 Thread John Polstra
Make release using sources from yesterday (June 16) seems to be broken. These two commands are failing: umount: unmount of /mnt failed: Device busy umount: unmount of /dev failed: Device busy I'll include a bigger snippet of the output below. My src/release/Makefile is standard except

i386 -current make release available for testing

2003-02-28 Thread John De Boskey
Hi, I have built a i386 specific install for -current. It is available as: ftp://releng4.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20030228-CURRENT Floppies are in the typical place. It was built using the patch below passed in as LOCAL_PATCH to the make release process. I'll leave

Re: i386 -current make release available for testing

2003-02-28 Thread Ruslan Ermilov
On Fri, Feb 28, 2003 at 05:46:55AM -0500, John De Boskey wrote: Hi, I have built a i386 specific install for -current. It is available as: ftp://releng4.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20030228-CURRENT ^^^

Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

2003-02-16 Thread Makoto Matsushita
phk Not yet. I think adding a -m architecture flag to disklabel is the phk way around this problem, but have not had time to do so. Thanks, I'm waiting until you have enough time to do since I have little knowledge about this issue:) BTW, what's changes do you imagine? Make a table which

Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

2003-02-16 Thread phk
In message [EMAIL PROTECTED], Makoto Matsushita writes: phk Not yet. I think adding a -m architecture flag to disklabel is the phk way around this problem, but have not had time to do so. Thanks, I'm waiting until you have enough time to do since I have little knowledge about this issue:) BTW,

FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

2003-02-15 Thread Makoto Matsushita
I've tried to do make release of FreeBSD/alpha on FreeBSD/i386 box last night, and found that follow error while generating drivers.flp: + export BLOCKSIZE=512 + [ /R/stage/floppies/drivers.flp = -s ] + do_size= + FSIMG=/R/stage/floppies/drivers.flp + shift + RD=/R/stage + shift + MNT=/mnt

Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

2003-02-15 Thread phk
In message [EMAIL PROTECTED], Makoto Matsushita writes: I've tried to do make release of FreeBSD/alpha on FreeBSD/i386 box last night, and found that follow error while generating drivers.flp: If my understandings are correct, this is because disklabel(8) kicked is FreeBSD/i386 native binary

Re: FreeBSD/alpha make-release on FreeBSD/i386: dislabel problem

2003-02-15 Thread Wilko Bulte
On Sat, Feb 15, 2003 at 10:37:26PM +0100, [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Makoto Matsushita writes: I've tried to do make release of FreeBSD/alpha on FreeBSD/i386 box last night, and found that follow error while generating drivers.flp: If my understandings

Newfs börked: Kills make release in strange ways.

2003-01-29 Thread Poul-Henning Kamp
Newfs is börked right now (see below), and that kills make release in really strange ways. Considering I actually went as far as adding a make test target in src/sbin/newfs then it is a tiny bit disappointing that it was not used pre-commit. Poul-Henning bang# dd if=/dev/zero of=/dev/md0 dd

Re: Newfs börked: Kills make release in strange ways.

2003-01-29 Thread Juli Mallett
* De: Poul-Henning Kamp [EMAIL PROTECTED] [ Data: 2003-01-29 ] [ Subjecte: Newfs börked: Kills make release in strange ways. ] Newfs is börked right now (see below), and that kills make release in really strange ways. It looks like it was this typo, which didn't show up as being

  1   2   3   4   5   >