The problem is that he was trying to build glibc in
/mnt/lfs/tools/glibc-build and not what we would expect
/mnt/lfs/glibc-build, so yes, there would be an error. Noone should be
using /mnt/lfs/tools for their builds.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linu
On 2/10/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> My question is: Why does the package try to install something *from* a
> location that is outside its own files. Its own files reside on, in
> this case,
>
> {/mnt/lfs}/tools/glibc-build/ and
> {/mnt/lfs}/tools/glibc-$glibc-version
>
> but it
Chris Staub wrote:
> Yes, but in general it doesn't matter *where* you build stuff, it will
> still work fine.
>
> However, this does seem to be an exception in the case of Glibc
> 2.5...I've been testing it myself, and I get a build failure due to the
> same problem, as it keeps complaining t
On 2/10/07, Chris Staub <[EMAIL PROTECTED]> wrote:
>
> Apparently, if there is an "include" dir one level up from the Glibc
> build dir, it automatically copies headers from there into the default
> include dir. Obviously, this means that if you build Glibc in /tools, it
> tries to copy from "glibc
Matthew Burgess wrote:
> On Saturday 10 February 2007 06:23, Dan Winkler wrote:
>
>> i unpack the package in /mnt/lfs/tools then follow the instructions.
>
> Why? It's recommended that all packages should live in /sources and be
> unpacked there. See 3.1: Introduction
>
> "Downloaded packages
On Saturday 10 February 2007 06:23, Dan Winkler wrote:
> i unpack the package in /mnt/lfs/tools then follow the instructions.
Why? It's recommended that all packages should live in /sources and be
unpacked there. See 3.1: Introduction
"Downloaded packages and patches will need to be stored so
This issue has been resolved but points to potential other issues
when glibc-2.35 is unpacked and built within the /tools directory
somthing seems to get mixed up in the path names
when unpacking and building within the /sources directory the build
proceeds normally
--
http://linuxfromscratch.or
> How are you building this? None of those paths look right at all. I
> have no idea why it's trying to install to linux/limits.h.
im using the instructions located in section 5.6.1 of the LFS book (dev)
mkdir -v ../glibc-build
cd ../glibc-build
../glibc-2.5/configure --prefix=/tools \
--disa
On 2/9/07, Dan Winkler <[EMAIL PROTECTED]> wrote:
>
> i hit a road block at glibc-2.5:
>
> /usr/bin/install -c -m 644
> /mnt/lfs/tools/glibc-build/../include/linux/limits.h
> /tools/include/linux/limits.h
> /usr/bin/install:
> `/mnt/lfs/tools/glibc-build/../include/linux/limits.h' and
> `/tools/inc
running off the most recent snapshot
SVN-20070207
i hit a road block at glibc-2.5:
/usr/bin/install -c -m 644
/mnt/lfs/tools/glibc-build/../include/linux/limits.h
/tools/include/linux/limits.h
/usr/bin/install:
`/mnt/lfs/tools/glibc-build/../include/linux/limits.h' and
`/tools/include/linux/lim
10 matches
Mail list logo
