On 16 January 2014 00:59, Ken Moffat zarniwh...@ntlworld.com wrote:
On Wed, Jan 15, 2014 at 04:51:23PM +, Ken Moffat wrote:
On Tue, Jan 14, 2014 at 03:50:47PM -0500, alex lupu wrote:
I would like to submit for your consideration the following changes
to the Section III. 6.7.
Greetings, back in GCC-4.8.1 again section 5.5.1 - after re-reading
everything I decided to do as suggested to try to find out why I am
having so much difficulty with this 'make'.
In the config.log I found the following fatal errors:
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
On Jan 16, 2014, at 9:46 AM, William Darryl Jackson wrote:
After the the configure appears to complete successfully. Should I
be concerned about either of these two failures?
Thanks,
William
No, it is testing a system for which compiler is installed and which
options to include for
Le 16/01/2014 16:49, William Darryl Jackson a écrit :
On 01/16/2014 10:46 AM, William Darryl Jackson wrote:
Greetings, back in GCC-4.8.1 again section 5.5.1 - after re-reading
everything I decided to do as suggested to try to find out why I am
having so much difficulty with this 'make'.
In
Em 16-01-2014 13:37, Pierre Labastie escreveu:
Le 16/01/2014 16:49, William Darryl Jackson a écrit :
On 01/16/2014 10:46 AM, William Darryl Jackson wrote:
Greetings, back in GCC-4.8.1 again section 5.5.1 - after re-reading
everything I decided to do as suggested to try to find out why I am
Hi,
I am build the LFS 7.4 following the book, and find two suspected bugs:
(1) In Preface, vii. Host System Requirements,
the version of tar is required 1.18, but this version does not support
xz format at all.As such, the following command will fail:
tar Jxvf foo.tar.xz
Although using
On 01/16/14 13:00, parmenides wrote:
Hi,
I am build the LFS 7.4 following the book, and find two suspected bugs:
(2) In chapter 5, 5.7. Glibc-2.18
I got the following warning:
configure: WARNING:
*** These auxiliary programs are missing or incompatible versions: autoconf
*** some
On Jan 16, 2014, at 12:00 PM, parmenides wrote:
(2) In chapter 5, 5.7. Glibc-2.18
I got the following warning:
configure: WARNING:
*** These auxiliary programs are missing or incompatible versions:
autoconf
*** some features will be disabled.
*** Check the INSTALL file for required
On Jan 16, 2014, at 1:04 PM, William Harrington wrote:
The New short option -J (alias for --lzma) was put in 1.20.90 which is
in 1.22.
This didn't make it,
Also for the release note: http://freecode.com/projects/tar/releases/295528
Sincerely,
William Harrington
--
Greetings,
My first pass of make produced the following error:
checking for MPFR... no
configure: error: libmpfr not found or uses a different ABI (including
static vs shared).
make[1]: *** [configure-mpc] Error 1
make[1]: Leaving directory `/mnt/lfs/sources/gcc-build'
make: *** [all] Error 2
Le 16/01/2014 22:15, William Darryl Jackson a écrit :
Greetings,
My first pass of make produced the following error:
checking for MPFR... no
configure: error: libmpfr not found or uses a different ABI (including static
vs shared).
make[1]: *** [configure-mpc] Error 1
make[1]: Leaving
Davis Abubakr-Sadik Nii Nai dwa2pac at gmail.com writes:
Hello list,
I am trying to build LFS 7.4 stable. The package check-0.9.10 in
section 5.14 failed to build.
I got it to build, but would like to ask if anyone has come across
this problem, and since it's not
Hello all. :)
I'v gone through the book a couple times in the past on i686, but this is
my first time around with x86_64. All seemed to go well until I ran into
this little gem while installing libstdc++:
...lots of compilation output...
Making install in libsupc++
make[1]: Entering directory
On 01/16/2014 04:23 PM, Pierre Labastie wrote:
Le 16/01/2014 22:15, William Darryl Jackson a écrit :
Greetings,
My first pass of make produced the following error:
checking for MPFR... no
configure: error: libmpfr not found or uses a different ABI (including static
vs shared).
make[1]:
On Thu, Jan 16, 2014 at 04:23:51PM -0600, Louis Rine wrote:
Hello all. :)
I'v gone through the book a couple times in the past on i686, but this is
my first time around with x86_64. All seemed to go well until I ran into
this little gem while installing libstdc++:
...lots of compilation
If this is the correct use of ldd...
:~$ ldd /tools/bin/x86_64-lfs-linux-gnu-ranlib
linux-vdso.so.1 = (0x7fffa837b000)
libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7ff874f03000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7ff874b3a000)
On Thu, Jan 16, 2014 at 05:47:42PM -0600, Louis Rine wrote:
If this is the correct use of ldd...
:~$ ldd /tools/bin/x86_64-lfs-linux-gnu-ranlib
linux-vdso.so.1 = (0x7fffa837b000)
libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7ff874f03000)
libc.so.6 =
Ah, I was wondering if dash would make a difference. I will fix that and
try again. Thank you. :)
On Thu, Jan 16, 2014 at 5:53 PM, Ken Moffat zarniwh...@ntlworld.com wrote:
On Thu, Jan 16, 2014 at 05:47:42PM -0600, Louis Rine wrote:
If this is the correct use of ldd...
:~$ ldd
On Jan 16, 2014, at 5:56 PM, Louis Rine wrote:
Ah, I was wondering if dash would make a difference. I will fix that
and try again. Thank you. :)
It does, and that is why the host system requirements states:
Bash-3.2 (/bin/sh should be a symbolic or hard link to bash)
But that may not be
On 01/16/14 18:07, William Darryl Jackson wrote:
On 01/16/2014 04:23 PM, Pierre Labastie wrote:
Le 16/01/2014 22:15, William Darryl Jackson a écrit :
You are correct - Pierre, I came to that same conclusion. So I very
carefully repeated the steps on page 36 to ensure those folders were
being
20 matches
Mail list logo
