LinuxQuestions.org - LFS Libstdc++ make error [ Help! ]

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - LFS Libstdc++ make error [ Help! ] (https://www.linuxquestions.org/questions/linux-from-scratch-13/lfs-libstdc-make-error-%5B-help-%5D-4175541459/)

LFS Libstdc++ make error [ Help! ]

So things were running smoothly, I passed the requirements.
I have all the stuff I need installed then when attempting to run the make command on libstc++, It returns:

Code:

make[3]: *** [compatibility-thread-c++0x.lo] Error 1

make[3]: *** [compatibility-atomic-c++0x.lo] Error 1

make[3]: Leaving directory `/mnt/lfs/sources/gcc-build/src'

make[2]: *** [all-recursive] Error 1

make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/mnt/lfs/sources/gcc-build'

make: *** [all] Error 2

Can someone help?
I've already reinstalled Gcc

You should input few more lines before error text.

what host are you using is it a VM what is the result of version.sh et etc etc, gets boring after a while trying to get people to post basic information.

Quote:

Originally Posted by Keith Hedger (Post 5356960)

what host are you using is it a VM what is the result of version.sh et etc etc, gets boring after a while trying to get people to post basic information.

I'm using Debian 7 Weezy ( Not VM )
here's a few lines before
and This is a result of make

Code:

l>]

/mnt/lfs/sources/gcc-build/include/chrono:252:12: note:  candidate expects 0 arguments, 1 provided

make[3]: *** [compatibility-atomic-c++0x.lo] Error 1

make[3]: *** [compatibility-thread-c++0x.lo] Error 1

make[3]: Leaving directory `/mnt/lfs/sources/gcc-build/src'

make[2]: *** [all-recursive] Error 1

make[2]: Leaving directory `/mnt/lfs/sources/gcc-build/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/mnt/lfs/sources/gcc-build'

make: *** [all] Error 2

And here's the Host Requirements test

Code:

bash, version 4.2.37(1)-release

/bin/sh -> /bin/dash

Binutils: (GNU Binutils for Debian) 2.22

bison (GNU Bison) 2.5

/usr/bin/yacc -> /usr/bin/bison.yacc

bzip2,  Version 1.0.6, 6-Sept-2010.

Coreutils:  8.13

diff (GNU diffutils) 3.2

find (GNU findutils) 4.4.2

GNU Awk 4.0.1

/usr/bin/awk -> /usr/bin/gawk

gcc (Debian 4.7.2-5) 4.7.2

g++ (Debian 4.7.2-5) 4.7.2

(Debian EGLIBC 2.13-38+deb7u8) 2.13

grep (GNU grep) 2.12

gzip 1.5

Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.68-1+deb7u1

m4 (GNU M4) 1.4.16

GNU Make 3.81

patch 2.6.1

Perl version='5.14.2';

GNU sed version 4.2.1

tar (GNU tar) 1.26

makeinfo (GNU texinfo) 4.13

xz (XZ Utils) 5.1.0alpha

g++ compilation OK

Quote:

Originally Posted by Erich (Post 5357053)

I'm using Debian 7 Weezy

Have you symlinked bash to /bin/sh?

What is the output of:

Code:

ls -l /bin/sh

EDIT: You haven't.

Run this:

Code:

# ln -sfT bash /bin/sh

Quote:

Originally Posted by Head_on_a_Stick (Post 5357074)

Have you symlinked bash to /bin/sh?

What is the output of:

Code:

ls -l /bin/sh

EDIT: You haven't.

Run this:

Code:

# ln -sfT bash /bin/sh

Code:

ls -l /bin/sh

Returned

Code:

lrwxrwxrwx 1 root root 4 May 3 12:25 /bin/sh -> bash

Then I ran

Code:

# ln -sfT bash /bin/sh

.. Still not working.

/bin/sh MUST point to /bin/bash

Perhaps you made a typo in the `./configure` options -- try using Copy&Paste from the on-line manual to your terminal screen to eliminate possible errors.

BTW, your "Host Requirements test" [sic] showed /bin/sh symlinked to dash (standard Debian practice) so I don't understand why the output of `ls -l /bin/sh` showed the bash symlink before you ran my suggested command...

You'll also have to start over once you retune dash to bash. The shell used by bash is a requirement to build gcc and binutils. You also should be using traditional glibc rather than eglibc.

Quote:

Originally Posted by ReaperX7 (Post 5358074)

You also should be using traditional glibc rather than eglibc.

Not true. Eglibc is/was just a Glibc fork that accepted support for more architectures than the original Glibc used to. The projects were more or less merged together once the Glibc steering committee was dissolved.

Ah. I stand corrected. Carry on.