Re: Building -CURRENT on -STABLE

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

Building -CURRENT on -STABLE

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]

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 >

building current with meta mode

#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

Re: Building Current

> 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 ___

Re: Building Current

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

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

> 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

Re: Building Current

> 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

Building Current

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

Error building -CURRENT from 10.1

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 [...]

Re: Error building -CURRENT from 10.1

On Jun 3, 2015, at 12:35 PM, Steve Kargl s...@troutmask.apl.washington.edu 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.

Re: Error building -CURRENT from 10.1

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

Re: Error building -CURRENT from 10.1

On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote: On Jun 3, 2015, at 12:35 PM, Steve Kargl s...@troutmask.apl.washington.edu 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?

Re: Error building -CURRENT from 10.1

On Jun 3, 2015, at 12:44 PM, Baptiste Daroussin b...@freebsd.org wrote: On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote: On Jun 3, 2015, at 12:35 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson

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

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 kaput: ...

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

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 22

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

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 FreeBSD

Re: problem building -current

On May 7, 2013, at 16:10, Dimitry Andric d...@freebsd.org wrote: On 2013-05-07 16:01, Sergey Kandaurov wrote: On 7 May 2013 17:21, Michael W. Lucas mwlu...@michaelwlucas.com wrote: ... c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include

problem building -current

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

Re: problem building -current

On 7 May 2013 17:21, Michael W. Lucas mwlu...@michaelwlucas.com 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

Re: problem building -current

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

Problem building current

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

Re: Building -CURRENT with 4.5-RELEASE

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: Building -CURRENT with 4.5-RELEASE

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 point?

Installworld fails building Current from 4.7-R

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: Installworld fails building Current from 4.7-R

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

Re: Installworld fails building Current from 4.7-R

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 PM Subject: Re: Installworld fails building Current from

Re: Installworld fails building Current from 4.7-R

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

Re: Installworld fails building Current from 4.7-R

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 need to run

Re: Installworld fails building Current from 4.7-R

[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

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

Re: building -CURRENT on RELENG_4

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: illegal option -- m usage: lint1

Re: Building -CURRENT with 4.5-RELEASE

* 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. No,

Re: Building -CURRENT with 4.5-RELEASE

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. Cheers,

building -CURRENT on RELENG_4

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 --- cut here

Re: Building -CURRENT with 4.5-RELEASE

* 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 with as

Re: Building -CURRENT with 4.5-RELEASE

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 -CURRENT?

Re: Building -CURRENT with 4.5-RELEASE

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 mean an

Re: Building -CURRENT with 4.5-RELEASE

* 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 need to use a

Building -CURRENT with 4.5-RELEASE

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

. 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. Ditto. I have managed to build a current world on RELENG_4 only with Alexander's patch

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

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'm

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

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 versions

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

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

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

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 you try yet

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

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, I

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

/~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 Institute smime.p7s Description: S/MIME Cryptographic Signature

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

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

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 ago

Trouble Building CURRENT on STABLE, cpp seg. fault

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 on Sat Sep 21 23

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

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,

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

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't just you. The same error stopped my

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

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? Is there a problem with building CURRENT

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

. 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. if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V

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

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 with building CURRENT on STABLE at the moment? It isn't just

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

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: building -current on -stable broken?

. == Am I doing something wrong here or is building -current on -stable broken? Seems to work OK here; xcalloc() and xmalloc() are defined in mem.c. The problem I'm having is a stale version of xlint/lint1/mem.c in my cvsup-perforce gateway tree. cvs has a similar problem. If I

Re: building -current on -stable broken?

/FreeBSD-ken/src. *** 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? Seems

building -current on -stable broken?

in /c/ken/perforce/FreeBSD-ken/src. == Am I doing something wrong here or is building -current on -stable broken? Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe

Weirdness in building -CURRENT today

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

Re: Weirdness in building -CURRENT today

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

Re: Weirdness in building -CURRENT today

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 least, did not

Re: Weirdness in building -CURRENT today

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

Re: Weirdness in building -CURRENT today

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

Re: Weirdness in building -CURRENT today

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

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

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.

: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

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

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

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

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/3dfx. ***

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

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

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

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 be more

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

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

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

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

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

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: found the fragger. Re: Problem building -current kernel with read-only /usr/src.

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

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

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.

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

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: Problem building -current kernel with read-only /usr/src.

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.

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

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

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

Building -current kernel on ref5 broken ?

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

Problem building -current kernel

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

Re: Problem building -current kernel

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

Re: Error building current

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 something?

Re: Error building current

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

Re: Error building current

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 hadn't

Error building current

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