Hi,
In Adjusting the Toolchain, I found that the new linker is being used with
the WRONG search paths.
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
... prints nothing (and has no errors) instead of printing...
SEARCH_DIR(/usr/lib)
SEARCH_DIR(/lib);
I found that my backup from the end
hello I got problem on Chapter 6.10. Adjusting the Toolchain - LFS 7.3
according to the LFS 7.3 book, the result of this command
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
---
should be
-
SEARCH_DIR(/tools/i686-pc
hello I got problem on Chapter 6.10. Adjusting the Toolchain - LFS 7.3
according to the LFS 7.3 book, the result of this command
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
---
should be
-
SEARCH_DIR(/tools/i686-pc
Em 11-05-2013 19:45, Mic Ky escreveu:
hello I got problem on Chapter 6.10. Adjusting the Toolchain - LFS 7.3
according to the LFS 7.3 book, the result of this command
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
---
should
On Sun, May 12, 2013 at 05:49:55AM +0700, Mic Ky wrote:
hello I got problem on Chapter 6.10. Adjusting the Toolchain - LFS 7.3
according to the LFS 7.3 book, the result of this command
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g
On May 11, 2013, at 6:07 PM, Ken Moffat wrote:
don't recall the details of why the svn book was changed, so it
is possible that the difference also exists on some 7.3 builds - but
if it does, I haven't seen it on my own builds. I'd assumed it was
soemthing to do with the move to either
I use LFS 7.3 not LFS svn, on x86 (32-bit), so I can continue it. Thank you for
your quick supports Mr. Ken and Mr. Fernando
Date: Sun, 12 May 2013 00:07:47 +0100
From: zarniwh...@ntlworld.com
To: lfs-support@linuxfromscratch.org
Subject: Re: [lfs-support] Adjusting the Toolchain - LFS 7.3
Mic Ky wrote:
hello I got problem on Chapter 6.10. Adjusting the Toolchain - LFS 7.3
according to the LFS 7.3 book, the result of this command
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
---
should
Hello
everyone, it's my first time to build the LFS. Now i have problem. I use
LFS liveCD ,and the version is LFS6.3, make it in the VMware , When i first
time adjusting the toolchain ,with this
SPECFILE=`dirname $(gcc -print-libgcc-file-name)`/specs
gcc -dumpspecs $SPECFILE
On Mon, 15 Aug 2011 01:21:56 +0800
赵佳晖 jiahui.tar...@gmail.com wrote:
Hello
everyone, it's my first time to build the LFS. Now i have problem. I use
LFS liveCD ,and the version is LFS6.3, make it in the VMware , When i first
time adjusting the toolchain ,with this
SPECFILE
am feeling a little optimistic, and am afraid of be wrong in next
steps.
Where I must doing the 5.8. Adjusting the Toolchain? Into
/mnt/lfs/sources?
---Fuf
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above
On Thu, 24 Mar 2011 20:24:47 +0300
fuflono fufl...@aol.com wrote:
Where I must doing the 5.8. Adjusting the Toolchain? Into
/mnt/lfs/sources?
It doesn't matter what directory you're in when you execute the
commands on that page
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
Hi,
I don't quite understand how re-writing the 'specs' file under the '/tools'
directory actually works -- by the way it does work!.
The specs file that is written with the fancy 'sed' script shows up as:
/tools/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/specs
I don't get how writing the spec
Hi,
from community reactions to subject mail I gather the problem (as usual)
is in front my display.
When starting my third round of LFS, I am going to use LFS 6.3 LiveCD
as host system for LFS book 6-5 (-6?).
Thank you.
attachment: f_kuhlmann.vcf--
Hello,
I am having a problem getting thru section 6.10, Re-Adjusting the Toolchain.
The 3rd block of instructions seems to hang on the cc dummy.c... command. I
can ctrl-C, and it stops, but would like to know what may have caused it to not
complete, or if it is ok to continue.
From
From the Book, the 3rd block of commands are:
--
echo 'main(){}' dummy.c
cc dummy.c -v -Wl,--verbose dummy.log
readelf -l a.out | grep ': /lib'
--
The only thing that I see that is different
On Mon, 2010-03-15 at 13:30 +0100, Franz L. Kuhlmann wrote:
Trying to build LFS using the LiveCD.iso
within SUN VirtualBox under Windows XP by the book
echo $(gcc -print-libgcc-file-name) returns
/mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-/gnu/4.1.2
how come
Date: Tue, 16 Mar 2010 02:37:52 -0400
Subject: Re: v6.6 section 6.10, Re-adjusting the Toolchain
From: sto...@gmail.com
To: lfs-support@linuxfromscratch.org
From the Book, the 3rd block of commands
Trying to build LFS using the LiveCD.iso
within SUN VirtualBox under Windows XP by the book
echo $(gcc -print-libgcc-file-name) returns
/mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-/gnu/4.1.2
how come ???
While I am starting from scratch again (assuming I missed a
2010/3/15 Franz L. Kuhlmann f_kuhlm...@freenet.de:
Trying to build LFS using the LiveCD.iso
within SUN VirtualBox under Windows XP by the book
echo $(gcc -print-libgcc-file-name) returns
/mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-/gnu/4.1.2
how come ???
While
On 03/15/2010 08:30 AM, Franz L. Kuhlmann wrote:
Trying to build LFS using the LiveCD.iso
within SUN VirtualBox under Windows XP by the book
echo $(gcc -print-libgcc-file-name) returns
/mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-/gnu/4.1.2
how come ???
While
2010/3/15 Franz L. Kuhlmann f_kuhlm...@freenet.de:
Trying to build LFS using the LiveCD.iso
within SUN VirtualBox under Windows XP by the book
echo $(gcc -print-libgcc-file-name) returns
/mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-/gnu/4.1.2
how come ???
While
Hi,
I am trying to install lfs 6.5 and I started with a good toolbox of which I
had made a backup.
I rebuilt the environment, and made with success all the steps of Chapter 6
until 6.10.
In this section the first steps are successful overcome but, when I give the
command
grep
Hi,
I tried creating a Linux from Scratch using the latest stable version of the
online LFS-book. My host system is an Ubuntu 9.10 Karmic Koala.
So I arrived at chapter 5.8, adjusting the toolchain and all went ok until
there. Some minor errors here and there, but nothing lethal. I completely
On Thu, Nov 5, 2009 at 2:28 PM, pieter blomme pieter.blo...@gmail.com wrote:
Checking the config.log didn't teach me a lot of new things. But the error
came before installing Binutils in second pass allready. Judging by the
error, I suppose it has to do with the C-compiler, so here's the
On 11/05/2009 03:28 PM, pieter blomme wrote:
Hi,
I tried creating a Linux from Scratch using the latest stable version of
the online LFS-book. My host system is an Ubuntu 9.10 Karmic Koala.
So I arrived at chapter 5.8, adjusting the toolchain and all went ok
until there. Some minor errors
This is wat version-check.sh outputs (after I installed gawk (again, I had
already done once manually from the soundcloud database, but something might
have gone wrong ofcourse)):
bash, version 4.0.33(1)-release
/bin/sh - /bin/dash
Binutils: (GNU Binutils for Ubuntu) 2.20
bison (GNU Bison) 2.4.1
pieter blomme wrote:
This is wat version-check.sh outputs (after I installed gawk (again, I had
already done once manually from the soundcloud database, but something might
have gone wrong ofcourse)):
bash, version 4.0.33(1)-release
/bin/sh - /bin/dash
First mistake. Change the symlink
On 11/05/2009 03:54 PM, Bruce Dubbs wrote:
pieter blomme wrote:
This is wat version-check.sh outputs (after I installed gawk (again, I had
already done once manually from the soundcloud database, but something might
have gone wrong ofcourse)):
bash, version 4.0.33(1)-release
/bin/sh -
On Thu, Nov 5, 2009 at 10:05 PM, Chris Staub ch...@beaker67.com wrote:
On 11/05/2009 03:54 PM, Bruce Dubbs wrote:
pieter blomme wrote:
This is wat version-check.sh outputs (after I installed gawk (again, I
had
already done once manually from the soundcloud database, but something
might
pieter blomme wrote:
Sorry for top-posting, and for being an ignorant fool. Version-check
currently looks like this:
bash, version 4.0.33(1)-release
/bin/sh - /bin/sh
This looks strange. It should be:
/bin/sh - bash
Alternatively it *could* be a hard link to bash, but that is not very
Chris Staub wrote:
On 11/05/2009 03:54 PM, Bruce Dubbs wrote:
pieter blomme wrote:
This is wat version-check.sh outputs (after I installed gawk (again, I had
already done once manually from the soundcloud database, but something might
have gone wrong ofcourse)):
bash, version
On Thu, Nov 5, 2009 at 10:29 PM, Bruce Dubbs bruce.du...@gmail.com wrote:
pieter blomme wrote:
Sorry for top-posting, and for being an ignorant fool. Version-check
currently looks like this:
bash, version 4.0.33(1)-release
/bin/sh - /bin/sh
This looks strange. It should be:
On 11/05/2009 04:24 PM, Bruce Dubbs wrote:
Chris Staub wrote:
On 11/05/2009 03:54 PM, Bruce Dubbs wrote:
First mistake. Change the symlink
No need for that...long as /bin/bash is specified for the LFS user.
I'm not sure about that Chris. That means that no script will ever
invoke sh.
Chris Staub wrote:
On 11/05/2009 04:24 PM, Bruce Dubbs wrote:
Chris Staub wrote:
On 11/05/2009 03:54 PM, Bruce Dubbs wrote:
First mistake. Change the symlink
No need for that...long as /bin/bash is specified for the LFS user.
I'm not sure about that Chris. That means that no script will
Hi all,
I'm fairly new to LFS and enjoying the build so far. I've made it to
6.10 Adjusting the toolchain in Version SVN-x86_64-20070807
When I ran the command below:
grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
it returned the following:
SEARCH_DIR(/tools/x86_64-
unknown-linux-gnu/lib
On Sun, May 3, 2009 at 9:53 AM, William Stevenson
w...@alumni.princeton.edu wrote:
I'm fairly new to LFS and enjoying the build so far. I've made it to
6.10 Adjusting the toolchain in Version SVN-x86_64-20070807
WTH?!?!?!
You are using a obslete x86_64 book, and a old one at it too.
If you
the build so far. I've made it to
6.10 Adjusting the toolchain in Version SVN-x86_64-20070807
WTH?!?!?!
You are using a obslete x86_64 book, and a old one at it too.
If you want a good x86_64 system from scratch, you might wanna try
Cross LFS, at cross-lfs.org.
(BTW, x86_64 support in LFS
On Sun, May 3, 2009 at 10:23 AM, William Stevenson
w...@alumni.princeton.edu wrote:
That said, I seemed to pass the Glibc test. There was only one extra
error and it was similar to the other nptl ones mentioned. If anyone
has any thoughts, I'd like to keep going if possible.
Uh... you should
Uh... you should switch to CLFS immediately to build this system,
becuase, the book you are using, does not have a bootloader, among
other things.
got it, thanks - will do
On Sun, May 3, 2009 at 11:38 AM, William Immendorf
will.immend...@gmail.com wrote:
On Sun, May 3, 2009 at 10:23 AM,
On Sunday 03 May 2009 10:56:22 William Immendorf wrote:
You are using a obslete x86_64 book, and a old one at it too.
This is wrong! It should be:
... an obslete ... an old ...
--
http://www.wowgreen.net/11324
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ:
On Sun, May 3, 2009 at 12:22 PM, genericmailli...@gmail.com wrote:
This is wrong! It should be:
... an obslete ... an old ...
What I meant by obslete, is that it isn't used anymore.
William
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ:
On Sun, May 03, 2009 at 12:40:38PM -0500, William Immendorf wrote:
On Sun, May 3, 2009 at 12:22 PM, genericmailli...@gmail.com wrote:
This is wrong! It should be:
... an obslete ... an old ...
What I meant by obslete, is that it isn't used anymore.
William
I think he was correcting
Hi there,
I see something wierd in the follwing line from the lfs-6.3 book (it
is in chapter 5.7):
Though I did not check it seems to be the same in the new lfs-6.4 book.
GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include
find ${GCC_INCLUDEDIR}/* -maxdepth 0 -xtype d -exec rm -rvf
Hi there,
I overlooked a mistake on my side.
(Somehow these things come to mind after writing a post...)
The LFS users .bashrc contained a wrong $PATH variable
I somehow ommited the /tools/bin...
Thanks anyway, and sorry...
Herman Gerritsen
On Sun, Nov 30, 2008 at 12:57 PM, Herman Gerritsen
--- On Tue, 7/15/08, Tarsier [EMAIL PROTECTED] wrote:
Philipp, thanks for the logs and let me CC this to the list
too, others also may be aware of this.
After the GCC-4.2.3 - Pass 2, its still not everything get
from /tools. Which is not pure as per our objective, but
since they are temp
--- On Mon, 7/14/08, Chris Staub [EMAIL PROTECTED] wrote:
From: Chris Staub [EMAIL PROTECTED]
Subject: Re: Compile error after final Re-adjusting the Toolchain
To: LFS Support List lfs-support@linuxfromscratch.org
Date: Monday, July 14, 2008, 1:51 PM
Tarsier wrote:
Oh, what I mean
On Sun, Jul 13, 2008 at 11:34:33PM -0700, Tarsier wrote:
Yep, no typo, I applied the GCC-4.2.3 - Pass 1 and GCC-4.2.3 - Pass 2
instructions to build and install the GCC 4.3.1 and the toolchain. Appreciate
if you could refer to my first email, I want to understand why the linking
went
Hi again,
my system is running a GCC-4.3.1, which is why
I responded in the first place.
If you have installed the patches for Glibc-2.7,
which should come in two *.diff files, then everything
should compile just fine with the development book's
instructions - well, at least it worked twice for
--- On Mon, 7/14/08, Ken Moffat [EMAIL PROTECTED] wrote:
From: Ken Moffat [EMAIL PROTECTED]
Subject: Re: Compile error after final Re-adjusting the Toolchain
To: lfs-support@linuxfromscratch.org
Date: Monday, July 14, 2008, 8:16 PM
On Sun, Jul 13, 2008 at 11:34:33PM -0700, Tarsier wrote
On Jul 14, 2008, at 9:21 AM, Tarsier wrote:
--- On Mon, 7/14/08, Ken Moffat [EMAIL PROTECTED] wrote:
I restarted building the Temporary System.
Appreciate very much if someone could send me the following
dummy.log (verbose output of the compilation) after the GCC-4.2.3 -
Pass 2 but
--- On Mon, 7/14/08, Philipp Christian Loewner [EMAIL PROTECTED] wrote:
From: Philipp Christian Loewner [EMAIL PROTECTED]
Subject: Re: Compile error after final Re-adjusting the Toolchain
To: [EMAIL PROTECTED]
Date: Monday, July 14, 2008, 11:16 PM
I restarted building the Temporary System
Hi
I'm getting a compile error after final Re-adjusting the Toolchain(6.10):
1. Rename ld-new to ld
2. gcc -dumpspecs | sed ...
echo 'main(){}' dummy.c
cc dummy.c -v -Wl,--verbose dummy.log
attempt to open /usr/lib/libc.so succeeded
:
attempt to open /usr/lib/crtn.o succeeded
/usr/lib/crtn.o
--- On Mon, 7/14/08, Ken Moffat [EMAIL PROTECTED] wrote:
From: Ken Moffat [EMAIL PROTECTED]
Subject: Re: Compile error after final Re-adjusting the Toolchain
To: LFS Support List lfs-support@linuxfromscratch.org
Date: Monday, July 14, 2008, 6:30 AM
On Sun, Jul 13, 2008 at 07:33:22PM +0200
Tarsier wrote:
The big problem here is the gcc version Tarsier is using -
it doesn't match what's in the book. I know people
are using the
4.3 series, but I don't know what changes they've
had to make.
Trying newer versions, after one is familiar with the
build process,
is not a bad
--- On Mon, 7/14/08, Chris Staub [EMAIL PROTECTED] wrote:
From: Chris Staub [EMAIL PROTECTED]
Subject: Re: Compile error after final Re-adjusting the Toolchain
To: [EMAIL PROTECTED], LFS Support List lfs-support@linuxfromscratch.org
Date: Monday, July 14, 2008, 12:39 PM
Tarsier wrote
Tarsier wrote:
Oh, what I mean is GCC-4.2.3 - Pass 1 and GCC-4.2.3 - Pass 2 instructions.
All necessary dependencies installed.
Tarsier
Then something is *seriously* wrong, assuming the directory name you
gave earlier wasn't a typo...
Tarsier wrote:
It is getting crtbegin.o,
Hello,
I have completed the chapter 5. But I am facing one problem in chapter 6.10
every time. After done all the steps before it, then query the following:
$ grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
I got nothing, then I tried with
$ grep 'SEARCH.*/lib' dummy.log |sed
On Tue, Feb 26, 2008 at 8:05 AM, mark jones [EMAIL PROTECTED] wrote:
Hello,
I have completed the chapter 5. But I am facing one problem in chapter
6.10 every time. After done all the steps before it, then query the following:
$ grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
Hello,
I have completed the chapter 5. But I am facing one problem in chapter 6.10
every time. After done all the steps before it, then query the following:
$ grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
I got nothing, then I tried with
$ grep 'SEARCH.*/lib' dummy.log |sed 's|; |\n|g'
where could i have missed to copy/install that file?
Hi,
have a look at chapter 5.12 Binutils. ld-new is installed there.
Something must have gone wrong here.
thorsten
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe:
hi everybody!
i got stuck here, but i got no idea why the linker is missing,
the earlier two commands in 6.10 of the stable lfs-book all
worked:
mv -v /tools/bin/{ld,ld-old}
mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
but it seems as i do not have a ld-new to be moved to ld..
where
Hi,
received the this error after re-adjusting the toolchain in chapter 6
and running sanity check.
root:~# mv -v /tools/bin/{ld,ld-old}
`/tools/bin/ld' - `/tools/bin/ld-old'
root:~# mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
`/tools/i686-pc-linux-gnu/bin/ld' - `/tools/i686-pc-linux-gnu
Hi,
I'm using lfs6.3 livecd an in section 5.7 Adjusting the toolchain, the 'gcc
-dumpspecs .' command doesn't appear to run properly. I've tried
finding the specs file to verify that its been edited correctly but I can't
find it.
From other posts I think the specs file should
I am using LFS v6.2. The host system is the LFS liveCD. I have not
intentionally deviated from the book at all. I think I have followed
the directions exactly.
Up to section 6.10, I have not had any unexpected errors or output that
is different from what is described in the book. When I
On Thu, 2007-08-23 at 11:11 -0500, Bryan J. McBride wrote:
Please disregard, I found the issue. Never fails, as soon as I ask for
help I find the stupid mistake.
Haha, if I had a nickel for every time that happened to me, I'd be
buying Bill Gates out with my vast fortune.
--
Peter B.
Hi,
In section 6.10. Re-adjusting the Toolchain,
mv -v /tools/bin/{ld,ld-old}
outputs an error saying that ld do not exist. It is
true that in /tools/bin instaed of ld ld-old and
ld-new are present. What is to be done ???
Similarly, for
mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old
On 4/27/07, Gopa Kumar [EMAIL PROTECTED] wrote:
Hi,
In section 6.10. Re-adjusting the Toolchain,
mv -v /tools/bin/{ld,ld-old}
outputs an error saying that ld do not exist. It is
true that in /tools/bin instaed of ld ld-old and
ld-new are present. What is to be done ???
Similarly
On 4/27/07, Tijnema ! [EMAIL PROTECTED] wrote:
I wonder how i486-linux-gnu suddenly appeared ?
What's the output of uname -m?
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Hi Dan,
It returned i686
Gopa Kumar
--- Dan Nicholson [EMAIL PROTECTED] wrote:
On 4/27/07, Tijnema ! [EMAIL PROTECTED] wrote:
I wonder how i486-linux-gnu suddenly
appeared ?
What's the output of uname -m?
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ:
Found the mistake,
didn't finish binutils installation :-/
Kai
Kai Ulrich schrieb:
Hallo,
I try to adjust the toolchain
but I dont have an ld-new file to rename !
Went something wrong ?
[EMAIL PROTECTED]:~$ mv -v /tools/bin/{ld,ld-old}
`/tools/bin/ld' - `/tools/bin/ld-old'
[EMAIL
If you are now saying that you knew it had failed, why did you
continue ? (Your words here can be interpreted in at least 2 ways,
so maybe you're saying you fell out of chroot because it failed and
you didn't notice).
no, on purpose :/
On a straight-through build (compared to doing a bit,
I kinda messed up after trying the first part in 6.10. Re-adjusting the
toolchain.
w00t:/LFS# ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld
create symbolic link `/tools/i486-linux/bin/ld' to `/tools/bin/ld'
ln: creating symbolic link `/tools/i486-linux/bin/ld' to `/tools/bin/ld
On 10/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I kinda messed up after trying the first part in 6.10. Re-adjusting the
toolchain.
w00t:/LFS# ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld
create symbolic link `/tools/i486-linux/bin/ld' to `/tools/bin/ld'
ln: creating symbolic
On 10/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I kinda messed up after trying the first part in 6.10. Re-adjusting the
toolchain.
w00t:/LFS# ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld
create symbolic link `/tools/i486-linux/bin/ld' to `/tools/bin/ld'
ln: creating
On Mon, Oct 16, 2006 at 06:55:17PM +0200, [EMAIL PROTECTED] wrote:
No such file or directory
Since I didnt have the i486-linux I changed the $(gcc -dumpmachine) to
i686-linux which I have, but in this process I accidently cp -v over the
ld in /tools/bin/ld and /tools/i686-linux/bin/ld.
On Mon, Oct 16, 2006 at 07:59:18PM +0200, [EMAIL PROTECTED] wrote:
You seem to be in /LFS when I would really expect you to be in /
(that is, /mnt/lfs) although you are root. This sort of suggests you
aren't in chroot, in which case you have probably trashed the files
in /tools.
My
the toolchain (Simon Needham)
2. Re: Chapter 5 part 7 adjusting the toolchain (Bauke Jan Douma)
3. Re: Chapter 5 part 7 adjusting the toolchain
(Mag. Leonhard Landrock)
--
Message: 1
Date: Tue, 3 Oct 2006 19:54:07 +0100
From
I am getting stuck while adjusting the toolchain. When I try to move
the files with:
mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
I get an error message:
mv: cannot stat '/tools/bin/ld' : No such file or directory
The message is of course self explanatory, but I have double checked
all
Simon Needham wrote:
I am getting stuck while adjusting the toolchain. When I try to move
the files with:
mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
I get an error message:
mv: cannot stat '/tools/bin/ld' : No such file or directory
I don't have an LFS installation, so this is just
Am Dienstag, 3. Oktober 2006 20:54 schrieb Simon Needham:
I am getting stuck while adjusting the toolchain. When I try to move
the files with:
mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
I get an error message:
mv: cannot stat '/tools/bin/ld' : No such file or directory
The message
Angel Tsankov wrote:
As what user should I re-adjust the toolchain in Ch. 6 of LFS 6.1.1?
First, backup the /tools linker, and replace it with...
The linker (ld) is part of the binutils package, so the first block of
commands (3 mv and 1 ln) should be done as your binutils
package user.
Next,
As what user should I re-adjust the toolchain in Ch. 6 of LFS 6.1.1?
First, backup the /tools linker, and replace it with...
The linker (ld) is part of the binutils package, so the first block of
commands (3 mv and 1 ln) should be done as your binutils
package user.
Next, amend the GCC specs
Angel Tsankov wrote:
As what user should I re-adjust the toolchain in Ch. 6 of LFS 6.1.1?
First, backup the /tools linker, and replace it with...
The linker (ld) is part of the binutils package, so the first block of
commands (3 mv and 1 ln) should be done as your binutils
package user.
As what user should I re-adjust the toolchain in Ch. 6 of LFS 6.1.1?
First, backup the /tools linker, and replace it with...
The linker (ld) is part of the binutils package, so the first block of
commands (3 mv and 1 ln) should be done as your binutils
package user.
For LFS 6.1.1 the
Angel Tsankov wrote:
As what user should I re-adjust the toolchain in Ch. 6 of LFS 6.1.1?
If you need to ask this, you shouldn't be using package users. Besides,
the whole toolchain readjustment only affects stuff in /tools, so it
doesn't make any difference what user you use.
--
Brandon Peirce wrote:
Angel Tsankov wrote:
For LFS 6.1.1 the instructions says Install the adjusted linker by
running the following command from within the binutils-build directory:
The make -C ld ... install command is different to the LFS 6.2
commands but is still manipulating (in 6.1.1
Chris Staub wrote:
The adjusted linker is installed into /tools, so you need to use root.
Why root?
Of course you can always achieve this with root, but that's kind of missing
the point of package users technique, (and also violating principle of least
privelege).
I concede that the
Brandon Peirce wrote:
Why root?
Of course you can always achieve this with root, but that's kind of
missing the point of package users technique, (and also violating
principle of least privelege).
I concede that the motivation for why you would use the package users
technique in the first
Chris Staub wrote:
You're not *supposed* to be using package users in chapter 5. It's only
in chapter 6. The only package installed using package users so far
should be glibc.
From the hint:
Build Chapter 5 exactly as explained by the LFS book. There is only one
little change you have to
You're not *supposed* to be using package users in chapter 5. It's only
in chapter 6. The only package installed using package users so far
should be glibc.
Why glibc only?! What about Linux Libc headers and Man pages - the hint
recommends to install them using PU?
--
Angel Tsankov wrote:
You're not *supposed* to be using package users in chapter 5. It's
only in chapter 6. The only package installed using package users so
far should be glibc.
Why glibc only?! What about Linux Libc headers and Man pages - the hint
recommends to install them using PU?
Chris Staub wrote:
Chris Staub wrote:
You're not *supposed* to be using package users in chapter 5. It's only in
chapter 6. The only package installed using package users so far should be
glibc.
From the hint:
Build Chapter 5 exactly as explained by the LFS book. There is only one
little
Hallo!
I'm trying to build a LFS system from the LFS LiveCD and I've come to section
6.12. Re-adjusting the Toolchain. Then I noticed that
the
make -C ld INSTALL=/tools/bin/install install
command does not get executed properly, as the binutils-build/Makefile
contains paths that do not exist
On 4/27/06, Angel Tsankov [EMAIL PROTECTED] wrote:
make -C ld INSTALL=/tools/bin/install install
command does not get executed properly, as the binutils-build/Makefile
contains paths that do not exist in the chroot environment.
All these are absolute paths beginning with /mnt/lfs. Since this
Could a problem in previous steps result in these makefiles using
absolute paths?
You didn't configure binutils in the chapter 5 with
--prefix=/mnt/lfs/tools, did you?
Here's how I configured binutils in chapter 5, pass 2:
Hallo Everybody!
May I present you the following result:
$ SPECFILE=`gcc --print-file specs`
sed 's@ /lib/ld-linux.so.2@ /tools/lib/[EMAIL PROTECTED]' \
$SPECFILE tempspecfile
mv -f tempspecfile $SPECFILE
unset SPECFILE
mv: Verschieben zwischen Geräten fehlgeschlagen: ,,tempspecfile
Hi,
I'm currently in Chapter 6, section 6.12, of the LFS book version 6.1. It's
the section where we re-adjust the toolchain. The book says to adjust the
gcc specs file to remove the reference to /tools/lib/ld-linux.so.2, and
replace it with /{,usr/}lib/ld-linux.so.2. Now, I understand this to
On 11/1/05, Paul Lewis [EMAIL PROTECTED] wrote:
The book says to adjust the
gcc specs file to remove the reference to /tools/lib/ld-linux.so.2, and
replace it with /{,usr/}lib/ld-linux.so.2. Now, I understand this to mean
that we are specifying two paths - /lib/ld-linux.so.2, and
Perhaps you haven't set your PATH correctly - you should be using
programs from /tools/bin in preference to the host's /bin and /usr/bin,
so gcc should already be in /tools.
yes , you are right . because I'm using live cd so , i should set my
PATH every time ... ; there is some good script
1 - 100 of 117 matches
Mail list logo
