from matthew sporleder:
> Can you take a step back and try using default tools (gcc) and a clean
> dir (build.sh -r should do it, or just completely delete your obj and
> tool dir first)?
That's what I did originally when I failed several times, but I could try
again, omitting -j.
What about wi
On Sun, Dec 15, 2013 at 8:05 PM, Thomas Mueller
wrote:
>
> Matt Sporleder asks:
>
> > What is your build.sh command?
>
> > Did the build ever work?
>
> Latest build.sh command was
>
> ===> build.sh command:./build.sh -m amd64 -M ../obj.amd64.llvm -B
> nb20131214-llvm -T ../tooldir.amd64.llvm
On Mon, Dec 16, 2013 at 12:49:23PM +, Thomas Mueller wrote:
> > "clean out the tools directory" means to remove the -T directory,
> > i.e. ../tooldir.amd64.llvm in your case.
>
> That's what I first thought, but I was beginning to wonder if I need to do
> a new cvs checkout or update after
On Sun, Dec 15, 2013 at 11:34:39AM +, Thomas Mueller wrote:
> My /etc/mk.conf is geared to pkgsrc, I don't see anything relevant to
> building the system.
If you encapsulate the pkgsrc settings in a block like this ...
.if defined(BSD_PKG_MK)
[...]
.endif
... you can be sure that they don't
On Sun, 15 Dec 2013, Thomas Mueller wrote:
My /etc/mk.conf is geared to pkgsrc, I don't see anything
relevant to building the system.
Is all the pkgsrc-related stuff protected by ".if defined(BSD_PKG_MK)" ?
If not, then it will be used for a system build too.
There was a suggestion to set -std
from John Nemeth:
> "clean out the tools directory" means to remove the -T directory,
> i.e. ../tooldir.amd64.llvm in your case.
That's what I first thought, but I was beginning to wonder if I need to do a
new cvs checkout or update after deleting entire source tree.
I've removed the tooldi
On Dec 16, 1:05am, "Thomas Mueller" wrote:
} Subject: Re: READ ME: updating mpc, mpfr, and eventually gmp
} Matt Sporleder asks:
}
} > What is your build.sh command?
}
} > Did the build ever work?
}
} Latest build.sh command was
}
} ===> build.sh command:./b
Matt Sporleder asks:
> What is your build.sh command?
> Did the build ever work?
Latest build.sh command was
===> build.sh command:./build.sh -m amd64 -M ../obj.amd64.llvm -B
nb20131214-llvm -T ../tooldir.amd64.llvm -V MKLLVM=yes -V HAVE_LLVM=yes -V
MKLIBCXX=yes -U -j 9 distribution kern
On Dec 15, 2013, at 6:34 AM, "Thomas Mueller" wrote:
>>> This is in particular a sudden inability to build NetBSD-current from
>>> source.
>
>> Those happen, and are usually fixed by reading UPDATING and doing what it
>> recommends (or in the case of obvious breaks, waiting a day, updating
> >This is in particular a sudden inability to build NetBSD-current from source.
> Those happen, and are usually fixed by reading UPDATING and doing what it
> recommends (or in the case of obvious breaks, waiting a day, updating and
> running the build again).
> -current is built by umpte
Hi,
mueller6...@bellsouth.net ("Thomas Mueller") writes:
>from Paul Goyette:
>> I've had intermittent similar problems with NetBSD for at least three
>> years now. I have no idea what the problem is, though. I've
>> suspected some sort of memory corruption, but was never able to make
>> any pr
> > Last failure was on gmp, which later built successfully as a dependency
> > from pkgsrc.
> ah, i see the confusion here.
> my post was *only* about the in-tree gmp/mpfr/mpc that we use
> for the in-tree gcc and for building netbsd, and has nothing
> to do with the versions in
> Last failure was on gmp, which later built successfully as a dependency from
> pkgsrc.
ah, i see the confusion here.
my post was *only* about the in-tree gmp/mpfr/mpc that we use
for the in-tree gcc and for building netbsd, and has nothing
to do with the versions in pkgsrc. i don't maintain
On Mon, 2 Dec 2013, matthew green wrote:
> > This is in particular a sudden inability to build NetBSD-current from
> > source.
>
> could you be more explicit about what is failing? there
> shouldn't be any issues remaining, but some types of
> failure modes require cleaning out your build/obj t
> > This is in particular a sudden inability to build NetBSD-current from
> > source.
> could you be more explicit about what is failing? there
> shouldn't be any issues remaining, but some types of
> failure modes require cleaning out your build/obj trees,
> and won't go away with any amount of
> This is in particular a sudden inability to build NetBSD-current from source.
could you be more explicit about what is failing? there
shouldn't be any issues remaining, but some types of
failure modes require cleaning out your build/obj trees,
and won't go away with any amount of cvs update.
from Paul Goyette:
> I've had intermittent similar problems with NetBSD for at least three
> years now. I have no idea what the problem is, though. I've
> suspected some sort of memory corruption, but was never able to make
> any progress in tracking it down.
It could be a corruption or bug in
I've had intermittent similar problems with NetBSD for at least three
years now. I have no idea what the problem is, though. I've suspected
some sort of memory corruption, but was never able to make any progress
in tracking it down.
On Sun, 1 Dec 2013, Thomas Mueller wrote:
Base gcc
> Base gcc hasn't been updated. Updating mpc, mpfr, and gmp
> are part of the preparation for update base gcc. "Segfault due to
> internal compiler error" is often due to bad memory. You might
> want to run pkgsrc/sysutils/memtestplus.
I tried again, this time noticed that the choking poin
> Base gcc hasn't been updated. Updating mpc, mpfr, and gmp
> are part of the preparation for update base gcc. "Segfault due to
> internal compiler error" is often due to bad memory. You might
> want to run pkgsrc/sysutils/memtestplus.
Or it could be a bug in the NetBSD system.
These happ
On Nov 29, 6:42am, "Thomas Mueller" wrote:
}
} > this is a warning that builds might fail due to the updated mpc
} > and mpfr sources i've imported. you might need to clean both
} > the tools and normal build dirs for them.
}
} > please send-pr or send me email if you see issues. thanks
> this is a warning that builds might fail due to the updated mpc
> and mpfr sources i've imported. you might need to clean both
> the tools and normal build dirs for them.
> please send-pr or send me email if you see issues. thanks!
> .mrg.
I cleaned the tools and obj
22 matches
Mail list logo
