LFS 9.0: Cannot make gcc, multiple errors in config.log
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Background: The host environment is a Vagrant VM (on a Mac) running Ubuntu 18.04.3 LTS Bionic with 30GB space. I was a developer but have essentially no Linux or C++ experience beyond a C++ class in college a few years ago, so I can bob my head along and follow a discussion generally but can't do them per se.
When running make (towards the end of 5.5) I get the following error at the end after about 15 minutes:
Code:
checking for suffix of object files... configure: error: in `/mnt/lfs/sources/gcc-9.2.0/build/x86_64-lfs-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
Makefile:12427: recipe for target 'configure-target-libgcc' failed
make[1]: *** [configure-target-libgcc] Error 1
make[1]: Leaving directory '/mnt/lfs/sources/gcc-9.2.0/build'
Makefile:939: recipe for target 'all' failed
make: *** [all] Error 2
Googling about a bit I came to an older post here trying to debug a similar issue. From there I checked this SO answer which had a tiny link to this GCC FAQ entry which discusses the specific error a bit.
From reading over the GCC FAQ I ran a
Code:
grep -n error config.log
(from the /mnt/lfs/sources/gcc-9.2.0/build dir) and got the following relevant lines:
Code:
86 x86_64-linux-gnu
87 Thread model: posix
88 gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
89 configure:4356: $? = 0
90 configure:4345: gcc -V >&5
91 gcc: error: unrecognized command line option '-V'
92 gcc: fatal error: no input files
93 compilation terminated.
94 configure:4356: $? = 1
95 configure:4345: gcc -qversion >&5
96 gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
97 gcc: fatal error: no input files
98 compilation terminated.
...
150 x86_64-linux-gnu
151 Thread model: posix
152 gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
153 configure:4953: $? = 0
154 configure:4942: g++ -V >&5
155 g++: error: unrecognized command line option '-V'
156 g++: fatal error: no input files
157 compilation terminated.
158 configure:4953: $? = 1
159 configure:4942: g++ -qversion >&5
160 g++: error: unrecognized command line option '-qversion'; did you mean '--version'?
161 g++: fatal error: no input files
162 compilation terminated.
...
186 configure:6007: checking for isl 0.15 or later
187 configure:6020: gcc -o conftest -g -O2 -I$$r/$(HOST_SUBDIR)/gmp -I$$s/gmp -I$$r/$(HOST_SUBDIR)/mpfr/src -I$$s/mpfr/src -I$$s/mp 187 c/src -lisl -L$$r/$(HOST_SUBDIR)/gmp/.libs -L$$r/$(HOST_SUBDIR)/mpfr/src/.libs -L$$r/$(HOST_SUBDIR)/mpc/src/.libs -lmpc -lmp 187 fr -lgmp conftest.c -lisl -lgmp >&5
188 conftest.c:10:10: fatal error: isl/schedule.h: No such file or directory
189 #include <isl/schedule.h>
190 ^~~~~~~~~~~~~~~~
191 compilation terminated.
So it looks like I've got two main problems:
two unrecognized references to "qversion"
missing "isl" directory (wherever it is supposed to be) and specifically missing file "isl/schedule.h"
I did a find . -type d -name "*isl*" -print (think the syntax is right, snagged from SO) and got nothing, so there's no "isl" directory anywhere under /mnt/lfs/sources/gcc-9.2.0.
Looking for the "qversion" reference (thinking it was a typo I could correct) led me to this SO answer which implies the Ubuntu host GCC may be outdated.
For ref the Ubuntu host GCC version is: gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
Which is interesting since I'm trying to Compile GCC 9.2.0... But per section 2.2 I should be good to go with anything above 6.2.
So at this point I'm not sure what the solution is for those two problems, if those are in fact the actual problems. Should I apt-get a newer version of GCC (but not above 9.2.0, per section 2.2) ? Or do something else?
If anyone has any insight I'd greatly appreciate it. Thanks in advance.
Preamble:
I have no knowledge of Vagrant. I have never used it.
Things to check:
I have used Ubuntu as a host for LFS (in the past) and I know that stock Ubuntu OOTB needs modifications to satisfy the minimum host requirements. Did you run 'version-check.sh' from chapter 2.2. on the host before you started and resolved the errors that I know occur?
This also could be some sort of interaction between Ubuntu (the build host) and Vagrant. I try not to over-complicate my LFS builds (host running from a USB stick and compiling to an installed hard drive).
Vagrant shouldn't be a factor here because all Vagrant does is provide a wrapper for managing VMs in VirtualBox using the command line and configuration-as-code. Ubuntu is just a guest VM, it doesn't even know Vagrant exists. At least I wouldn't think it would be an issue, I'm just reporting for thoroughness.
What Ubuntu tweaks were necessary? If there is a better distro to use I can certainly try that.
Yes I did run version-check.sh, multiple times in fact, and cross-checked the versions reported against the versions listed in 2.2. I just ran it again and confirmed the versions from the Ubuntu host are within the parameters required by 2.2.
Note I also had previously redirected /bin/sh to /bin/bash instead of the default /bin/dash, before attempting any compilations.
Code:
lfs@lfs-host:/mnt/lfs$ bash version-check.sh
bash, version 4.4.20(1)-release
/bin/sh -> /bin/bash
Binutils: (GNU Binutils) 2.32
bison (GNU Bison) 3.0.4
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2, Version 1.0.6, 6-Sept-2010.
Coreutils: 8.28
diff (GNU diffutils) 3.6
find (GNU findutils) 4.7.0-git
GNU Awk 4.1.4, API: 1.1 (GNU MPFR 4.0.1, GNU MP 6.1.2)
/usr/bin/awk -> /usr/bin/gawk
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
(Ubuntu GLIBC 2.27-3ubuntu1) 2.27
grep (GNU grep) 3.1
gzip 1.6
Linux version 4.15.0-43-generic (buildd@lgw01-amd64-001) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018
m4 (GNU M4) 1.4.18
GNU Make 4.1
GNU patch 2.7.6
Perl version='5.26.1';
Python 3.6.8
sed (GNU sed) 4.4
tar (GNU tar) 1.29
texi2any (GNU texinfo) 6.5
xz (XZ Utils) 5.2.2
g++ compilation OK
One thing I did do "extra" was created a symlink for /usr/bin/texinfo -> /usr/bin/texi2any since it was specifically stating it wanted texinfo but Ubuntu provided texi2any instead. Not sure if that would cause an issue, I can remove it if so.
One interesting bit I've noticed: Despite creating a separate lfs user I still routinely need to sudo many of the commands to get them to work. This is after I chown'd the /mnt/lfs to lfs and even did a chmod -R 777 /mnt/lfs.
Not sure what the underlying problem is, but it seems counter to what the LFS book states. From what I recall reading it should not need sudo unless explicitly stated in the text.
I used the wget scripts from the LFS (chapter 2 I think?) to download all the sources.
For good measure, here's the contents of /mnt/lfs/sources/gcc-9.2.0/build:
Code:
lfs@lfs-host:/mnt/lfs/sources/gcc-9.2.0$ ls -l build
total 700
-rw-r--r-- 1 root root 539389 Nov 24 22:53 Makefile
drwxr-xr-x 5 lfs lfs 4096 Nov 24 23:15 build-x86_64-pc-linux-gnu
-rw-rw-r-- 1 lfs lfs 30854 Nov 24 22:53 config.log
-rwxr-xr-x 1 root root 38375 Nov 24 22:53 config.status
drwxr-xr-x 2 lfs lfs 4096 Nov 24 23:13 fixincludes
drwxr-xr-x 20 lfs lfs 36864 Nov 24 23:27 gcc
drwxr-xr-x 15 lfs lfs 4096 Nov 24 23:14 gmp
drwxr-xr-x 2 lfs lfs 4096 Nov 24 23:13 intl
drwxr-xr-x 3 lfs lfs 4096 Nov 24 23:15 libbacktrace
drwxr-xr-x 4 lfs lfs 4096 Nov 24 23:27 libcc1
drwxr-xr-x 3 lfs lfs 4096 Nov 24 23:15 libcpp
drwxr-xr-x 2 lfs lfs 4096 Nov 24 23:15 libdecnumber
drwxr-xr-x 4 lfs lfs 4096 Nov 24 23:13 libiberty
drwxr-xr-x 3 lfs lfs 4096 Nov 24 23:15 lto-plugin
drwxr-xr-x 6 lfs lfs 4096 Nov 24 23:14 mpc
drwxr-xr-x 7 lfs lfs 4096 Nov 24 23:14 mpfr
-rw-r--r-- 1 root root 13 Nov 24 22:53 serdep.tmp
drwxr-xr-x 3 lfs lfs 4096 Nov 24 23:27 x86_64-lfs-linux-gnu
drwxr-xr-x 3 lfs lfs 4096 Nov 24 23:15 zlib
EDIT: For good measure I renamed those three dirs, removed the build dir, then followed the instructions in 5.5.1 again to untar those three libs into the gcc dir, rerun the scripts in 5.5.1 and am currently re-running make. We'll see what happens.
I asked because absence of one of these libraries is known to cause this problem. Yours however seems to be linked to libgcc.
The gcc build is unusual in that it has more than one configuration stage (binutils does the same). Each stage has its own configure log. Could you search for extra config.logs using the find -name config.log command? You might find a more informative log.
>What Ubuntu tweaks were necessary?
If I remember correctly, /bin/sh points to dash, not bash and texinfo is not installed.
>If there is a better distro to use I can certainly try that.
Personal preference. I currently use MX Linux, it needs more modifications than Ubuntu but is not as heavy as Ubuntu, has no running systemd and has way better support for 32bit.
>One thing I did do "extra" was created a symlink for /usr/bin/texinfo -> /usr/bin/texi2any >since it was specifically stating it wanted texinfo but Ubuntu provided texi2any instead. >Not sure if that would cause an issue, I can remove it if so.
I never thought of simply creating a symbolic link to texi2any calling it texinfo. I would install the texinfo package which is in the 'universe' repository (which is not turned on by default).
I read through the gcc wiki FAQ that you provided and that leads me to 'mpfr', 'gmp' and 'mpc'. These three packages are required to be present in the root gcc directory ($LFS/sources/gcc-9.2.0). After you un-tar gcc to the 'sources' directory, the first thing you do is to un-tar those three packages into the gcc directory and rename their folders to remove the version numbers. Check your gcc directory. You should have three folders there 'mpfr', 'gmp' and 'mpc'. My suggestion is to remove the entire gcc directory and start again.
Will do, once compilation completes or fails again.
During exploration earlier I did find multiple config.log files but wasn't sure how far to explore down that rabbit hole, given I've never really used gcc before.
What is the TLDR of the "more than one configuration stage" in gcc/binutils compilation? What are the purposes of the stages? I understand the theory and basic construction of compilers (e.g. frontend -> intermediate representation -> backend -> machine code) but I'm not familiar with compilation in *nix so not familiar with the configure file or this gcc process at all, this is really my first stab at really diving into linux and its toolset beyond looking up basic commands as needed a handful of times over the years. I intend to go back and study something like LLTHW for everyday working knowledge but figured the best way to start is to dive deep into it with LFS first then build up from there.
I also noted the date on the files. I really recommend that you 'rm -rvf' on that gcc directory. It is also not a good idea to use the same directory multiple number of times.
Hi rsmereka, I was thinking along the same lines and had already wiped the build dir, redeployed those three libs and restarted the compilation which failed again as above unfortunately.
Regarding texinfo, I removed the symlink but apt-get refuses to install texinfo. Apparently the universe repo is already enabled (per output from sudo add-apt-repository universe) and I'm already at the latest version of texinfo, despite texinfo not being anywhere on my path:
Code:
lfs@lfs-host:/mnt/lfs/sources/gcc-9.2.0/build$ sudo apt-get install texinfo
Reading package lists... Done
Building dependency tree
Reading state information... Done
texinfo is already the newest version (6.5.0.dfsg.1-2).
0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.
lfs@lfs-host:/mnt/lfs/sources/gcc-9.2.0/build$ which texinfo
lfs@lfs-host:/mnt/lfs/sources/gcc-9.2.0/build$ <empty line here>
I'm assuming this is because texi2any is "GNU texinfo" ?
Ran apt list --installed | grep texinfo with result texinfo/bionic,now 6.5.0.dfsg.1-2 amd64 [installed] and no indication that it is in fact texi2any.
Reaching the very edge of my knowledge here -- not sure if a package name in the apt list has to match the command name deployed on the filesystem, i.e. should there be a texi2any entry in the apt installed list? Or can the package be named texinfo/bionic in the apt installed list but the package actually deploys the texi2any command on the filesystem? (assuming the latter)
So I don't see a way to install texinfo itself through apt, since it says it is already on my system. Am I misunderstanding something?
I also noted the date on the files. I really recommend that you 'rm -rvf' on that gcc directory. It is also not a good idea to use the same directory multiple number of times.
Just saw this, doing that now. Will redo section 5.5 again and see what happens. thanks.
Result of the command to change GCC default dynamic linker:
Look in the libgcc config.log. You might find something useful there, since the error message mentioned libgcc.
Rsmereka is right about not doing multiple builds in the same directory. Before restarting, you need to delete the entire gcc directory (not just the build directory), then untar it afresh, copy the three maths libraries into it, do all the fiddly configuration, then build.
I am going through the official build log to see if I can find anything relevant.
Nope, nothing! Ironically libgcc is one of the last things to be built.
Well, even after removing the entire gcc dir and recreating as mentioned above the make errored out again, I still get the exact same errors:
Code:
checking for suffix of object files... configure: error: in `/mnt/lfs/sources/gcc-9.2.0/build/x86_64-lfs-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
Makefile:12427: recipe for target 'configure-target-libgcc' failed
make[1]: *** [configure-target-libgcc] Error 1
make[1]: Leaving directory '/mnt/lfs/sources/gcc-9.2.0/build'
Makefile:939: recipe for target 'all' failed
make: *** [all] Error 2
Hazel: There is no "libgcc config.log" but I see ./libcc1/config.log and ./gcc/config.log files so I checked them both.
Result of grep -n error ./libcc1/config.log:
Code:
63:Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
68:gcc: error: unrecognized command line option '-V'
69:gcc: fatal error: no input files
73:gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
74:gcc: fatal error: no input files
119:conftest.c:9:10: fatal error: ac_nonexistent.h: No such file or directory
138:conftest.c:9:10: fatal error: ac_nonexistent.h: No such file or directory
203:conftest.c:52:10: fatal error: minix/config.h: No such file or directory
264:conftest.c:19:10: fatal error: minix/config.h: No such file or directory
427:Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
432:g++: error: unrecognized command line option '-V'
433:g++: fatal error: no input files
437:g++: error: unrecognized command line option '-qversion'; did you mean '--version'?
438:g++: fatal error: no input files
455:conftest.cpp:26:10: fatal error: ac_nonexistent.h: No such file or directory
491:conftest.cpp:26:10: fatal error: ac_nonexistent.h: No such file or directory
581:collect2: error: ld returned 1 exit status
611:| /* Override any GCC internal prototype to avoid an error.
Result of grep -n error ./gcc/config.log:
Code:
78:gcc: error: unrecognized command line option '-V'
79:gcc: fatal error: no input files
83:gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
84:gcc: fatal error: no input files
134:Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
139:g++: error: unrecognized command line option '-V'
140:g++: fatal error: no input files
144:g++: error: unrecognized command line option '-qversion'; did you mean '--version'?
145:g++: fatal error: no input files
166:conftest.cpp:9:10: fatal error: ac_nonexistent.h: No such file or directory
185:conftest.cpp:9:10: fatal error: ac_nonexistent.h: No such file or directory
250:conftest.cpp:52:10: fatal error: minix/config.h: No such file or directory
311:conftest.cpp:19:10: fatal error: minix/config.h: No such file or directory
347:conftest.c:24:10: fatal error: ac_nonexistent.h: No such file or directory
381:conftest.c:24:10: fatal error: ac_nonexistent.h: No such file or directory
450:conftest.cpp:64:14: error: expected primary-expression before 'long'
453:conftest.cpp:64:14: error: expected ')' before 'long'
454:conftest.cpp:65:14: error: expected ')' before ';' token
457:conftest.cpp:65:14: error: expected ')' before ';' token
540:conftest.cpp:68:56: error: size of array 'test_array' is negative
625:conftest.cpp:68:58: error: size of array 'test_array' is negative
713:conftest.cpp:68:58: error: size of array 'test_array' is negative
801:conftest.cpp:68:58: error: size of array 'test_array' is negative
896:conftest.cpp:68:22: error: expected primary-expression before ')' token
979:conftest.cpp:69:22: error: expected primary-expression before ')' token
1079:conftest.cpp:70:23: error: expected primary-expression before ')' token
1164:conftest.cpp:71:23: error: expected primary-expression before ')' token
1255:conftest.cpp:40:2: error: #error compiler not affected by placement new aliasing bug
1256: #error compiler not affected by placement new aliasing bug
1299:| #error compiler not affected by placement new aliasing bug
1373:conftest.cpp:75:10: fatal error: valgrind.h: No such file or directory
1457:conftest.cpp:42:10: fatal error: valgrind.h: No such file or directory
1510:conftest.cpp:42:10: fatal error: valgrind/memcheck.h: No such file or directory
1559:| #error VALGRIND_DISCARD not defined
1564:conftest.cpp:42:10: fatal error: memcheck.h: No such file or directory
1613:| #error VALGRIND_DISCARD not defined
1730:conftest.cpp:72:10: fatal error: direct.h: No such file or directory
1819:conftest.cpp:74:10: fatal error: ldfcn.h: No such file or directory
1910:conftest.cpp:76:10: fatal error: thread.h: No such file or directory
2001:conftest.cpp:77:9: error: expected unqualified-id before 'not' token
2090:conftest.cpp:83:8: error: 'big' was not declared in this scope
2189:conftest.cpp:76:10: fatal error: ac_nonexistent.h: No such file or directory
2297:collect2: error: ld returned 1 exit status
2379:| /* Override any GCC internal prototype to avoid an error.
2395:collect2: error: ld returned 1 exit status
2477:| /* Override any GCC internal prototype to avoid an error.
2493:collect2: error: ld returned 1 exit status
2575:| /* Override any GCC internal prototype to avoid an error.
2591:collect2: error: ld returned 1 exit status
2673:| /* Override any GCC internal prototype to avoid an error.
2689:collect2: error: ld returned 1 exit status
2771:| /* Override any GCC internal prototype to avoid an error.
2790:collect2: error: ld returned 1 exit status
2872:| /* Override any GCC internal prototype to avoid an error.
2888:collect2: error: ld returned 1 exit status
2970:| /* Override any GCC internal prototype to avoid an error.
2989:collect2: error: ld returned 1 exit status
3071:| /* Override any GCC internal prototype to avoid an error.
3087:collect2: error: ld returned 1 exit status
3169:| /* Override any GCC internal prototype to avoid an error.
3195:collect2: error: ld returned 1 exit status
3277:| /* Override any GCC internal prototype to avoid an error.
3322:collect2: error: ld returned 1 exit status
3426:| /* Override any GCC internal prototype to avoid an error.
3496:configure:9850: checking for ferror_unlocked
3523:collect2: error: ld returned 1 exit status
3644:| /* Override any GCC internal prototype to avoid an error.
3728:conftest.cpp:148:21: error: expected primary-expression before ')' token
3891:conftest.cpp:148:21: error: expected primary-expression before ')' token
4068:conftest.cpp:151:19: error: expected primary-expression before ')' token
4231:conftest.cpp:115:10: fatal error: vfork.h: No such file or directory
4558:configure:11158: checking whether ferror_unlocked is declared
4581:conftest.cpp:174:28: error: 'fprintf_unlocked' was not declared in this scope
4818:conftest.cpp:192:28: error: 'ldgetname' was not declared in this scope
5147:conftest.cpp:189:10: fatal error: ac_nonexistent.h: No such file or directory
5542:collect2: error: ld returned 1 exit status
5763:collect2: error: ld returned 1 exit status
6106:ac_cv_func_ferror_unlocked=yes
6346:gcc_cv_have_decl_ferror_unlocked=yes
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
which failed again as above unfortunately. 
