Re: [lfs-support] questions about chapter 5.5.1
On 28 March 2014 03:07, François Bissey
wrote:
> Hi,
>
> I suspect it may be a case of "to much knowledge is dangerous".
>
> Having some experience in building cross compilers and bootstrapping
> systems in the past I found some elements in that chapter troubling
> enough to stop and post here first:
>
> 1) There are instructions to download and unpack gmp,mpfr and mpc.
> But nowhere to configure && compile them.
> The hints that I have from the remaining of your instructions is that
> you don't want to install them.
>
> 2) we are asked to gcc so that it looks for ld* in /tools/lib{,32,64} rather
> than in plain /lib{,32,64}. Yet, at this stage we haven't built glibc
> which would provide it, so there is nothing in /tools/lib* at this stage.
> It looks to me like this will be useful in pass 2 but could lead to
> breakage in pass 1.
>
> 3) configuration options for gmp and mpc? Only mpfr paths are given,
> and they would need to be compiled first - statically I am guessing.
>
> Francois
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
1) I read it as the gcc pass 1 build just requires the in-tree sources
of gmp, mpfr and mpc.
--
rob
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] questions about chapter 5.5.1
François Bissey wrote:
> Hi,
>
> I suspect it may be a case of "to much knowledge is dangerous".
>
> Having some experience
"some" experience is indeed a dangerous thing.
in building cross compilers and bootstrapping
> systems in the past I found some elements in that chapter troubling
> enough to stop and post here first:
>
> 1) There are instructions to download and unpack gmp,mpfr and mpc.
> But nowhere to configure && compile them.
> The hints that I have from the remaining of your instructions is that
> you don't want to install them.
They are built as a part of the gcc instructions in Chapter 5. They are
built as separate libraries in Chapter 6.
"GCC now requires the GMP, MPFR and MPC packages. As these packages may
not be included in your host distribution, they will be built with GCC.
Unpack each package into the GCC source directory and rename the
resulting directories so the GCC build procedures will automatically use
them:"
> 2) we are asked to gcc so that it looks for ld* in /tools/lib{,32,64} rather
> than in plain /lib{,32,64}. Yet, at this stage we haven't built glibc
> which would provide it, so there is nothing in /tools/lib* at this stage.
> It looks to me like this will be useful in pass 2 but could lead to
> breakage in pass 1.
Try it and see. /tools/lib* is the first place it looks, but if not
found, it looks at the host's files. That's why we build gcc twice.
> 3) configuration options for gmp and mpc? Only mpfr paths are given,
> and they would need to be compiled first - statically I am guessing.
Just follow the instructions as they are written.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
[lfs-support] questions about chapter 5.5.1
Hi,
I suspect it may be a case of "to much knowledge is dangerous".
Having some experience in building cross compilers and bootstrapping
systems in the past I found some elements in that chapter troubling
enough to stop and post here first:
1) There are instructions to download and unpack gmp,mpfr and mpc.
But nowhere to configure && compile them.
The hints that I have from the remaining of your instructions is that
you don't want to install them.
2) we are asked to gcc so that it looks for ld* in /tools/lib{,32,64} rather
than in plain /lib{,32,64}. Yet, at this stage we haven't built glibc
which would provide it, so there is nothing in /tools/lib* at this stage.
It looks to me like this will be useful in pass 2 but could lead to
breakage in pass 1.
3) configuration options for gmp and mpc? Only mpfr paths are given,
and they would need to be compiled first - statically I am guessing.
Francois
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] 64 bit host machine build question
On Fri, 21 Mar 2014 17:04:42 +
Ken Moffat wrote:
> On Thu, Mar 20, 2014 at 09:15:35PM -0400, Jonathan Arnold wrote:
> > I'm doing the 5.7 glibc-2.19 step and everything seems to be going
> > along swimmingly. But the test program mentioned in the Caution
> > isn't exactly what is desired:
> >
> > lfs:/mnt/lfs/sources/glibc-build$ echo 'main(){}' > dummy.c
> > lfs:/mnt/lfs/sources/glibc-build$ $LFS_TGT-gcc dummy.c
> > lfs:/mnt/lfs/sources/glibc-build$ readelf -l a.out | grep ': /tools'
> > [Requesting program
> > interpreter: /tools/lib64/ld-linux-x86-64.so.2]
> >
> > While the Caution says to expect the /tools/lib64 part, it doesn't
> > say anything about the '-x86-64' I have appended to the name. Is
> > this going to be okay or is something amiss here?
> >
>
> Your result looks fine. When you get to section 6.10 you will see
> that we add the phrase "allowing for platform-specific differences in
> dynamic linker name". If you look at your host system, the linker
> will be ld-linux-x86-64.so for 64-bit x86_64.
>
> ĸen
Thanks for the input. I figured as much but I didn't want any screwups
so early in the game!
--
Jonathan ArnoldWebstream: http://hieronymus.soup.io
If you want to go fast, go alone. If you want to go far, you
need a team ~ John Wooden
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
