On Thu, Apr 02, 2015 at 02:42:35PM -0400, rail shafigulin wrote:
> I've done a search for this error online as well as through the mailing
> lists but couldn't find an answer that would explain what is going on. One
> of the answers indicated that /bin/sh symlink is not pointing to the
> correct shell, but I verified mine, it points to the /bin/bash.
>
> I also want to ask if it is a good idea to attach a file to the email
> instead of pasting its contents. Is it usually done? Is it impolite to
> attach a file instead of posing its contents?
It is often better to paste only part of a file.
>
> I'm using book version 7.7 and I'm on chapter 5.5.
>
> Below is the output of make as well as contents of config.log. Any help in
> resolving the problem is appreciated.
>
> Last lines of make output:
>
> make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/gcc'
> Checking multilib configuration for libgcc...
> mkdir -p -- x86_64-lfs-linux-gnu/libgcc
> Configuring in x86_64-lfs-linux-gnu/libgcc
> configure: creating cache ./config.cache
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-lfs-linux-gnu
> checking for --enable-version-specific-runtime-libs... no
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for gawk... gawk
> checking for x86_64-lfs-linux-gnu-ar... x86_64-lfs-linux-gnu-ar
> checking for x86_64-lfs-linux-gnu-lipo... x86_64-lfs-linux-gnu-lipo
> checking for x86_64-lfs-linux-gnu-nm... /mnt/lfs/sources/gcc-build/./gcc/nm
> checking for x86_64-lfs-linux-gnu-ranlib... x86_64-lfs-linux-gnu-ranlib
> checking for x86_64-lfs-linux-gnu-strip... x86_64-lfs-linux-gnu-strip
> checking whether ln -s works... yes
> 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
> See `config.log' for more details.
> make[1]: *** [configure-target-libgcc] Error 1
> make[1]: Leaving directory `/mnt/lfs/sources/gcc-build'
> make: *** [all] Error 2
>
> Contents of config.log
The gcc dev's caught you out ;-) I think that what you have
attached is the top-level config.log. That runs before 'make', but
then make runs configure in various directories. In this case, it
seems to have failed in the libgcc directory.
The attached file shows error(s) which are normal. For example,
configure creates a tiny test program to see if libisl exists and
the long output shows an apparent error, but the screen output from
the initial configure would have been:
checking for objdir... .libs
checking for version 0.10 of ISL... no
checking for version 0.11 of ISL... no
checking for version 0.12 of ISL... no
*** This configuration is not supported in the following subdirectories:
target-libquadmath gnattools target-libada target-libgfortran target-libgo
target-libffi target-libbacktrace target-zlib target-libjava target-libobjc
target-libgomp target-libcilkrts target-libatomic target-libitm
target-libstdc++-v3 target-libsanitizer target-libvtv target-libssp
target-boehm-gc
(Any other directories should still work fine.)
So, what you now need to do is check the newest config.log (in
libgcc, I think), then search for 'cannot compute suffix of object
files:' e.g. in view or less, use the command
/cannot\ compute
and then look at the lines above, probably a screen or two earlier.
You should see the 'checking for suffix' message, a program
fragment, and a more-detailed error, probably from gcc. That error
message should identify the problem.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
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
