Re: make release: how utilise filemon?

On 5/10/17 1:12 AM, O. Hartmann wrote: > hello, > > building a release of most recent 12-CURRENT seems to be at some point very > annoying. When building the main host's system out of /usr/src > using /etc/src-env.conf set with WITH_META_MODE=yes, build time decreases > significantly. Now I perfor

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) > BRILLIANTSER

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

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

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 Mirama homepage

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 h

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) BRILLIA

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 r

Re: make release recursion

Alexander Pyhalov 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: >>> >> >> [...] >>

Re: make release recursion

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 ple

Re: make release recursion

On Fri, Jul 27, 2012 at 8:37 AM, Garrett Cooper wrote: > On Fri, Jul 27, 2012 at 7:26 AM, Oliver Brandmueller 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

Re: make release recursion

On Fri, Jul 27, 2012 at 7:26 AM, Oliver Brandmueller 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 file

Re: make release recursion

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 c

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

On Fri, Jun 24, 2011 at 8:47 AM, Kim Culhan 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-current@fr

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

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/fre

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

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 cd

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

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/u

Re: make release

Sorry I didn't read the man pages lately! releaseMeta-target to build all release media and distributions applicable to this platform. All output goes to ${.OBJDIR}, which will likely be either src/release or the equivalent p

Re: make release

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 in /usr

Re: make release

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 everythin

Re: make release problems (amd64)

On 03/26/11 03:44, Daniel O'Connor wrote: 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' b

Re: make release problems (amd64)

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://p

Re: make release problems (amd64)

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

Re: make release problems (amd64)

On 26/03/2011, at 15:02, Daniel O'Connor wrote: usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/release/ker

Re: make release broken

On Sun, May 23, 2010 at 11:02 PM, James R. Van Artsdalen 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/boot_crunch.conf f

Re: make release broken

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 te

Re: make release broken

On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen wrote: > On 5/18/2010 2:34 AM, jhell wrote: >> On Mon, May 17, 2010 at 10:35 PM, Rob Farmer >> wrote: make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch b

Re: make release broken

On 5/18/2010 2:34 AM, jhell wrote: > On Mon, May 17, 2010 at 10:35 PM, Rob Farmer > 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 camcontrol.lo dh

Re: make release broken

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'

Re: make release broken

On 5/18/2010 1:39 AM, Garrett Cooper wrote: > On Mon, May 17, 2010 at 10:35 PM, Rob Farmer 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 camc

Re: make release broken

On Mon, May 17, 2010 at 10:35 PM, Rob Farmer 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 ifconfig.lo mount_n

Re: make release...

On Wednesday 22 October 2003 22:15, Anthony Fajri wrote: > thanks alot for your reply... > > but, after patched my FreeBSD with your patch, i still get errors Err the patch isn't designed to fix your problem, it is just written by me to make things a bit easier. I suggest re-reading

Re: make release...

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 RELE

Re: make release...

> 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. J

Re: make release...

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. Chee

Re: make release...

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 broken [FIX]

On Fri, Jul 25, 2003 at 01:59:40PM -0700, David O'Brien 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 wor

Re: make release broken [FIX]

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" (

Re: make release broken [FIX]

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

Re: make release broken [FIX]

Hi Please do not commit this. M Ruslan Ermilov writes: > > --A9z/3b/E4MkkD+7G > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Tue, Jul 22, 2003 at 07:42:33PM +0300, Ruslan Ermilov wrote: > > Hi! > >=20 > > As many

Re: make release broken [FIX]

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. Attache

Re: make release broken [FIX]

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

Re: make release broken [FIX]

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 preser

Re: make release broken [FIX]

On 22-Jul-2003 Ruslan Ermilov wrote: > On Tue, Jul 22, 2003 at 02:45:52PM -0400, John Baldwin wrote: >> >> 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

Re: make release broken [FIX]

On Tue, Jul 22, 2003 at 02:45:52PM -0400, John Baldwin wrote: > > 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 brok

Re: make release broken [FIX]

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 wi

Re: make release broken [FIX]

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" (

RE: make release broken [FIX]

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 f

Re: make release broken [FIX]

This is on my TODO. Do not commit this - I have a much cleaner fix. M Ruslan Ermilov writes: > > --v9Ux+11Zm5mwPlX6 > Content-Type: multipart/mixed; boundary="a8Wt8u1KmwUX3Y2C" > Content-Disposition: inline > > > --a8Wt8u1KmwUX3Y2C > Content-Type: text/plain; charset=us-ascii > Content-Dispos

Re: make release of CURRENT on 4.7 broken again ?

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

Re: make release of CURRENT on 4.7 broken again ?

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 -j) : > > > > > > cc -Os -pipe -c chown_stub.c > > > ld -dc -r

Re: make release of CURRENT on 4.7 broken again ?

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 -j) : > > > > 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 > > crunc

Re: make release of CURRENT on 4.7 broken again ?

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 -j) : > > 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 > crun

Re: make release of CURRENT on 4.7 box

* 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 > > &g

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. ... [it == newvers.sh] > > I think you're right, but don't see a very simple way to make that > work, especially given t

Re: make release of CURRENT on 4.7 box

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 th

Re: make release of CURRENT on 4.7 box

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. > > > > Look

Re: make release of CURRENT on 4.7 box

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 newvers.s

Re: make release of CURRENT on 4.7 box

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 sc

Re: make release of CURRENT on 4.7 box

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 osreldat

Re: make release of CURRENT on 4.7 box

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 buildin

Re: make release of CURRENT on 4.7 box

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 b

Re: make release of CURRENT on 4.7 box

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 still broken

* De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-26 ] [ Subjecte: make release still broken ] > Hi Juli! > > This is just a FYI that your patch for newfs(8) that makes > it use libufs _does_ make it fit onto the MFSROOT floppy > again! Okay, cool. I haven't gotten many (any?) rep

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 floppie

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

Re: make release.9 fails ... ?

Hi Marc, It Should be dhclient-script.sh (a bug in the release builder?) then it works... :) Joseph On Wed, 2003-01-22 at 19:06, Marc G. Fournier wrote: > Evening ... > > I found the release man page this evening, after more searching, and > understand from it that a simple: > > cd /usr/src >

Re: make release.9 fails ... ?

scrappy> I found the release man page this evening, after more searching, and scrappy> understand from it that a simple: >From release(7): floppies Generate a new set of boot floppies. This will call the release.5, release.9, and release.10 targets to re-generate

Re: make release errors

--On Thursday, January 16, 2003 6:12 AM -0800 "Joel M. Baldwin" <[EMAIL PROTECTED]> wrote: I've been trying to do a 'make release' the last couple of weeks and keep getting the following error. geeze time for a coffee. sorry people. here is the error. ===> chinese/mozilla-tclp ===> Crea

Re: make release run output

In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes: > >--gr/z0/N6AeWAPJVB >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Tue, Oct 22, 2002 at 08:41:38AM +0200, Poul-Henning Kamp wrote: >>=20 >> Thankyou! >>=20 >> This i

Re: make release run output

On Tue, Oct 22, 2002 at 08:41:38AM +0200, Poul-Henning Kamp wrote: > > Thankyou! > > This is most valuable at this time! > > Do we have some volunteers chasing the pc98 and alpha issues ? > I thought you'd fix pc98. These were your changes, weren't they? :-) > In message <[EMAIL PROTECTED]>,

Re: make release run output

Thankyou! This is most valuable at this time! Do we have some volunteers chasing the pc98 and alpha issues ? Poul-Henning In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes: > >--LQksG6bCIzRHxTLp >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Enco

Re: make release failure in kerberos

On Thu, Feb 21, 2002 at 06:24:59AM +0200, John Hay wrote: > Hi Jacques, > > Make release fails here. Can it be your changes to kerberos? Could be; I'll have a look. Thanks! -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNI

Re: make release broken

> > jhay> The last one that worked here was on 20020108. The one on the > jhay> next day broke. The release builds are started from cron at > jhay> midnight SAST which is 2 hours ahead of UTC. > > FYI: 5.0-CURRENT-20020113-JPSNAP builds goes fine here. I dunno what > change fixes this :-) Yes,

Re: make release broken

jhay> The last one that worked here was on 20020108. The one on the jhay> next day broke. The release builds are started from cron at jhay> midnight SAST which is 2 hours ahead of UTC. FYI: 5.0-CURRENT-20020113-JPSNAP builds goes fine here. I dunno what change fixes this :-) -- - Makoto `MAR'

Re: make release broken

This error is occured when "make release" try to roll 'bin' distribution. jhay> Make release of -current has been broken here for the past few jhay> days. I had a look on the Japanese snapshot site and theirs jhay> break with the same error. Do anybody have an idea about what jhay> is going wro

Re: make release broken

> At 07:51 AM 1/12/2002 +0200, John Hay wrote: > >Hi, > > > >Make release of -current has been broken here for the past few days. I had > >a look on the Japanese snapshot site and theirs break with the same error. > >Do anybody have an idea about what is going wrong? > > > >###

Re: make release broken

At 07:51 AM 1/12/2002 +0200, John Hay wrote: >Hi, > >Make release of -current has been broken here for the past few days. I had >a look on the Japanese snapshot site and theirs break with the same error. >Do anybody have an idea about what is going wrong? > >###

Re: "make release" breakage: src/sbin/ifconfig

Makoto Matsushita <[EMAIL PROTECTED]> writes: > With 5-current as of Dec/04/2001 15:00:00 GMT. > > It seems that this is because 'WARNS=0' line is inside of > !defined(RELEASE_CRUNCH) clause. IMO, if an application's code > requires to set 'WARNS=0" for build, it should also be set when > buildi

Re: make release failure

If memory serves me right, John Hay wrote: > I have now also tested your second patch and with a minor mod to make > make happy, the release finished. Here is the patch as I have used it. [snip] Great, thanks for testing this! I'm still having problems keeping my scratch box alive long enough

Re: make release failure

Bruce, > > Yes, this patch fix it for me. I had to convert the spaces back to tabs > > though. :-) > > Hi John-- > > I was trying to test out another patch, which (in addition to fixing > the problem you found) also folds the functionality of NORELNOTES into > NODOC. Unfortunately, my -CURRE

Re: make release failure

If memory serves me right, John Hay wrote: > Yes, this patch fix it for me. I had to convert the spaces back to tabs > though. :-) Hi John-- I was trying to test out another patch, which (in addition to fixing the problem you found) also folds the functionality of NORELNOTES into NODOC. Unfor

Re: make release failure

Yes, this patch fix it for me. I had to convert the spaces back to tabs though. :-) John -- John Hay -- [EMAIL PROTECTED] > If memory serves me right, Dima Dorfman wrote: > > John Hay <[EMAIL PROTECTED]> writes: > > > > > > *** Filesystem is 1440 K, 66 left > > > > > *** 4000 bytes/inode,

Re: make release failure

If memory serves me right, Dima Dorfman wrote: > "David O'Brien" <[EMAIL PROTECTED]> writes: > > On Sun, May 27, 2001 at 11:32:09PM -0700, Bruce A. Mah wrote: > > > +.if !defined(NORELNOTES) > > > > Do we really need Yet Another Knob? Why isn't NODOC suffient? > > FWIW, I think we should lose N

Re: make release failure

"David O'Brien" <[EMAIL PROTECTED]> writes: > On Sun, May 27, 2001 at 11:32:09PM -0700, Bruce A. Mah wrote: > > +.if !defined(NORELNOTES) > > Do we really need Yet Another Knob? Why isn't NODOC suffient? FWIW, I think we should lose NORELNOTES; as you say, NODOC is sufficient. > I cannot think

Re: make release failure

On Sun, May 27, 2001 at 11:32:09PM -0700, Bruce A. Mah wrote: > +.if !defined(NORELNOTES) Do we really need Yet Another Knob? Why isn't NODOC suffient? I cannot think of any reason that the people who typically use NODOC=yes would want release notes. Or please at least treat NODOCS=yes ==> NOR

Re: make release failure

If memory serves me right, Dima Dorfman wrote: > John Hay <[EMAIL PROTECTED]> writes: > > > > *** Filesystem is 1440 K, 66 left > > > > *** 4000 bytes/inode, 116 left > > > > cp: /usr/src/release/texts/FLOPPIES.TXT: No such file or directory > > > > > > What revision of src/release/Makefile

Re: make release failure

John Hay <[EMAIL PROTECTED]> writes: > > > A make release failed here with: > > > > > > # > > > touch release.8 > > > Making fixit floppy. > > > disklabel: ioctl DIOCWLABEL: Operation not supported by device > > > Warning: Block size restricts cylinders per group t

Re: make release failure

> > A make release failed here with: > > > > # > > touch release.8 > > Making fixit floppy. > > disklabel: ioctl DIOCWLABEL: Operation not supported by device > > Warning: Block size restricts cylinders per group to 6. > > Warning: 1216 sector(s) in last cylinder u

Re: make release failure

John Hay <[EMAIL PROTECTED]> writes: > A make release failed here with: > > # > touch release.8 > Making fixit floppy. > disklabel: ioctl DIOCWLABEL: Operation not supported by device > Warning: Block size restricts cylinders per group to 6. > Warning: 1216 sector(

Re: make release failure

On Sun, May 27, 2001 at 10:45:59PM +0200, John Hay wrote: This strongly smells like a side-effect of RELNOTESng that removed the 'texts' subdir in favor of generated .txt from .sgml source files Wilko > A make release failed here with: > > # > touch release.8 >

Buildworld failure. [Re: make release Börked...]

My buildworld today also fails at gdb. cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=p

Re: make release broken in telnetd

On Sun, Apr 01, 2001 at 10:40:46PM +0100, Brian Somers wrote: > Hi, > > I'm not convinced that the patch will help. It looks like the error > is because it's using the ppp.lo that was built with crypto support > but without the mppe bits. Maybe other objects (such as ccp.o in > this case - w

Re: make release broken in telnetd

Hi, I'm not convinced that the patch will help. It looks like the error is because it's using the ppp.lo that was built with crypto support but without the mppe bits. Maybe other objects (such as ccp.o in this case - which seems to be built with HAVE_DES and therefore includes MPPEAlgorithm

Re: make release broken in telnetd

Hi! This was tricky. Due to the old bug in release/Makefile (it did not pass -DRELEASE_CRUNCH when building list of object files for crunched binary), ${OBJS} list for ppp was computed incorrectly, and ppp/Makefile had a special glue to build empty object files: : .if defined(RELEASE_CRUNCH) :

Re: make release broken in telnetd

Hi Ruslan, > > Could you please try the attached patch and let me know? > > I had to move -DRELEASE_CRUNCH to *_fixit.conf so that > ${OBJS} are computed correctly for usr.bin/telnet. I have tried it, but now it breaks in boot_crunch: ## cc -O -pipe-DCRUNCHED_BINARY -c tunefs_stub

Re: make release broken in telnetd

John! Could you please try the attached patch and let me know? I had to move -DRELEASE_CRUNCH to *_fixit.conf so that ${OBJS} are computed correctly for usr.bin/telnet. On Thu, Mar 29, 2001 at 10:08:50AM +0200, John Hay wrote: > > On Wed, Mar 28, 2001 at 01:00:59PM +0300, Ruslan Ermilov wrote:

Re: make release broken in telnetd

Hi! I don't see how my changes to non-secure Makefiles might affect this. What I did is disabled building of non-secure, standard libtelnet, telnet and telnetd if we are also building the secure versions. I did not touch the secure/ versions in this commit. Moreover, the standard versions are st

Re: make release still broken...

> > ===> rpcsvc > > rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h > > rpcgen: cannot find any C preprocessor (cpp) > > *** Error code 1 > > > Let me start a release. This means rpcgen has been using > /usr/libexec/cpp which is *only* for the compiler's use. rpcgen s

Re: make release still broken...

On Tue, Jan 09, 2001 at 09:11:20AM +0100, Poul-Henning Kamp wrote: > ===> rpcsvc > rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h > rpcgen: cannot find any C preprocessor (cpp) > *** Error code 1 Let me start a release. This means rpcgen has been using /usr/libexec/cp

  1   2   3   >