Le jeudi 03 mai à 15:16, Scott Robertson a écrit :
> Ahh, ok, yes thank you, that is more what I am looking for.   So you can have 
> the Binutils-xx AND Binutils-build in the same /mnt/lfs/sources directory.  I 
> know everyone disagrees with me, but I still think that isn't clear given 
> that quote on page 35 recommending that Binutils be built outside the sources 
> directory.  But maybe it is just a wording issue.  I guess in essence, there 
> are two "sources" directories:  
> 
> /mnt/lfs/sources AND /mnt/lfs/sources/Binutils-xx
> 
> 
> So the GCC directory is similar in that it goes in /mnt/lfs/sources/GCC-4.x  
> is that right?   I don't think the book explicitly says it, but I guess you 
> are supposed to uncompress the GCC-4.x tar file into the GCC-4.x directory 
> first, right?  And then the GMP, MPFR and MPC packages go into the GCC-4.x 
> directory? So the folder structure  would be:
> 
> /mnt/lfs/sources/GCC-4.x/

Yes and this will repeat for every package in chapter 5 and then in chapter
6.


> 
> /mnt/lfs/sources/GCC-4.x/GMP
> /mnt/lfs/sources/GCC-4.x/MPFR
> /mnt/lfs/sources/GCC-4.x/MPC

Thats' right but you should have understood this by reading the commands
:-)

> 
> and then you put the gcc-4.x-cross_compile-1.patch into the
> /mnt/lfs/sources/GCC-4.x directory right?

No. Use the patch if it is required by the book (I think it's not the case
now but I'm not sure because I don't know what version of the book your are
following).

Nevertheles, when a patch is needed, you have not to copy it in the source
directory of the package.

> 
> Then you create the GCC-Build directory.  So that would be   
> /mnt/lfs/sources/GCC-Build
> so you would have:
> /mnt/lfs/sources/GCC-4.x      and
> /mnt/lfs/sources/GCC-Build
> 
> is that right?

Yes except that case is sensitive and that it is gcc and not GCC, gcc-build
and not GCC-Build.

-- 
Ph. Delavalade
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to