Hello again,
I have finally completed the leviathan task of my first gcc compilation and
test.
I am encouraged to have only one unexpected failure outside libmudflap.
This leaves me with two questions.
1. How bad is that error? I have inferred that it is probably infrequent - but
it does no
On Thu, Oct 31, 2013 at 01:28:09PM +, Richard wrote:
Hello again,
I have finally completed the leviathan task of my first gcc compilation and
test.
I am encouraged to have only one unexpected failure outside libmudflap.
This leaves me with two questions.
1. How bad is that
From: Ken Moffat zarniwh...@ntlworld.com
...
Are you using the 7.4 book or svn ? If you are using gcc-4.8.2
then I have no data to offer.
...
I am (I hope!) using the plain, normal, generic, unadulterated LFS 7.4 - which
means that I just compiled gcc 4.8.1.
I
On Thu, Oct 31, 2013 at 03:26:35PM +, Richard wrote:
From: Ken Moffat zarniwh...@ntlworld.com
...
Are you using the 7.4 book or svn ? If you are using gcc-4.8.2
then I have no data to offer.
...
I am (I hope!) using the plain, normal, generic,
On Oct 31, 2013, at 8:28 AM, Richard wrote:
1. How bad is that error? I have inferred that it is probably
infrequent - but it does no harm to check...
(FAIL: g++.dg/asan/asan_test.C -O2 AddressSanitizer_HugeMallocTest
Ident((char*)malloc(size))[-1] = 0 output pattern test, should match
So that I can hit the deck running after I get my new system to boot,
I want to add a few packages, and their associated boot scripts, from
BLFS. These are dhcpd, wpa-supplicant, libxml, libn, open-ssl and
d-bus. I seem to remember reading somewhere, and I thought it was in
the LFS book,
Em 31-10-2013 16:28, Dan McGhee escreveu:
So that I can hit the deck running after I get my new system to boot,
I want to add a few packages, and their associated boot scripts, from
BLFS. These are dhcpd, wpa-supplicant, libxml, libn, open-ssl and
d-bus. I seem to remember reading
On Thu, Oct 31, 2013 at 02:28:27PM -0500, Dan McGhee wrote:
So that I can hit the deck running after I get my new system to boot,
I want to add a few packages, and their associated boot scripts, from
BLFS. These are dhcpd, wpa-supplicant, libxml, libn, open-ssl and
d-bus. I seem to
On 10/31/2013 03:02 PM, Ken Moffat wrote:
There used to be some packages that gave problems if building in
chroot. But I don't remember what they were. In the last couple of
years I've done some complete builds in chroot while I sorted out
changes to my build scripts, so I don't think
Op Thu, 31 Oct 2013 21:02:22 +0100 schreef Ken Moffat zarniwh...@ntlworld.com:
On Thu, Oct 31, 2013 at 02:28:27PM -0500, Dan McGhee wrote:
So that I can hit the deck running after I get my new system to boot,
I want to add a few packages, and their associated boot scripts, from
BLFS. These
Dan McGhee wrote:
So that I can hit the deck running after I get my new system to boot,
I want to add a few packages, and their associated boot scripts, from
BLFS. These are dhcpd, wpa-supplicant, libxml, libn, open-ssl and
d-bus. I seem to remember reading somewhere, and I thought it was in
On 10/31/2013 03:51 PM, Bruce Dubbs wrote:
Dan McGhee wrote:
So that I can hit the deck running after I get my new system to boot,
I want to add a few packages, and their associated boot scripts, from
BLFS. These are dhcpd, wpa-supplicant, libxml, libn, open-ssl and
d-bus. I seem to
On Thu, Oct 31, 2013 at 06:07:03PM -0500, Dan McGhee wrote:
I also have my sources in /usr/src and that is a separate partition so I
can use it from any build. I recommend the following as separate
partitions: /boot, /home, and /usr/src. /opt is also a possibility.
-- Bruce
I
13 matches
Mail list logo
