Bonjour Chris, Many Thanks for the information, start to make sens now (ld-new become ld beyond "Installing Basic System Software" ,chapter 6.9)
Problem, as specified in my original post, I was trying test
cc dummy
within chapter 5.10 (well inside "Constructing a Temporary System ")
;---------
echo 'main(){}' > dummy.c
cc dummy.c
readelf -l a.out | grep ': /tools'
;----
Getting:
cc dummy.c
/usr/bin/ld: unrecognized option '-plugin'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
Do we agree, at that stage, we are compiling with /tools/bin/cc
(so, the reference to ld must be hardcoded within cc to an ld
(/tools/bin/ld-new ????),
but instead (my) cc was using /usr/bin/ld)
I need to do all steps again this time more carefully, to check what
I have done wrong...
Thanks for your help.
Quoting Chris Staub <[email protected]>:
On 08/18/14 10:16, Jean-Marc Pigeon wrote:Bonjour akhiezer Agreed. ld-new really trouble me somewhat, obviously I am misunderstanding something. I was expecting an answer from the list like "ld-new is found in the search path because chapter X.Y.Z". On my side I am working "cutting and pasting" HTML screen, so I think I do everything according manual, telling me "redo cut and past" is not helping to my understanding. Right? About zlib, I should had say about previous ld-new post, I "cut corner" thinking it was (obviously) a new Makefile with "-lz" within 'file' tar file. "my solution" was just to go a little bit further to the next step, not implying it was THE solution. I need to redo the whole installation process in a more systematic way... But if in the mid-time someone can give us some light about ld-new problem, that will be welcome (telling "redo the process" is 'windows like magic' it is not improving understanding, my 2 Cents)Not really much to tell about it other than what the LFS book itself says - ld-new never is found with any search path; it's never used by the toolchain at all, at least not when it has that name. The short version is: you can see the grand total of where ld-new is used in the LFS book simply by looking at Binutils Pass 2, and Adjusting the Toolchain in Chapter 6 - that's really it. A longer version: If you look at Binutils Pass 2, you'll see that the last thing there is to rebuild the "ld" directory so it creates an ld binary with a new LIB_PATH which looks in /lib and /usr/lib instead of /tools; Binutils just initially creates it with the name "ld-new" by default. This "ld-new" program is copied to /tools/bin, and sits there until you get to Chapter 6. After installing Glibc in Chapter 6, you adjust the toolchain, which includes renaming the current "/tools/bin/ld" (the one that searches in /tools for libraries) to "ld-old" to get it out of the way (but also have it still around in the event you might want to undo the adjustment and rename it back) and "ld-new" to "ld", so the default "ld" now looks in /lib and /usr/lib. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
-- A bientôt =========================================================== Jean-Marc Pigeon E-Mail: [email protected] SAFE Inc. Phone: (514) 493-4280 Clement, 'a kiss solution' to get rid of SPAM (at last) Clement' Home base <"http://www.clement.safe.ca";> ===========================================================
smime.p7s
Description: S/MIME Cryptographic Signature
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
