![]() |
5.9. Binutils-2.25 - Pass 2 configure fails
Dear all,
I am trying to do 5.9. Binutils-2.25 - Pass 2 but i have a configure error. I have centos6 as the host os. Code:
lfs:/mnt/lfs/sources/binutils-2.25$ CC=$LFS_TGT-gcc \ Code:
This file contains any messages produced by compilers while Code:
[root@Unknown Desktop]# bash version-check.sh |
btw I using Linux From Scratch - Version 7.7 book
|
Hi
Did you forget Code:
mkdir -v ../binutils-build |
hi spikey,
I did not forget to issue the configure outside the source directory, I was in binutils-build . Also I have added the version check in the previous post. |
Quote:
should be /mnt/lfs/sources/binutils-build |
hey dont you believe me! see below:
Quote:
|
That is not the same as the 1st post? check
what dose this ouput echo 'main(){}' > dummy.c $LFS_TGT-gcc dummy.c readelf -l a.out | grep ': /tools' |
hi, sorry you was right about the posts,
the output of: Quote:
Quote:
|
whats the output of
Code:
env Also did you remove binutils-2.2.5 and binutils-build dir from 1st build? |
env
Quote:
Quote:
|
regarding binutils source and build folders, 1st build i did remove them, i unpaked the tar again for 2nd pass.
|
something went wrong in in glib or gcc
If you removed all untarred dir & build dir when you finished building, I would start again you have this in config log ../binutils-2.25/configure: ./a.out: /tools/lib64/ld-linux-x86-64.so.2: bad ELF interpreter: No such file or directory |
hi this is the second time round im am trying this, glibc and gcc compile and install fine. - no errors. what is going to change by starting from binutils pass1? thats where i started again the second time. I have made no changes to the process! I always get stuck at binutils pass2...
|
I have checked the config.log file and it points to 4246 of configure:
Quote:
|
Well if your copy pasting commands they should be good, the only other thing is the host
I have built 7.7 a few times now but not on centos i build from lfs. Maybe try slack or arch you can wait see if anyone else can figure the error out. The only only other thing you did run the case $(uname -m) in x86_64) mkdir -v /tools/lib && ln -sv lib /tools/lib64 ;; esac end of binutils 1st pass |
im sure people have been able to do this (get past binutils 2nd pass) on centos somewhere and I should be ok because my host has all the prequisite software installed as version check shows....I really need help I really dont wanna move on to another distro for host.....
|
last idea
Code:
ls -l $LFS/tools |
Unfortunately it's the distribution. CentOS is based on Red Hat which it and Fedora are known to have problems. We aren't entirely certain, but the way they patch certain packages often affects how the system works and it ends up killing GCC.
The evidence of this can be found by running this: Code:
cat > library-check.sh << "EOF" |
thanks for helping...
Quote:
|
run the script Reaper mentioned
also shouldn't lib be linked to lib64 |
hi spiky, can you send me the full command to link correctly lib and lib64 and I will try issue the configure command again, thanks in advance.
|
At the end of binutils pass 1 Ch 5.4
|
issued:
Quote:
Quote:
Quote:
|
Not got a 64bit machine about but lib64 should be linked
Reaper will know |
thanks for the time you took on this...do you think Reaper will come back then? Is there a way of notifying him I would like his input?
|
I really think thats the problem
whats inside tools/lib64 also the script reaper put |
hi spiky,
this is what is in tools/lib64 Quote:
|
output from reaper script is:
Quote:
|
Quote:
Check if /tools/lib has it? Or is it present in /tools filesystem tree by using 'find' command. |
Hi veerain,
The file seems to be in /tools/lib, see below the output of the find command I issued. Quote:
|
Try linking tools/lib to tools/lib64
this was supposed to be done in binutils 1st pass |
tried but still no luck, also i cant see a sym link created although it says file exists when i issue the command again:
Quote:
|
Quote:
So I say before installing binutils pass1 you should go the /tools directory and run 'mkdir lib64; ln -s lib64 lib'. Or If you want to run anyway from this point onward, then copy all the files, directories in /tools/lib to /tools/lib64. Careful to not overwrite files in /tools/lib64 especially symlinks overwriting regular files. And then delete /tools/lib and put a symlink from /tools/lib to /tools/lib64. Code:
rm -fr /tools/lib |
hi veerain, thats worked! I decided to continue rather than start again, thanks so much for your help on this problem.
|
You are welcome.
|
All times are GMT -5. The time now is 11:34 AM. |