On Sunday 19 August 2007 15:11, J.R. Hass wrote:
> Is there a way to store that command in a variable and then run it
> from the command line via a variable?
You might try playing around with an alias rather than export, but it's
probably better to separate the CC= from the command.
...
export CC
On Sun, 19 Aug 2007 11:59:44 -0700,
lists <[EMAIL PROTECTED]> wrote :
> > I have a (potentially stupid) question. Can I simply use a X86_64
> > and follow the LFS instructions to build a system (taking care to
> > configure the kernel for 64 bits operation) ? I mean, do I have to
> > be concern
J.R. Hass wrote:
> After having binutils fail right off the bat, I checked the errata and
> it appears I need to add
>
> CC="gcc -B/usr/bin/" to the configure line when building binutils.
>
> The problem is, if I do something like this
>
> export command='CC="gcc -B/usr/bin/" ../binutils/configure
On Sunday 19 August 2007 7:58:50 pm Peter Santimauro wrote:
> I am working on building the LFS system, I am currently installing
> diffutils in 5.17. I ran the ./configure ... , make, and make
> install. Make install finishes with an error, saying that it cannot
> create regular file /usr/local
good call thanks alot
On 8/19/07, Trent Shea <[EMAIL PROTECTED]> wrote:
> On Sunday 19 August 2007 17:58, Peter Santimauro wrote:
> > Make install finishes with an error, saying that it cannot
> > create regular file /usr/local/bin/cmp, .../bin/diff, .../bin/diff3.
> > ../bin/sdiff, Permission den
On Sunday 19 August 2007 17:58, Peter Santimauro wrote:
> Make install finishes with an error, saying that it cannot
> create regular file /usr/local/bin/cmp, .../bin/diff, .../bin/diff3.
> ../bin/sdiff, Permission denied.
Chapter 5 should be trying to install to $LFS/tools. Check if your
config
I am working on building the LFS system, I am currently installing
diffutils in 5.17. I ran the ./configure ... , make, and make
install. Make install finishes with an error, saying that it cannot
create regular file /usr/local/bin/cmp, .../bin/diff, .../bin/diff3.
../bin/sdiff, Permission deni
Wala!
I created the build directory down from $LFS, (/mnt/lfs/glibc-build)
where my other build dirs live,
copied the tar and patch to it,
untar'd the tarball,
moved down to the glibc-2.5 dir
and ran the patch exactly as written.
Everything that needed it got patched.
In chapter 5.6, the firs
As an exercise in both Linux and Bash, I've been trying to write some
scripts on my own to automate the building of an LFS system.
After having binutils fail right off the bat, I checked the errata and
it appears I need to add
CC="gcc -B/usr/bin/" to the configure line when building binutils.
Th
On Sunday 19 August 2007 15:32, Łukasz Choiński wrote:
> /mnt/lfs/sources/glibc-2.5.1/nscd/nscd.c:414: undefined reference to
> `__stack_chk_guard'
You probably are trying to build glibc-2.5.1 with the old gcc-3.3.1.
Make sure you have built the newer gcc and have set PATH correctly. IOW
make sure
lanas wrote:
> Folks,
>
> I have a (potentially stupid) question. Can I simply use a X86_64 and
> follow the LFS instructions to build a system (taking care to configure
> the kernel for 64 bits operation) ? I mean, do I have to be concerned
> with cross LFS if the system I'm building using the
On Sunday 19 August 2007 12:21, Burt Alcantara wrote:
> I created the structure as above. First time created
> /mnt/lfs/packagename. Copied sources/glibc-2.5.tar.bz2. Ran the
> patch.
Ah, see the chapter 5 introduction.
Before issuing the build instructions for a package... (it's marked
importa
Trent Shea wrote:
> Directory structure:
> Sources: /mnt/lfs/sources
> Patches: /mnt/lfs/sources/patches
> Unpacked Sources: /home/lfs/packagename
> Build Directory: /home/lfs/packagename-build
>
> Command:
> cd /home/lfs/packagename
> patch -Np1 -i /mnt/lfs/sources/patches/"patchname"
>
I crea
On Sunday 19 August 2007 09:49, Burt Alcantara wrote:
> When you run this patch, where dir are you running it from and
> what is your directory structure in general?
Directory structure:
Sources: /mnt/lfs/sources
Patches: /mnt/lfs/sources/patches
Unpacked Sources: /home/lfs/packagename
Build Direc
I've put all of the source tarballs and patches in /mnt/lfs/sources. I
make a subdirectory build directory in lfs. From there, I copy the
tarball into the build directory and run the make(s). So far, this has
worked up, populating tools as expected (I hope).
When you say "be in the root of t
Folks,
I have a (potentially stupid) question. Can I simply use a X86_64 and
follow the LFS instructions to build a system (taking care to configure
the kernel for 64 bits operation) ? I mean, do I have to be concerned
with cross LFS if the system I'm building using the X86_64 will run on
the s
Hi,
when trying to compile glibc i get this error:
gcc -B/tools/bin/ -nostdlib -nostartfiles -o
/mnt/lfs/sources/glibc-build/nscd/nscd
-Wl,-dynamic-linker=/tools/lib/ld-linux.so.2 -Wl,-z,combreloc
-Wl,-z,relro /mnt/lfs/sources/glibc-build/csu/crt1.o
/mnt/lfs/sources/glibc-build/csu/crti.o `gcc
17 matches
Mail list logo
