Re: Can't build -current incrementally due to libnv changes

2016-08-27 Thread Mariusz Zaborski
Sorry I missed somehow header file. Done in r304912. Thanks, Mariusz On 27 August 2016 at 17:00, Andrey Chernov wrote: > Yes, 'make includes' (and 'make obj' and 'make depend') is done before > 'make all' in /usr/src/lib > ===> libnv (all) > cc -O2 -pipe -march=sandybridge -I/usr/src/lib/libnv

Can't build -current incrementally due to libnv changes

2016-08-27 Thread Andrey Chernov
Yes, 'make includes' (and 'make obj' and 'make depend') is done before 'make all' in /usr/src/lib ===> libnv (all) cc -O2 -pipe -march=sandybridge -I/usr/src/lib/libnv/../../sys -I/usr/src/lib/libnv -MD -MF.depend.cnvlist.o -MTcnvlist.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werro

Re: can't build CURRENT/amd64 using 9.3?

2014-10-28 Thread owner-freebsd-current
Fixed by scrubbing 9.3 and installing 10.1-RC3, which solved a couple of other issues. Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-cu

Re: can't build CURRENT/amd64 using 9.3?

2014-10-25 Thread Ian Lepore
On Fri, 2014-10-24 at 21:06 -0400, owner-freebsd-curr...@freebsd.org wrote: > roberth...@rcn.com writes: > > > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on > > the command line. For installkernel, do I need to use them also, > > or will it magically know where to look? > >

Re: can't build CURRENT/amd64 using 9.3?

2014-10-25 Thread owner-freebsd-current
Garrett Cooper writes: > The message is telling you (indirectly) that you need to run make > buildworld successfully first? Recapping: Current system: FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 Source tree at CURRENT/r273626. No make.c

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread Garrett Cooper
On Oct 24, 2014, at 21:02, owner-freebsd-curr...@freebsd.org wrote: > David Wolfskill writes: > >>> Kernel built. >>> However: >>> >>> huff@>> make installkernel >>> ERROR: No kernel "GENERIC" to install. >>> *** Error code 1 >>> ... >>> I believe there is a kernel in >>> /usr/obj/a

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread owner-freebsd-current
David Wolfskill writes: > > > I believe that the cited message refers to the kernel configuration > > > file, which is expected to be in sys/amd64/conf/GENERIC within the > > > src hierarchy. > > > >Like this: > > > > huff@>> pwd > > /usr/src > > huff@>> dir sys/amd64/conf/GENER

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread owner-freebsd-current
David Wolfskill writes: > >Kernel built. > >However: > > > > huff@>> make installkernel > > ERROR: No kernel "GENERIC" to install. > > *** Error code 1 > > ... > >I believe there is a kernel in > > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in > > /usr/obj/amd64.a

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread David Wolfskill
On Sat, Oct 25, 2014 at 12:02:48AM -0400, roberth...@rcn.com wrote: > ... > > > huff@>> make installkernel > > > ERROR: No kernel "GENERIC" to install. > > > *** Error code 1 > > > ... > > > I believe there is a kernel in > > > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in > > >

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread David Wolfskill
On Fri, Oct 24, 2014 at 09:06:37PM -0400, owner-freebsd-curr...@freebsd.org wrote: > > roberth...@rcn.com writes: > > > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on > > the command line. For installkernel, do I need to use them also, > > or will it magically know where to

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread owner-freebsd-current
roberth...@rcn.com writes: > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on > the command line. For installkernel, do I need to use them also, > or will it magically know where to look? Kernel built. However: huff@>> make installkernel ERROR: No kernel "G

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread owner-freebsd-current
Putting TARGET/TARGET_ARCH on the command line didn't help. Adding " -j 1 " to make - did. I am now doing "make buildkernel" with TARGET/TARGET_ARCH on the command line. For installkernel, do I need to use them also, or will it magically know where to look? Respe

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread owner-freebsd-current
Ian Lepore writes: > >I have a system running > > > > FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 > > > >I have updated the source tree to CURRENT r273542. > >If I build "make buildworld" for the GENERIC kernel and no > > make.conf or src.conf, it succee

Re: can't build CURRENT/amd64 using 9.3?

2014-10-24 Thread Ian Lepore
On Thu, 2014-10-23 at 21:54 -0400, owner-freebsd-curr...@freebsd.org wrote: > I have a system running > > FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 > > I have updated the source tree to CURRENT r273542. > If I build "make buildworld" for the GENERIC kern

can't build CURRENT/amd64 using 9.3?

2014-10-23 Thread owner-freebsd-current
I have a system running FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386 I have updated the source tree to CURRENT r273542. If I build "make buildworld" for the GENERIC kernel and no make.conf or src.conf, it succeeds. If I use an empty make.conf

Re: Can't build -CURRENT on 4.7

2003-06-09 Thread Daniel C. Sobral
Ruslan Ermilov wrote: On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support

Re: Can't build -CURRENT on 4.7

2003-06-08 Thread Ruslan Ermilov
On Sat, Jun 07, 2003 at 03:34:08PM -0700, Tim Kientzle wrote: > David O'Brien wrote: > > >This won't work on non-i386, due to alloca issues. > >>+ WORLDTMP=${WORLDTMP} CSTD= \ > >may. > > > Hmmm... This seems like the Right Thing in > any case, since it is one less assumption you're

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread Tim Kientzle
David O'Brien wrote: This won't work on non-i386, due to alloca issues. + WORLDTMP=${WORLDTMP} CSTD= \ may. Hmmm... This seems like the Right Thing in any case, since it is one less assumption you're making about the build environment. I'm still getting buildworld failures, though. Long afte

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> "David O'Brien" <[EMAIL PROTECTED]> writes: : > + WORLDTMP=${WORLDTMP} CSTD= \ : : may. This seems to mostly work... I'm trying to sort out a couple of other issues, but those may be related to other changes that I've made in my test tree. W

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread David O'Brien
On Sat, Jun 07, 2003 at 10:38:15AM -0700, Tim Kientzle wrote: > Index: Makefile.inc1 > === > RCS file: /usr/src/cvs/src/Makefile.inc1,v > retrieving revision 1.363 > diff -u -r1.363 Makefile.inc1 > --- Makefile.inc1 31 May 2003 21:

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread David O'Brien
On Sat, Jun 07, 2003 at 10:38:15AM -0700, Tim Kientzle wrote: > Index: usr.bin/xlint/lint1/cgram.y > === > RCS file: /usr/src/cvs/src/usr.bin/xlint/lint1/cgram.y,v > retrieving revision 1.7 > diff -u -r1.7 cgram.y > --- usr.bin/xlint/l

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> "David O'Brien" <[EMAIL PROTECTED]> writes: : > First off, I'd like to say that's my understanding as well. : : That was not my understanding at all. The last time it came it, it was specifically stated that it was until the branch point. But so far th

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread David O'Brien
On Sat, Jun 07, 2003 at 06:30:11AM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Ruslan Ermilov <[EMAIL PROTECTED]> writes: > : On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > : > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > : > > T

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread Tim Kientzle
David O'Brien wrote: On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this is

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Ruslan Ermilov <[EMAIL PROTECTED]> writes: : On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: : > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: : > > The compiler in 4.7 does not like this: : > > : > > -std=gnu99 : > >

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread Ruslan Ermilov
On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > > The compiler in 4.7 does not like this: > > > > -std=gnu99 > > > > As a result, buildworld of -CURRENT fails > > rather early. > > Committers are not required to

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread Kris Kennaway
On Sat, Jun 07, 2003 at 01:07:24AM -0700, David O'Brien wrote: > I carefully worded the reply to specifically address build 5-CURRENT on > 4.7. Can you try src/share/mk/bsd.sys.mk rev 1.29 to see if it fixes > your problem? Have you tested it thoroughly? Didn't you back out -std=c99 in a previo

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread David O'Brien
On Sat, Jun 07, 2003 at 12:08:31AM -0700, Kris Kennaway wrote: > On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > > > The compiler in 4.7 does not like this: > > > > > > -std=gnu99 > > > > > > As a result, build

Re: Can't build -CURRENT on 4.7

2003-06-07 Thread Kris Kennaway
On Fri, Jun 06, 2003 at 11:57:00PM -0700, David O'Brien wrote: > On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > > The compiler in 4.7 does not like this: > > > > -std=gnu99 > > > > As a result, buildworld of -CURRENT fails > > rather early. > > Committers are not required to

Re: Can't build -CURRENT on 4.7

2003-06-06 Thread David O'Brien
On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote: > The compiler in 4.7 does not like this: > > -std=gnu99 > > As a result, buildworld of -CURRENT fails > rather early. Committers are not required to support building 5-CURRENT, post 5.0-RELEASE on a 4.7 machine. So this is not g

Re: Can't build -CURRENT on 4.7

2003-06-06 Thread Tim Kientzle
The compiler in 4.7 does not like this: -std=gnu99 As a result, buildworld of -CURRENT fails rather early. Tim Kientzle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[

Re: cvsupit assumptions (was: Re: Re[2]: Can't build current...)

2001-03-28 Thread Kris Kennaway
On Wed, Mar 28, 2001 at 09:15:51PM +0200, Gabriel Ambuehl wrote: > Oh and while I'm on it: where is src/crypto/rijndael in the CVS? in src/sys/crypto/rijndael :-) > CVSWEB doesn't find it, neither does it get downloaded (this time > using a complete supfile ;-)... You need the src-sys-crypto c

Re: cvsupit assumptions (was: Re: Re[2]: Can't build current...)

2001-03-28 Thread Gabriel Ambuehl
-BEGIN PGP SIGNED MESSAGE- Hello Robert, Tuesday, March 27, 2001, 8:19:42 PM, you wrote: > I've actually heard that from a couple of other people lately -- that > cvsupit still assumes that crypto should not be pulled down, and the > crypto code is now assumed in the default build. Thi

Re: Can't build current...

2001-03-27 Thread Makoto MATSUSHITA
kris> I believe Mark's intention was to keep crypt-blowfish.c optional for kris> those who don't want to install crypto. Perhaps this is broken. src/lib/libcrypt/Makefile says: # Pull in the crypt-des.c source, assuming it is present. .if exists(${.CURDIR}/../../secure/lib/libcrypt/crypt-des.c

Re: Re[2]: Can't build current...

2001-03-27 Thread J Wunsch
Gabriel Ambuehl <[EMAIL PROTECTED]> wrote: > I'm using cvsup.de.FreeBSD.org which appears to be a cname > cvsup.uk.FreeBSD.org. Huh? That would be a mistake if it happened. But it isn't: j@uriah 159% nslookup cvsup.de.freebsd.org Server: uriah.heep.sax.de Address: 0.0.0.0 Non-authoritative

Re: Can't build current...

2001-03-27 Thread Kris Kennaway
On Wed, Mar 28, 2001 at 02:55:15AM +0900, Makoto MATSUSHITA wrote: > You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't > have, it's your problem. The CVS repository has this file already: > http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blowfish.c > > Ha

cvsupit assumptions (was: Re: Re[2]: Can't build current...)

2001-03-27 Thread Robert Watson
On Tue, 27 Mar 2001, Gabriel Ambuehl wrote: > I'm using cvsup.de.FreeBSD.org which appears to be a cname > cvsup.uk.FreeBSD.org. But it looks like, that for some reason, > src-secure didn't get added to the cvsupfile (hmm. might be related to > the fact that cvsupit creates cvsup.intl for that

Re[2]: Can't build current...

2001-03-27 Thread Gabriel Ambuehl
-BEGIN PGP SIGNED MESSAGE- Hello Makoto, Tuesday, March 27, 2001, 7:55:15 PM, you wrote: gabriel_ambuehl>> I can't seem to be able to build 5-CURRENT since several days. > You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't > have, it's your problem. The CVS reposit

Re: Can't build current...

2001-03-27 Thread Makoto MATSUSHITA
gabriel_ambuehl> I can't seem to be able to build 5-CURRENT since several days. You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't have, it's your problem. The CVS repository has this file already: http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blowfish.c

Can't build current...

2001-03-27 Thread Gabriel Ambuehl
-BEGIN PGP SIGNED MESSAGE- Hello, I can't seem to be able to build 5-CURRENT since several days. I just cvsupped again (tracking everything on CURRENT branch) but I always run into the following: sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libmd.a /usr/obj/usr/src/i386/usr/

Can't build current...

2001-03-27 Thread Gabriel Ambuehl
-BEGIN PGP SIGNED MESSAGE- Hello, I can't seem to be able to build 5-CURRENT since several days. I just cvsupped again (tracking everything on CURRENT branch) but I always run into the following: sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 libmd.a /usr/obj/usr/src/i386/usr/