Re: Building -CURRENT on -STABLE

2020-01-12 Thread Gordon Bergling
Hi, if someone is facing the same error, the build variable MAKEOBJDIRPREFIX must be set within the environment and _not_ within the make context. I would also suggest that the source and object directories are on the same partition. My sources where located in my home directory and the object

Building -CURRENT on -STABLE

2020-01-09 Thread Gordon Bergling
Hi, I am currently about to setup an -CURRENT system, which should gets updated via a build server that’s runs on -STABLE and shares the src and obj directories via NFS to -CURRENT system. While doing a „make -s -j 4 buildworld buildkernel“ the builds fails randomly with the following error. ---

Re: building current with DIRDEPS_BUILD [was meta mode]

2018-03-03 Thread Bryan Drewery
On 3/3/2018 10:13 AM, Eitan Adler wrote: > #make toolchain > This is now known as DIRDEPS_BUILD. META_MODE is something different now, see man src.conf. This failure is not unexpected as the build breaks with LLVM updates. I'll work on a fix this next week. > ... > Building > /srv/obj/srv/src/

building current with meta mode

2018-03-03 Thread Eitan Adler
#make toolchain ... Building /srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full c++: error: no such file or directory: '/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminimal.a' *** Error code 1 Stop. make[1]: stopped in /srv/src/fbsd/head/usr.bin/

Re: Building Current

2017-03-04 Thread Ngie Cooper
> On Mar 4, 2017, at 13:19, Roberto Rodriguez Jr wrote: > > Would make -DNO_CLEAN=NO also/maybe help as well? Remove =NO from your invocation above. That would define a variable as: ${NO_CLEAN=NO}=1 HTH, -Ngie ___ freebsd-current@freebsd.org mailing

Re: Building Current

2017-03-04 Thread Roberto Rodriguez Jr
Would make -DNO_CLEAN=NO also/maybe help as well? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building Current

2017-03-04 Thread Navdeep Parhar
On Sat, Mar 04, 2017 at 03:46:20PM -0500, Roberto Rodriguez Jr wrote: > What tools can I use to make the building a little faster? > The src tree supports incremental builds. You'll need to load the filemon module and add WITH_META_MODE=yes in /etc/src-env.conf to use it. See the WITH_META_MODE

Re: Building Current

2017-03-04 Thread Manfred Antar
> On Mar 4, 2017, at 12:46 PM, Roberto Rodriguez Jr > wrote: > > What tools can I use to make the building a little faster? > > I'm using an AMD 64 HP 15 laptop and I update the source tree daily and > rebuild so if I have any errors I could report. Just curious if there's any > extra software

Re: Building Current

2017-03-04 Thread Manfred Antar
> On Mar 4, 2017, at 12:46 PM, Roberto Rodriguez Jr > wrote: > > What tools can I use to make the building a little faster? > > I'm using an AMD 64 HP 15 laptop and I update the source tree daily and > rebuild so if I have any errors I could report. Just curious if there's any > extra software

Building Current

2017-03-04 Thread Roberto Rodriguez Jr
What tools can I use to make the building a little faster? I'm using an AMD 64 HP 15 laptop and I update the source tree daily and rebuild so if I have any errors I could report. Just curious if there's any extra software I could be implementing to make the compiling faster. Thank you

Re: Error building -CURRENT from 10.1

2015-06-03 Thread Jonathan Anderson
> > On Jun 3, 2015, at 12:44 PM, Baptiste Daroussin wrote: > > On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote: >>> >>> On Jun 3, 2015, at 12:35 PM, Steve Kargl >>> wrote: >>> >>> On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote: So, how do I boo

Re: Error building -CURRENT from 10.1

2015-06-03 Thread Baptiste Daroussin
On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote: > > > > On Jun 3, 2015, at 12:35 PM, Steve Kargl > > wrote: > > > > On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote: > >> > >> So, how do I bootstrap 11-CURRENT from 10.1-RELEASE? > >> > > > > Update your so

Re: Error building -CURRENT from 10.1

2015-06-03 Thread Jonathan Anderson
> > On Jun 3, 2015, at 12:35 PM, Steve Kargl > wrote: > > On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote: >> >> So, how do I bootstrap 11-CURRENT from 10.1-RELEASE? >> > > Update your source tree. My source tree is up-to-date as of a few hours ago. Jon -- jonat...@freeb

Re: Error building -CURRENT from 10.1

2015-06-03 Thread Steve Kargl
On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote: > > So, how do I bootstrap 11-CURRENT from 10.1-RELEASE? > Update your source tree. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fre

Error building -CURRENT from 10.1

2015-06-03 Thread Jonathan Anderson
Hi all, I’m attempting to `make buildworld` from a 10.1-RELEASE box, and I’m encountering an error in the “bootstrap tools" stage. It looks like gzip, which is part of the bootstrap tools, depends on `futimens` from a newish (since February?) libc / syscall API: $ make buildworld [...] usr.bin

Re: Building current no longer possible on 8.2, worked 7 days ago

2013-05-22 Thread Ulrich Spörlein
On Tue, 2013-05-21 at 04:10:30 +0200, Ulrich Spörlein wrote: > On Mon, 2013-05-20 at 23:06:40 +0200, Matthias Andree wrote: > > Am 20.05.2013 15:49, schrieb Ulrich Spörlein: > > > Hey all, > > > > > > I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d > > > ago, now it's kapu

Re: Building current no longer possible on 8.2, worked 7 days ago

2013-05-20 Thread Ulrich Spörlein
On Mon, 2013-05-20 at 23:06:40 +0200, Matthias Andree wrote: > Am 20.05.2013 15:49, schrieb Ulrich Spörlein: > > Hey all, > > > > I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d > > ago, now it's kaput: > > ... > > > This is on src r250825 and the host is running > > Fre

Re: Building current no longer possible on 8.2, worked 7 days ago

2013-05-20 Thread Matthias Andree
Am 20.05.2013 15:49, schrieb Ulrich Spörlein: > Hey all, > > I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d > ago, now it's kaput: ... > This is on src r250825 and the host is running > FreeBSD scan.freebsd.your.org 8.2-STABLE FreeBSD 8.2-STABLE #2 r223420: Wed > Jun 2

Building current no longer possible on 8.2, worked 7 days ago

2013-05-20 Thread Ulrich Spörlein
Hey all, I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d ago, now it's kaput: >>> Building an up-to-date make(1) >>> World build started on Mon May 20 13:43:09 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims -

Re: problem building -current

2013-05-13 Thread Dimitry Andric
On May 7, 2013, at 16:10, Dimitry Andric wrote: > On 2013-05-07 16:01, Sergey Kandaurov wrote: >> On 7 May 2013 17:21, Michael W. Lucas wrote: > ... >>> c++ -O2 -pipe >>> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include >>> -I/usr/src/lib/clang/libllvmsupport/../../../contrib/

Re: problem building -current

2013-05-07 Thread Dimitry Andric
On 2013-05-07 16:01, Sergey Kandaurov wrote: On 7 May 2013 17:21, Michael W. Lucas wrote: ... c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmsupport/../

Re: problem building -current

2013-05-07 Thread Sergey Kandaurov
On 7 May 2013 17:21, Michael W. Lucas wrote: > > Hi, > > I'm running an older -current: > > bewilderbeast/usr/src;uname -a > FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT > #15: Thu Nov 8 14:02:45 EST 2012 > mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/

problem building -current

2013-05-07 Thread Michael W. Lucas
Hi, I'm running an older -current: bewilderbeast/usr/src;uname -a FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/G Trying to build new, and get: ... c++ -O2 -p

Problem building current

2011-12-05 Thread Alexander Yerenkow
Hello. I think I have some problem building current on my system (which is not current). # uname -a FreeBSD 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:51:43 UTC 2011 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # pwd /zpool0/testenv/sources/10-kms/lib/libc # svn info Path

Building -current on -stable box => install broken?

2003-07-09 Thread Ruben de Groot
Hi, I've been building -current on a 4.x buildmachine on a daily basis for about a year. The /usr/obj and /usr/src directories are nfs exported to a testmachine running -current. After I came back from holiday a few days ago I noticed that the install on the -current machine gave m

Re: Building -CURRENT with 4.5-RELEASE

2002-10-26 Thread Ulrich 'Q' Spoerlein
On Tue, 22 Oct 2002 04:25:23 +0200, you wrote: >Is it possible, or do I need to use a more recent installation to be able to >build -CURRENT? it was possible for me, but i had to go through a lot of hassles installing -CURRENT from within -STABLE. i used the DESTDIR-switch to install everything

Re: Installworld fails building Current from 4.7-R

2002-10-25 Thread M. Warner Losh
What does uname -a say in single user. It should say 5.0, but I'd guess it is saying 4.x. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Building -CURRENT with 4.5-RELEASE

2002-10-25 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Tim Kientzle <[EMAIL PROTECTED]> writes: : > On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard H=E4ring wrote: : : >>"make installworld" dumps core at installing passwd (4.5-RELEASE). : : : Brooks Davis: : : > Are you running a current kernel at this

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread The Gupta Age
| |I've run into the same problem in the past but manually selected the new |kernel. Should we add the explicit step that you need to load |/boot/kernel/kernel when upgrading? Or has that been fixed? | |-Nate I have posted atleast twice on current to add this info to UPDATING. guess it still ha

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Nate Lawson
[Redirected to current@ with sender's approval] On Thu, 24 Oct 2002, Mike Hunter wrote: > On Thu, 24 Oct 2002, Nate Lawson wrote: > > > That's why there is a "reboot" between installing the new kernel and doing > > installworld. You need to run the new kernel to have the ABI match. > > From my

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Nate Lawson
On Thu, 24 Oct 2002, Mike Hunter wrote: > On Thu, 24 Oct 2002, Richard Cotrina wrote: > > > Yes, I did. However make installworld fails as I said. > > I ran into the same problem going from 4.6 to 5.0-CURRENT. > > We used truss to see that sh was making funny calls, and concluded that > we'd nee

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Mike Hunter
On Thu, 24 Oct 2002, Richard Cotrina wrote: > Yes, I did. However make installworld fails as I said. I ran into the same problem going from 4.6 to 5.0-CURRENT. We used truss to see that sh was making funny calls, and concluded that we'd need to run from the kernel to get it working. We instal

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Richard Cotrina
Yes, I did. However make installworld fails as I said. - Original Message - From: "Craig Rodrigues" <[EMAIL PROTECTED]> To: "Richard Cotrina" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, October 24, 2002 5:02

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Craig Rodrigues
Hi, Did you see the instructions in /usr/src/Makefile and /usr/src/UPDATING? This is from /usr/src/Makefile: # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make build

Installworld fails building Current from 4.7-R

2002-10-24 Thread Richard Cotrina
Hello : I am getting an strange error when trying to install current ( make installworld ). I cvsup-ed it in my 4.7- Release box, and I sompiling the sources and the kernel without any error messages : # make -j4 buildworld # make buildkernel # make installkernel # reboot All the above finished

Re: building -CURRENT on RELENG_4

2002-10-23 Thread Ruslan Ermilov
On Wed, Oct 23, 2002 at 01:08:31AM +0700, Max Khon wrote: > hi, there! > > cross-building -CURRENT on RELENG_4 is broken in src/usr.bin/xlint/lint1: > > --- cut here --- > ... > sh /usr/fbsd/HEAD/src/usr.bin/xlint/lint1/makeman /usr/libexec/lint1 -m >lint.7 > lint1:

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Gerhard Haering
* Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 16:55 -0700]: > On Wed, Oct 23, 2002 at 01:48:14AM +0200, Gerhard H?ring wrote: > > * Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 15:01 -0700]: > > > Are you running a current kernel at this point? If you aren't it's safe > > > to say it won't work.

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Gerhard Häring
* Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 15:01 -0700]: > On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard Häring wrote: > > * Ruslan Ermilov <[EMAIL PROTECTED]> [2002-10-22 12:23 +0300]: > > > On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote: > > > > Is it possible, or do I ne

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Brooks Davis
On Wed, Oct 23, 2002 at 01:48:14AM +0200, Gerhard Häring wrote: > * Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 15:01 -0700]: > > Are you running a current kernel at this point? If you aren't it's safe > > to say it won't work. > > No, this is 4.5-RELEASE, as I said. By "current kernel", do you

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Brooks Davis
On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard Häring wrote: > * Ruslan Ermilov <[EMAIL PROTECTED]> [2002-10-22 12:23 +0300]: > > On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote: > > > Is it possible, or do I need to use a more recent installation to be able to > > > build -CURRE

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Gerhard Häring
* Ruslan Ermilov <[EMAIL PROTECTED]> [2002-10-22 12:23 +0300]: > On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote: > > Is it possible, or do I need to use a more recent installation to be able to > > build -CURRENT? > > > Yes, it is. It should even be possible to build -CURRENT wit

building -CURRENT on RELENG_4

2002-10-22 Thread Max Khon
hi, there! cross-building -CURRENT on RELENG_4 is broken in src/usr.bin/xlint/lint1: --- cut here --- ... sh /usr/fbsd/HEAD/src/usr.bin/xlint/lint1/makeman /usr/libexec/lint1 -m >lint.7 lint1: illegal option -- m usage: lint1 [-abcdeghprstuvyzF] src dest gzip -cn lint.7 > lint.7.gz --- cu

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Ruslan Ermilov
On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote: > Is it possible, or do I need to use a more recent installation to be able to > build -CURRENT? > Yes, it is. It should even be possible to build -CURRENT with as early as 4.0-RELEASE. If it doesn't, please drop me a line. Cheer

Building -CURRENT with 4.5-RELEASE

2002-10-21 Thread Gerhard Haering
Is it possible, or do I need to use a more recent installation to be able to build -CURRENT? -- Gerhard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-25 Thread Crist J. Clark
On Tue, Sep 24, 2002 at 06:13:33PM -0400, Alexander Kabaev wrote: > > Nope, still getting it. > > I was able to reproduce the crash with your config file and unpatched > GCC, however crash does not happen when I use the patch. Are you using > make buildkernel or old config/make method? Since I'

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-25 Thread Giorgos Keramidas
> > >You are right. There was a stupid mistake in the latest version, sorry. > >Could you try yet another patch? > > > >http://people.freebsd.org/~kan/gcc-cpp.diff > > FYI, I saw the same error as Crist when building -current under 4.6, > and with your patch, th

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Lars Eggert
t; Could you try yet another patch? > > http://people.freebsd.org/~kan/gcc-cpp.diff FYI, I saw the same error as Crist when building -current under 4.6, and with your patch, the buildworld/buildkernel succeeded. Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Alexander Kabaev
> Nope, still getting it. I was able to reproduce the crash with your config file and unpatched GCC, however crash does not happen when I use the patch. Are you using make buildkernel or old config/make method? > > options IPSEC_ESP > > That is killing it. If I comment out that option,

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Crist J. Clark
On Tue, Sep 24, 2002 at 11:43:22AM -0400, Alexander Kabaev wrote: > On Tue, 24 Sep 2002 00:00:45 -0700 > "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > > > Not too sure about that. Now I'm getting SIGSEGV again, > > You are right. There was a stupid mistake in the latest version, sorry. > Could y

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Alexander Kabaev
On Tue, 24 Sep 2002 00:00:45 -0700 "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > Not too sure about that. Now I'm getting SIGSEGV again, You are right. There was a stupid mistake in the latest version, sorry. Could you try yet another patch? http://people.freebsd.org/~kan/gcc-cpp.diff -- Alex

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-23 Thread Crist J. Clark
On Mon, Sep 23, 2002 at 03:59:46PM -0400, Alexander Kabaev wrote: > On Mon, 23 Sep 2002 12:55:49 -0700 > "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > > > It seems to have worked. Thanks. > > Sorry for inconvenience, but could you please check that you got the > latest version of the patch. Both

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-23 Thread Alexander Kabaev
On Mon, 23 Sep 2002 12:55:49 -0700 "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > It seems to have worked. Thanks. Sorry for inconvenience, but could you please check that you got the latest version of the patch. Both versions will fix the bug, but the version I copied on freefall several hours a

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-23 Thread Crist J. Clark
On Sun, Sep 22, 2002 at 11:09:56PM -0400, Alexander Kabaev wrote: > I am asking people having CPP0 dying with SIG11 to try the patch at URL > below. Success/failure reports are appreciated. > > http://people.freebsd.org/~kan/gcc-cpp.diff It seems to have worked. Thanks. -- Crist J. Clark

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Alexander Kabaev
I am asking people having CPP0 dying with SIG11 to try the patch at URL below. Success/failure reports are appreciated. http://people.freebsd.org/~kan/gcc-cpp.diff -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Jim Bloom
Giorgos Keramidas wrote: > > On 2002-09-21 23:53, "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > > I've been unable to build CURRENT on STABLE for a few days. I made > > sure to bring STABLE up to date. Is this just me? Is there a problem > >

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread qhwt
I made > > > sure to bring STABLE up to date. Is this just me? Is there a problem > > > with building CURRENT on STABLE at the moment? > > > > It isn't just you. The same error stopped my build of current 2-3 > > days ago on 4.6-RELEASE. > > > >

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread qhwt
On Sun, Sep 22, 2002 at 02:44:54PM +0300, Giorgos Keramidas wrote: > On 2002-09-21 23:53, "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > > I've been unable to build CURRENT on STABLE for a few days. I made > > sure to bring STABLE up to date. Is this just me?

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Giorgos Keramidas
On 2002-09-21 23:53, "Crist J. Clark" <[EMAIL PROTECTED]> wrote: > I've been unable to build CURRENT on STABLE for a few days. I made > sure to bring STABLE up to date. Is this just me? Is there a problem > with building CURRENT on STABLE at the moment? It isn'

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Maxim Konovalov
Works for me: >>> Kernel build for GENERIC completed on Sun Sep 22 07:43:35 MSD 2002 $ uname -a FreeBSD golf.macomnet.net 4.6-20020805-MACOMNET-STABLE FreeBSD 4.6-20020805-MACOMNET-STABLE #19: Fri Sep 20 17:09:52 MSD 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GOLF i386. -- Maxim Konovalov,

Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-21 Thread Crist J. Clark
I've been unable to build CURRENT on STABLE for a few days. I made sure to bring STABLE up to date. Is this just me? Is there a problem with building CURRENT on STABLE at the moment? -- >>> Kernel build for GOKU started

Re: building -current on -stable broken?

2002-05-01 Thread Kenneth D. Merry
> Stop in /c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1. > > *** Error code 1 > > > > Stop in /c/ken/perforce/FreeBSD-ken/src. > > *** Error code 1 > > > > Stop in /c/ken/perforce/FreeBSD-ken/src. > > *** Error code 1 > > > > Stop in /c/ke

Re: building -current on -stable broken?

2002-04-29 Thread Ruslan Ermilov
en/src. > *** Error code 1 > > Stop in /c/ken/perforce/FreeBSD-ken/src. > == > > Am I doing something wrong here or is building -current on -stable broken? > Seems to work OK here; xcalloc() and

building -current on -stable broken?

2002-04-28 Thread Kenneth D. Merry
*** Error code 1 Stop in /c/ken/perforce/FreeBSD-ken/src. *** Error code 1 Stop in /c/ken/perforce/FreeBSD-ken/src. ====== Am I doing something wrong here or is building -current on -stable broken? Ken -- Kenneth Merr

Re: Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill
>Date: Wed, 30 Jan 2002 18:31:14 +0200 >From: Ruslan Ermilov <[EMAIL PROTECTED]> > stage 2: cleaning up the object tree >>-- >>... >>===> lib/libc >>"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a >>"/usr/

Re: Weirdness in building -CURRENT today

2002-01-30 Thread Ruslan Ermilov
On Wed, Jan 30, 2002 at 07:41:51AM -0800, David Wolfskill wrote: > >Date: Wed, 30 Jan 2002 17:02:07 +0200 > >From: Ruslan Ermilov <[EMAIL PROTECTED]> > > > >> stage 2: cleaning up the object tree > >> >-- > >> >... > >> >===> lib/l

Re: Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill
>Date: Wed, 30 Jan 2002 17:02:07 +0200 >From: Ruslan Ermilov <[EMAIL PROTECTED]> >> stage 2: cleaning up the object tree >> >-- >> >... >> >===> lib/libc >> >"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.

Re: Weirdness in building -CURRENT today

2002-01-30 Thread Ruslan Ermilov
On Wed, Jan 30, 2002 at 06:33:43AM -0800, David Wolfskill wrote: > >Date: Wed, 30 Jan 2002 05:58:24 -0800 (PST) > >From: David Wolfskill <[EMAIL PROTECTED]> > > >cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e > >tc/rc,v > >freebeast(4.5-STA)[2] > > That, at lea

Re: Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill
>Date: Wed, 30 Jan 2002 05:58:24 -0800 (PST) >From: David Wolfskill <[EMAIL PROTECTED]> >cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e >tc/rc,v >freebeast(4.5-STA)[2] That, at least, did not occur on my laptop. stage 2: cleaning up the object tree >

Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill
I think today is going to be "one of those days" :-( The first hint was after I built today's -STABLE, I then fired up a "cvs update" against my -CURRENT sources, and got: Script started on Wed Jan 30 05:12:16 2002 freebeast(4.5-STA)[1] cd /S4/usr/src && cvs update^M cvs update: Updating .

Re: Problem building -current kernel with read-only /usr/src.

2000-12-24 Thread Matt Dillon
:On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote: : :I will fix it today. Works like a charm now, thanks! My -current source is broken out on my -stable machine, so the only way to compile it is via an NFS mount to a -current machine which, for obvious reasons, needs to

Re: Problem building -current kernel with read-only /usr/src.

2000-12-24 Thread Max Khon
hi, there! On Sat, 23 Dec 2000, Chris wrote: > Actually, last time I checked, I think stable did not install with a RO > /usr/src either. Anyone know if this is still the case? I have no problems with 'make installworld' with RO obj and src on latest -stable /fjoe To Unsubscribe: send mail

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon
: :> Actually, last time I checked, I think stable did not install with a RO :> /usr/src either. Anyone know if this is still the case? : :I have installed -stable many times with /usr/src mounted readonly :via NFS. : :Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] Yah, -stable is fine.

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread sthaug
> Actually, last time I checked, I think stable did not install with a RO > /usr/src either. Anyone know if this is still the case? I have installed -stable many times with /usr/src mounted readonly via NFS. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMA

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Chris
Actually, last time I checked, I think stable did not install with a RO /usr/src either. Anyone know if this is still the case? Chris > It looks like it's trying to mess around with something in /usr/src, > which is a read-only NFS mount. Needless to say we do not want to > break

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Jeremy Lea
Hi, On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote: > Something got broken in the last week or two, it never did this sort > of thing before. David's speedup commits to sys/conf/Makefile.*. I informed him of the problem, and asked him to back out the hacks, but he wants the

Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon
:I will fix it today. : Thanks a lot Dave! -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Crist J. Clark
On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote: [snip] > I tried 'make cleandir' in /usr/src and that does not fix the problem > either. Sorry, I was not clear enough. You need to do, # cd /usr/src/sys/modules # make cleandir A 'cleandir' from /usr/src will not climb

Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread David O'Brien
On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote: > like either you or David O'Brien (I'm guessing, your guys names are I will fix it today. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

found the fragger. Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon
Ok, I found it. /usr/src/sys/conf/Makefile.i386 is broken. It looks like either you or David O'Brien (I'm guessing, your guys names are prominent in the CVS logs but I haven't tracked it down exactly) screwed up the object directory creation while trying to optimize it. It

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon
: :> While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: :> :> ===> 3dfx :> @ -> /FreeBSD/FreeBSD-current/src/sys :> ln: @: Read-only file system :> *** Error code 1 :> :> Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. :> *** Error code 1 :> :> It looks like i

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon
: :On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote: :> While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: :> :> ===> 3dfx :> @ -> /FreeBSD/FreeBSD-current/src/sys :> ln: @: Read-only file system :> *** Error code 1 :> : :Wouldn't using the buildkernel/installk

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Chris Faulhaber
On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote: > While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: > > ===> 3dfx > @ -> /FreeBSD/FreeBSD-current/src/sys > ln: @: Read-only file system > *** Error code 1 > Wouldn't using the buildkernel/installkernel targets

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Mike Smith
> While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: > > ===> 3dfx > @ -> /FreeBSD/FreeBSD-current/src/sys > ln: @: Read-only file system > *** Error code 1 > > Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. > *** Error code 1 > > It looks like it's trying to

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Crist J. Clark
On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote: > While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: > > ===> 3dfx > @ -> /FreeBSD/FreeBSD-current/src/sys > ln: @: Read-only file system > *** Error code 1 > > Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3d

Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon
While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: ===> 3dfx @ -> /FreeBSD/FreeBSD-current/src/sys ln: @: Read-only file system *** Error code 1 Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. *** Error code 1 It looks like it's trying to mess around with somet

Building -current kernel on ref5 broken ?

2000-10-29 Thread Darren Reed
Apart from the config(8) issue, I see this building GENERIC: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -I../../contrib/dev/acpica/Sub

Re: Problem building -current kernel

2000-05-22 Thread Kris Kennaway
On Mon, 22 May 2000, Stephen J. Roznowski wrote: > I'm attempting to update my -current system from mid-April, and > I'm getting the following error: make world first, or build the new binutils. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <

Problem building -current kernel

2000-05-22 Thread Stephen J. Roznowski
I'm attempting to update my -current system from mid-April, and I'm getting the following error: make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /usr/src/sys/compile/ISTARI cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wr

Re: Error building current

2000-01-20 Thread John Polstra
In article <[EMAIL PROTECTED]>, Warner Losh <[EMAIL PROTECTED]> wrote: > > I hit this problem as well. Put 'delete' in your cvsup file. > Otherwise you'll get screwed. This is a misfeature of cvsup, imho, I'm sorry you think so. I did it that way for backward compatibility with sup. If I ha

Re: Error building current

2000-01-20 Thread Warner Losh
In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote: : > CVS'uped today: : ... : > gcc/version.c is "dead" in my CVS repository. Has my repository been : > corrupted somehow? : : Please try again. Did you change release tags or som

Re: Error building current

2000-01-20 Thread David O'Brien
On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote: > CVS'uped today: ... > gcc/version.c is "dead" in my CVS repository. Has my repository been > corrupted somehow? Please try again. Did you change release tags or something? Possibly checked out RELENG_3 on top of the HEAD or somethin

Error building current

2000-01-20 Thread Tim Moore
CVS'uped today: cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools cannot open /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c: no such file "/usr/src/gnu/usr.bin/cc/cc_tools/../Makefile.inc", line 28: warning: "sed -e 's/.*\"\([^ \"]*\)[ \"].*/\1/' < /usr/src/gnu/usr.bin/cc

Re: Building -current with 3.1?

1999-06-26 Thread Anonymous
On Sat, Jun 26, 1999 at 12:53:31PM -0700, George V. Neville-Neil wrote: > > The standard compiler has changed between 3.x and -Current (gcc2.7.2.1 > > => egcs) - so don't even think of compiling code from -Current with > > Stable tools. > > > > You may want to try some "make upgrade" to upgrade a

Re: Building -current with 3.1?

1999-06-26 Thread Anonymous
> The standard compiler has changed between 3.x and -Current (gcc2.7.2.1 > => egcs) - so don't even think of compiling code from -Current with > Stable tools. > > You may want to try some "make upgrade" to upgrade all of your OS from > 3.X to 4.0 (then you will use the -Current sources for your k

Re: Building -current with 3.1?

1999-06-26 Thread Anonymous
Hello, The standard compiler has changed between 3.x and -Current (gcc2.7.2.1 => egcs) - so don't even think of compiling code from -Current with Stable tools. You may want to try some "make upgrade" to upgrade all of your OS from 3.X to 4.0 (then you will use the -Current sources for your kerne

Building -current with 3.1?

1999-06-26 Thread George V. Neville-Neil
Hi Folks, I've been getting the src-sys stuff via CVS and now want to build it. Can this be done with just the 3.1 tools (right off the CD) or do I need the compilers etc. as well? I get the following when doing a make in src/sys: ===> boot/i386/boot2 cc -elf -I/usr/local/FreeBSD-curr