Matthew Burgess wrote:
/tools/lib/gcc/i686-pc-linux-gnu/4.0.2/../../../../i686-pc-linux-gnu/bin/ld:
Sorry for the noise if this is my own doing, but the above line caught
my eye.
I just finished building the latest svn and noticed much the same after
installing GCC in ch6. Running the san
Dan Nicholson wrote:
On 2/18/06, Jeremy Byron <[EMAIL PROTECTED]> wrote:
I get the 'Requesting program interpreter: /lib/ld-linux.so.2,' 'attempt
to open /lib/libc.so.6 succeeded,' and 'found ld-linux.so.2 at
/lib/ld-linux.so.2' lines but not the '
DJ Lucas wrote:
> The glibc version in current LFS causes a build failure when compiling
> xorg-6.9 and xorg-server-1.0.{1,2}. linux/types.h cannot be included
> after sys/kd.h. The glibc-2.3.6-linux_types-1.patch just committed to
>
> http://www.linuxfromscratch.org/patches/downloads/glibc/glibc
William Zhou wrote:
One of my friend started LFS several days ago and got an error when
adjusting the toolchain( 5.7 ). The problem was that the gcc specs path
was pointed to the host's one. It took me me a while to figure out that
he ignored the creation of user lfs and thus the ~/.bashrc is no
Emu wrote:
I think that you have mis-understood William's email. From his email, I
gather that he means that the commands set in 1 through 3 should be
stated as 'Compulsory', ie if not used then you have a good chance of
> I think as Linux becomes more mainstream, more people are going to
Matthew Burgess wrote:
Hi folks,
There's a minor issue with the Makefile in this version.
Essentially, if one uses the current '--prefix=""' then the following
ends up in the logs:
/bin/sh: line 0: [: =: unary operator expected
That's caused by:
Makefile:71: if [ $(prefix) = / ]
In this c
I tried building OOo2 again using the instructions in the book seeing as
people are saying they have successful builds, but I don't see how they
could without a lot of monkeying on their own.
The bsh download is "..b4-src.tar.bz2" but the copy and decompression
command references "..b4.tar.bz2
Jeremy Byron wrote:
still have the sed in the book for unxlngi6.mk. There are a few files
that have this problem and unxlngi6.mk is no longer one of them so the
Sorry, my bad.. unxlngi6.mk still has the problem but so does a few
other files. No point fixing one and not the others and
