Hello,

I have rebuilt ch5 twice now.  The 2nd time around I have scripted all
build commands so that there's a firm reliable base to work with.  Each
package has its own build file.  The build instructions can be compared
with the book and adjusted if necessary.  Less guess work.  And each
command is followed by an error check and if there's an error, the
script will bail out.  It checks the error code with this:

function check4errors()
{
 if [ $? != 0 ]
  then 
  [ "$1" != "" ] && logError $1 exit 1
  fi
}

It simply logs by writing to a file.

So I rebuilt ch5.  Then at the beginning of ch6, the linux headers, the
very first command, 'make mrproper' yields this:

arch/x86/Makefile:184: *** Compiler lacks asm-goto support..  Stop.

I do not know what this support entails, yet, but it's possible to
comment it out for test purposes in:

../linux-4.18.5/arch/x86/Makefile

Doing this enables 'make mrproper' to go a tiny bit further until:

make: gcc: Command not found

Now, first culprit could be the PATH, so let's take it out of the
equation by cd into the /tools/bin/ directory and executing gcc
directly:

bash: ./gcc: No such file or directory

OK.  Let's execute xz from the same directory:

./xz: Compressed data cannot be written to a terminal

Works all right.

ld ?

bash: ./ld: No such file or directory

readelf ?

bash: ./ld: No such file or directory

date ?

Thu Jan 17 15:35:13 UTC 2019

So it seems there's a problem with gcc.  It looks like this problem was
hit before and I'm still reading/searching about this.  I thought of
dropping a line directly here in case there were any findings regarding
this.

Cheers.
-- 
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

Reply via email to