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 file
On 3/16/10, David Gay wrote:
> cc: unrecognized option '-mtune=generic'
>
> Any idea which step may have introduced this problem?
grep -i -r "mtune" /BOOK/LFS-6.6-XML/*
only reports:
chapter05/glibc
chapter06/introduction
chapter06/glibc
--
http://linuxfromscratch.org/mailman/listinfo/lfs-supp
> 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 3
> >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 diff
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.
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|;
> 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.lo
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: Se
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 cou
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. Steig
: Issue at 6.10. Re-adjusting the toolchain
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
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 attempte
> 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
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 /tool
> 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
> 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
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: c
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.
>
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/b
20 matches
Mail list logo
