On Sun, Oct 25, 2015 at 9:55 PM, Ken Moffat <[email protected]> wrote:
> What you have to do is work out in which directory configure was last > run, i.e. identify the *newest* config.log file and then search for > 'cannot compute suffix of object files'. Use less or vim to search, > e.g. > > /cannot\ compute\ suffix > > will probably take you to the right part of the file, then look back > at the lines before that - you should see that a code fragment was > created, probably with a message related to testing the suffix of > object files, and then you should see what happened when configure > tried to run that fragment. i.e. A "real" descriptive error. > That was easy..... it was on the line before: checking for x86_64-lfs-linux-gnu-gcc... /mnt/lfs/sources/gcc-build/./gcc/xgcc -B/mnt/lfs/sources/gcc-build/./gcc/ -B/tools/x86_64-lfs-linux-gnu/bin/ -B/tools/x86_64-lfs-linux-gnu/lib/ -isystem /tools/x86_64-lfs-linux-gnu/include -isystem /tools/x86_64-lfs-linux-gnu/sys-include checking for suffix of object files... configure: error: in `/mnt/lfs/sources/gcc-build/x86_64-lfs-linux-gnu/libgcc': configure: error: cannot compute suffix of object files: cannot compile **** I just searched the error and found a suggestion to start over from scratch (here <http://www.linuxquestions.org/questions/linux-from-scratch-13/error-with-gcc-first-pass-cannot-compute-suffix-of-object-files-cannot-compile-4175478166/page2.html>). There was no follow up so I am assuming that this worked. I would like to fix things to learn how to do it but if this would make it so that I would have to fix EVERYTHING I would rather start over. What do you think? -- :-)~MIKE~(-:
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
