[SOLVED] ./configure fails during Binutils Pass 2

supern0va · 11-08-2010, 04:20 PM

(Latest LFS/6.7)
Host: LFS

Original Command:

Code:

CC="$TARGETOS-gcc -B$TARGETDIR/lib/" \
  AR=$TARGETOS-ar RANLIB=$TARGETOS-ranlib \
  ../binutils-$BINUTILS_VERSION/configure --prefix=$TARGETDIR \
        --disable-nls --with-lib-path=$TARGETDIR/lib

Error msg:

Quote:

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for gcc... x86_64-installOS-linux-gnu-gcc -B/root/installOS/os/lib/
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: in `/root/installOS/source/binutils-2.20.1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

I imagined that this was caused by some mistake in my tool chain adjustment:

Code:

SPECS=`dirname $($TARGETOS-gcc -print-libgcc-file-name)`/specs
  $TARGETOS-gcc -dumpspecs | sed \
    -e 's@/lib\(64\)\?/ld@$TARGETDIR&@g' \
    -e "/^\*cpp:$/{n;s,$, -isystem $TARGETDIR/include,}" > $SPECS
  echo "New specs file is: $SPECS"
  unset SPECS

However gcc DOES seem to work:

Code:

echo 'main(){}' > dummy.c
$TARGETOS-gcc -B$TARGETDIR/lib dummy.c
readelf -l a.out | grep ': $TARGETDIR'

Quote:

[Requesting program interpreter: $TARGETDIR/lib64/ld-linux-x86-64.so.2]

Any ideas?

crts · 11-08-2010, 07:35 PM

This is a very good example why it is not recommended to deviate from the book. Especially if you have no idea what you are doing.
This

Code:

-e 's@/lib\(64\)\?/ld@$TARGETDIR&@g' \

is not what you were supposed to issue in chapter 5.8. As you can see, the statement is enclosed in single quotes, i.e. it got not expanded by bash as you thought it would. Also

Code:

[Requesting program interpreter: $TARGETDIR/lib64/ld-linux-x86-64.so.2]

This should had at least been whatever is stored in $TARGETDIR. I don't know what is stored in $TARGETDIR but I assume it will not work as you expect it to - even if you correct your previous statement and $TARGETDIR would get expanded in the sed statement. It would be probably best if you start over again and follow the book by the letter.

Code:

checking for gcc... x86_64-installOS-linux-gnu-gcc -B/root/installOS/os/lib/

Are you installing your toolchain on your host system? Again, do NOT deviate from the book.

supern0va · 11-08-2010, 11:07 PM

OK some further explanation:

$TARGETDIR simply points to some directory on my host system. While I know that this isn't necessarily the best way to build my system it should be possible after all or am I mistaken there? By now I don't even want to build the whole system but only the temporary system for my future projects.

What I want to do is to learn more about Linux and also about scripting. I am prepared to run into problems, but if I do I want to know what I did wrong and how I can then correct my code. After all I already built a complete and working LFS sticking completely to the book, which is why I now dared making changes.

Now as you already pointed out this

Code:

-e 's@/lib\(64\)\?/ld@$TARGETDIR&@g' \

does not expand. Would you be so kind to explain the syntax which is necessary to actually make it expand? I would at least give it a try

.

Thanks for your time,

Mario

crts · 11-09-2010, 03:27 AM

Well, if you insist:
Do not it expand but type in the whatever content $TARGETDIR holds. E.g., if $TARGETDIR point to /root/installOS then

Code:

-e 's@/lib\(64\)\?/ld@/root/installOS/&@g' \

Do the same for the statement in the next sed line.

druuna · 11-09-2010, 06:48 AM

Hi,

About the (not) expanding part: If you use single quotes, nothing is expanded by the shell, if you use double quotes it is expanded.

So you either use crts idea (replace all $TARGETDIR's with /root/installOS) or you use double quotes and parenthesis (the latter to protect the content of the variable):

-e "s@/lib$64$\?/ld@${TARGETDIR}/&@g" \

Hope this clears things up a bit.

supern0va · 11-09-2010, 10:46 AM

Thank you it worked (even with expanding syntax). Should spend some hours with the grep and sed manuals now

.