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
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/
> 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
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"
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
> 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
> 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
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
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
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
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
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
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: l
* 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.
* 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
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
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
* 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
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
On Mon, Apr 29, 2002 at 10:33:05 +0300, Ruslan Ermilov wrote:
> On Sun, Apr 28, 2002 at 10:27:10PM -0600, Kenneth D. Merry wrote:
> >
> > I'm trying to build -current from today (4/28/2002) on a -stable box with a
> > kernel/world from April 25th.
> >
> > It blows up in xlint:
> >
> > =
On Sun, Apr 28, 2002 at 10:27:10PM -0600, Kenneth D. Merry wrote:
>
> I'm trying to build -current from today (4/28/2002) on a -stable box with a
> kernel/world from April 25th.
>
> It blows up in xlint:
>
> ==
> cc -O
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
> 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
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
24 matches
Mail list logo
