Re: [lfs-support] Installation of Linux API Headers (chapter 6.7.1) problem
You should be chrooted into your new LFS build before installing the headers at step 6.7.1. As such your version of bash should look similar to this: bash -version GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) My bash version is: root:/sources# bash -version GNU bash, version 4.2.45(2)-release (i686-pc-linux-gnu) If command substitution is broken in your temp tools bash while in chroot, then your host wasn't setup properly. You should have bash as your default shell and bison yacc, not some other yacc. The host system requirements page helps set the stage for that. My linux distribution is Debian 7.1 and 'Berkley LA LR Yacc parser generator' is installed by default. I should change it to 'YACC-compatible parser generator' and rebuild bash in tools. Thank you, gentlemen. -- With respect, Artem Orlov -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] LFSv7.4 stuck at section 6.9.1
Hi everyone,
My linux machine details:
# uname -r : 3.2.0-50-generic-pae
using ubuntu 12.04 LTS
LFS version:7.4
I've followed the instructions in the book strictly.Successfully completed
chapter5.
After chrooting into the lfs partition,i.e, section 6.9.1 when i ran the
command:
../glibc-2.18/configure --prefix=/usr --disable-profile
--enable-kernel=2.6.32 \
--libexecdir=/usr/lib/glibc
and then it throws an error like this : (this is a copy paste from the
terminal)
root:/sources/glibc-build2:# ../glibc-2.18/configure --prefix=/usr
--disable-profile --enable-kernel=2.6.32 \
--libexecdir=/usr/lib/glibc
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for suffix of object files... configure: error: in
`/sources/glibc-build2':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
Now, the contents of config.log are:
root:/sources/glibc-build2:# cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by GNU C Library configure (see version.h), which was
generated by GNU Autoconf 2.68. Invocation command line was
$ ../glibc-2.18/configure --prefix=/usr --disable-profile
--enable-kernel=2.6.32 --libexecdir=/usr/lib/glibc
## - ##
## Platform. ##
## - ##
hostname = shiva-desktop
uname -m = i686
uname -r = 3.2.0-50-generic-pae
uname -s = Linux
uname -v = #76-Ubuntu SMP Tue Jul 9 19:24:55 UTC 2013
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /bin
PATH: /usr/bin
PATH: /sbin
PATH: /usr/sbin
PATH: /tools/bin
## --- ##
## Core tests. ##
## --- ##
configure:2344: checking build system type
configure:2358: result: i686-pc-linux-gnu
configure:2378: checking host system type
configure:2391: result: i686-pc-linux-gnu
configure:2460: checking for gcc
configure:2476: found /tools/bin/gcc
configure:2487: result: gcc
configure:2716: checking for C compiler version
configure:2725: gcc --version 5
../glibc-2.18/configure: line 2727: /tools/bin/gcc: No such file or
directory
configure:2736: $? = 127
configure:2725: gcc -v 5
../glibc-2.18/configure: line 2727: /tools/bin/gcc: No such file or
directory
configure:2736: $? = 127
configure:2725: gcc -V 5
../glibc-2.18/configure: line 2727: /tools/bin/gcc: No such file or
directory
configure:2736: $? = 127
configure:2725: gcc -qversion 5
../glibc-2.18/configure: line 2727: /tools/bin/gcc: No such file or
directory
configure:2736: $? = 127
configure:2741: checking for suffix of object files
configure:2763: gcc -c conftest.c 5
../glibc-2.18/configure: line 2765: /tools/bin/gcc: No such file or
directory
configure:2767: $? = 127
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME GNU C Library
| #define PACKAGE_TARNAME glibc
| #define PACKAGE_VERSION (see version.h)
| #define PACKAGE_STRING GNU C Library (see version.h)
| #define PACKAGE_BUGREPORT http://sourceware.org/bugzilla/;
| #define PACKAGE_URL http://www.gnu.org/software/glibc/;
| #define PKGVERSION (GNU libc)
| #define REPORT_BUGS_TO http://www.gnu.org/software/libc/bugs.html
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2781: error: in `/sources/glibc-build2':
configure:2783: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
## ##
## Cache variables. ##
## ##
ac_cv_build=i686-pc-linux-gnu
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i686-pc-linux-gnu
ac_cv_prog_ac_ct_CC=gcc
## - ##
## Output variables. ##
## - ##
AR=''
AS=''
ASFLAGS_config=''
AUTOCONF=''
AWK=''
BASH_SHELL=''
BISON=''
BUILD_CC=''
CC='gcc'
CFLAGS=''
CPP=''
CPPFLAGS=''
CPPUNDEFS=''
CXX=''
CXXFLAGS=''
CXX_SYSINCLUDES=''
DEFINES=''
DEFS=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
INSTALL_DATA=''
INSTALL_INFO=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
KSH=''
LD=''
LDFLAGS=''
LIBGD=''
LIBOBJS=''
LIBS=''
LN_S=''
LTLIBOBJS=''
MAKE=''
MAKEINFO=''
MSGFMT=''
NM=''
OBJCOPY=''
OBJDUMP=''
OBJEXT=''
[lfs-support] Good day sir!
I would like to ask some notes how to begin my blfs by building samba server on it? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFSv7.4 stuck at section 6.9.1
Le 24/09/2013 11:25, Kodali Sivakiran a écrit :
Hi everyone,
[description of the failure]
In the upper section of config.log we can see that:
configure:2725: gcc --version 5
../glibc-2.18/configure: line 2727: /tools/bin/gcc: No such file or
directory
configure:2736: $? = 127
...
not only gcc ,later i've checked with some of the binaries under
/tools/bin, they say the same thing when i try to use them...No such
file or directory
WHAT MIGHT BE THE REASON??
gcc is a program which mainly runs other executables (cpp for
preprocessing, cc1 for compiling, etc). So even if /tools/bin/gcc is
there, it could be somehow unable to find one ore all of those
executables, which would explain the 'no such file...' diagnostic.
In an attempt to understand the problem, i did this outside the chroot
environment:
shiva@shiva-desktop:/$ ldd /tools/bin/gcc
linux-gate.so.1 = (0xb77dd000)
libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xb761b000)
/lib/ld-linux.so.2 (0xb77de000)
so, does it mean that my /tools/bin/gcc got linked with the host
libraries rather than my /tools/lib ???
No it doesn't. When outside the chroot environment, you are using the
host libraries. You have to enter the chroot environment to do that test.
SUGGEST ME SOMETHING ON THIS, SO, THAT I CAN PROCEED FURTHER...
Try:
Enter the chroot environment again and type:
echo 'main(){}' | gcc -x c -v -
You might get some information on where it fails to find files.
If it works, add -Wl,-verbose before the last dash to the above command.
You'll get information on whrer le linker looks for files.
Another possibility is that you forgot to mount the virtual files. Type:
ls /dev (inside the chroot environment).
regards
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] LFSv7.4 stuck at section 6.9.1
On Sep 24, 2013, at 4:25 AM, Kodali Sivakiran wrote: WHAT MIGHT BE THE REASON?? In an attempt to understand the problem, i did this outside the chroot environment: shiva@shiva-desktop:/$ ldd /tools/bin/gcc linux-gate.so.1 = (0xb77dd000) libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xb761b000) /lib/ld-linux.so.2 (0xb77de000) so, does it mean that my /tools/bin/gcc got linked with the host libraries rather than my /tools/lib ??? If you were able to chroot, and you can't run gcc because of the error above, it means that most likely the gcc source and build directories weren't removed before rebuilding gcc during pass2 in chapter 5. You need to rebuild gcc. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFSv7.4 stuck at section 6.9.1
I have a problim compiling my samba...and this output were given client/smbmount.c:25:26: fatal error: linux/smb_fs.h: No such file or directory compilation terminated. The following command failed: gcc -I. -I/sources/samba-3.0.30/source -O -D_SAMBA_BUILD_=3 -I/sources/samba-3.0.30/source/popt -I/sources/samba-3.0.30/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/sources/samba-3.0.30/source/lib -D_SAMBA_BUILD_=3 -fPIC -c client/smbmount.c -o client/smbmount.o make: *** [client/smbmount.o] Error 1 can you help me how to solve this problem? - Original Message - From: William Harrington kb0...@berzerkula.org To: LFS Support List lfs-support@linuxfromscratch.org Cc: Sent: Tuesday, September 24, 2013 11:36 PM Subject: Re: [lfs-support] LFSv7.4 stuck at section 6.9.1 On Sep 24, 2013, at 4:25 AM, Kodali Sivakiran wrote: WHAT MIGHT BE THE REASON?? In an attempt to understand the problem, i did this outside the chroot environment: shiva@shiva-desktop:/$ ldd /tools/bin/gcc linux-gate.so.1 = (0xb77dd000) libc.so.6 = /lib/i386-linux-gnu/libc.so.6 (0xb761b000) /lib/ld-linux.so.2 (0xb77de000) so, does it mean that my /tools/bin/gcc got linked with the host libraries rather than my /tools/lib ??? If you were able to chroot, and you can't run gcc because of the error above, it means that most likely the gcc source and build directories weren't removed before rebuilding gcc during pass2 in chapter 5. You need to rebuild gcc. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] chroot into the temporary ...?
hi, It reads 'That is, we chroot into the temporary mini Linux system, ..' in Section6.1 of LFS7.4. but when i run 'sudo chroot /mnt/lfs', it returns 'chroot: failed to run command `/bin/bash': No such file or directory'. Of course /mnt/lfs/bin/bash not exists and then I tried 'sudo chroot /mnt/lfs/tools', it also 'chroot: failed to run command `/bin/bash': No such file or directory',but /mnt/lfs/tools/bin/bash exists. I really have no idea with the problem,maybe I have missed something in Ch5? Thanks in advance and sorry for my English. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] chroot into the temporary ...?
On Wed, 25 Sep 2013 08:41:37 +0800 (CST) Wiky wii...@yeah.net wrote: hi, It reads 'That is, we chroot into the temporary mini Linux system, ..' in Section6.1 of LFS7.4. but when i run 'sudo chroot /mnt/lfs', it returns 'chroot: failed to run command `/bin/bash': No such file or directory'. Of course /mnt/lfs/bin/bash not exists and then I tried 'sudo chroot /mnt/lfs/tools', it also 'chroot: failed to run command `/bin/bash': No such file or directory',but /mnt/lfs/tools/bin/bash exists. I really have no idea with the problem,maybe I have missed something in Ch5? Thanks in advance and sorry for my English. You didn't specify which program should chroot exec() after it chroots itself, so it did the default: tried to execute /bin/bash. Since there is no such program (/mnt/lfs/bin/bash in the root filesystem), it failed. To fix this, you should specify which program should be executed. Like this: chroot /mnt/lfs /tools/bin/bash But the full command is in Chapter 6.4. so look it up there. -- You don't need an AI for a robot uprising. Humans will do just fine. signature.asc Description: PGP signature -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFSv7.4 stuck at section 6.9.1
On Tue, 24 Sep 2013 17:37:28 -0700 (PDT) Phoebe Bacotot pupreen_lo...@yahoo.com wrote: I have a problim compiling my samba...and this output were given client/smbmount.c:25:26: fatal error: linux/smb_fs.h: No such file or directory compilation terminated. The following command failed: gcc -I. -I/sources/samba-3.0.30/source -O -D_SAMBA_BUILD_=3 -I/sources/samba-3.0.30/source/popt -I/sources/samba-3.0.30/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/sources/samba-3.0.30/source/lib -D_SAMBA_BUILD_=3 -fPIC -c client/smbmount.c -o client/smbmount.o make: *** [client/smbmount.o] Error 1 can you help me how to solve this problem? Okay, so bonus points for persistence. :) This belongs to blfs-support. Join that mailgroup, post your question there and I will then help you out. And when you do that, do include a bit more of the build log. There may be more information in there. -- You don't need an AI for a robot uprising. Humans will do just fine. signature.asc Description: PGP signature -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] chroot into the temporary ...?
I got it, Thank you. At 2013-09-25 09:49:36,Aleksandar Kuktin akuk...@gmail.com wrote: On Wed, 25 Sep 2013 08:41:37 +0800 (CST) Wiky wii...@yeah.net wrote: hi, It reads 'That is, we chroot into the temporary mini Linux system, ..' in Section6.1 of LFS7.4. but when i run 'sudo chroot /mnt/lfs', it returns 'chroot: failed to run command `/bin/bash': No such file or directory'. Of course /mnt/lfs/bin/bash not exists and then I tried 'sudo chroot /mnt/lfs/tools', it also 'chroot: failed to run command `/bin/bash': No such file or directory',but /mnt/lfs/tools/bin/bash exists. I really have no idea with the problem,maybe I have missed something in Ch5? Thanks in advance and sorry for my English. You didn't specify which program should chroot exec() after it chroots itself, so it did the default: tried to execute /bin/bash. Since there is no such program (/mnt/lfs/bin/bash in the root filesystem), it failed. To fix this, you should specify which program should be executed. Like this: chroot /mnt/lfs /tools/bin/bash But the full command is in Chapter 6.4. so look it up there. -- You don't need an AI for a robot uprising. Humans will do just fine. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] chroot into the temporary ...?
On Wed, 25 Sep 2013 09:56:34 +0800 (CST) Wiky wii...@yeah.net wrote: I got it, Thank you. At 2013-09-25 09:49:36,Aleksandar Kuktin akuk...@gmail.com wrote: On Wed, 25 Sep 2013 08:41:37 +0800 (CST) Wiky wii...@yeah.net wrote: hi, It reads 'That is, we chroot into the temporary mini Linux system, ..' in Section6.1 of LFS7.4. but when i run 'sudo chroot /mnt/lfs', it returns 'chroot: failed to run command `/bin/bash': No such file or directory'. Of course /mnt/lfs/bin/bash not exists and then I tried 'sudo chroot /mnt/lfs/tools', it also 'chroot: failed to run command `/bin/bash': No such file or directory',but /mnt/lfs/tools/bin/bash exists. I really have no idea with the problem,maybe I have missed something in Ch5? Thanks in advance and sorry for my English. You didn't specify which program should chroot exec() after it chroots itself, so it did the default: tried to execute /bin/bash. Since there is no such program (/mnt/lfs/bin/bash in the root filesystem), it failed. To fix this, you should specify which program should be executed. Like this: chroot /mnt/lfs /tools/bin/bash But the full command is in Chapter 6.4. so look it up there. -- You don't need an AI for a robot uprising. Humans will do just fine. Don't top post. Also, a post in the thread LFSv7.4 stuck at section 6.9.1 gave me an idea about why you were unable to run `chroot /mnt/lfs/tools'. The bash that lives there requests the dynamic interpreter (run-time linker) /tools/lib/ld-whatever.so and that did not exist. You can verify this by adding a symbolic link `tools' to /mnt/lfs/tools which points to `..'. Like this (command run from /mnt/lfs/tools): ln -sv .. tools With this, you should be able to do `chroot /mnt/lfs/tools' without any problems. Just don't execute Section 6. with that setup because you will have A LOT of problems and a lot of thrashing. ([thinking]...or maybe not... anyway, don't do it. not when you are building LFS for the first time) -- You don't need an AI for a robot uprising. Humans will do just fine. signature.asc Description: PGP signature -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] chroot into the temporary ...?
On Wed, Sep 25, 2013 at 08:41:37AM +0800, Wiky wrote: hi, It reads 'That is, we chroot into the temporary mini Linux system, ..' in Section6.1 of LFS7.4. but when i run 'sudo chroot /mnt/lfs', Why do you think that 'sudo' is the command to run here ? Do we build sudo in chapter 5 (/tools) ? it returns 'chroot: failed to run command `/bin/bash': No such file or directory'. Of course /mnt/lfs/bin/bash not exists and then I tried 'sudo chroot /mnt/lfs/tools', it also 'chroot: failed to run command `/bin/bash': No such file or directory',but /mnt/lfs/tools/bin/bash exists. I really have no idea with the problem,maybe I have missed something in Ch5? Thanks in advance and sorry for my English. Apart from using sudo instead of su, why doesn't /bin/bash exist in /mnt/lfs ? If you are following the book, we create the /mnt/lfs/bin/bash symlink in section 6.6 - and we enter chroot *after* that, not in section 6.1. I'm sure that reading the book is *hard* for people who don't have English as a native language, but you seem to be making false assumptions about what the book says. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] lfs-support Digest, Vol 2963, Issue 1
Hi William Harrington, Thanks for the advice...but what if i say i've done my gcc pass-2 build in $LFS/source/gcc-build2/ Do you think what you said still apply..??? (i doubt it..plz clarify..) thanks Regards Siva. On Wed, Sep 25, 2013 at 6:11 AM, lfs-support-requ...@linuxfromscratch.orgwrote: Send lfs-support mailing list submissions to lfs-support@linuxfromscratch.org To subscribe or unsubscribe via the World Wide Web, visit http://linuxfromscratch.org/mailman/listinfo/lfs-support or, via email, send a message with subject or body 'help' to lfs-support-requ...@linuxfromscratch.org You can reach the person managing the list at lfs-support-ow...@linuxfromscratch.org When replying, please edit your Subject line so it is more specific than Re: Contents of lfs-support digest... Today's Topics: 1. Re: Installation of Linux API Headers (chapter 6.7.1) problem (? ?) 2. LFSv7.4 stuck at section 6.9.1 (Kodali Sivakiran) 3. Good day sir! (Phoebe Bacotot) 4. Re: LFSv7.4 stuck at section 6.9.1 (Pierre Labastie) 5. Re: LFSv7.4 stuck at section 6.9.1 (William Harrington) 6. Re: LFSv7.4 stuck at section 6.9.1 (Phoebe Bacotot) 7. chroot into the temporary ...? (Wiky) -- Message: 1 Date: Tue, 24 Sep 2013 12:35:40 +0400 From: ? ? a.or...@veedo.ru Subject: Re: [lfs-support] Installation of Linux API Headers (chapter 6.7.1) problem To: LFS Support List lfs-support@linuxfromscratch.org Message-ID: cagfykrjjhpitv4k7ygkwfhnrspv9yxji3ytjiwxztncsnpv...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 You should be chrooted into your new LFS build before installing the headers at step 6.7.1. As such your version of bash should look similar to this: bash -version GNU bash, version 4.2.45(2)-release (x86_64-unknown-linux-gnu) My bash version is: root:/sources# bash -version GNU bash, version 4.2.45(2)-release (i686-pc-linux-gnu) If command substitution is broken in your temp tools bash while in chroot, then your host wasn't setup properly. You should have bash as your default shell and bison yacc, not some other yacc. The host system requirements page helps set the stage for that. My linux distribution is Debian 7.1 and 'Berkley LA LR Yacc parser generator' is installed by default. I should change it to 'YACC-compatible parser generator' and rebuild bash in tools. Thank you, gentlemen. -- With respect, Artem Orlov -- next part -- An HTML attachment was scrubbed... URL: http://linuxfromscratch.org/pipermail/lfs-support/attachments/20130924/05732075/attachment-0001.html -- Message: 2 Date: Tue, 24 Sep 2013 14:55:31 +0530 From: Kodali Sivakiran ksk.pink...@gmail.com Subject: [lfs-support] LFSv7.4 stuck at section 6.9.1 To: lfs-support@linuxfromscratch.org Message-ID: CAHVccjoXO0ypexKsFjaqJqus4LVwO_eCT3D88oi2n= xvv1d...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hi everyone, My linux machine details: # uname -r : 3.2.0-50-generic-pae using ubuntu 12.04 LTS LFS version:7.4 I've followed the instructions in the book strictly.Successfully completed chapter5. After chrooting into the lfs partition,i.e, section 6.9.1 when i ran the command: ../glibc-2.18/configure --prefix=/usr --disable-profile --enable-kernel=2.6.32 \ --libexecdir=/usr/lib/glibc and then it throws an error like this : (this is a copy paste from the terminal) root:/sources/glibc-build2:# ../glibc-2.18/configure --prefix=/usr --disable-profile --enable-kernel=2.6.32 \ --libexecdir=/usr/lib/glibc checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for suffix of object files... configure: error: in `/sources/glibc-build2': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details Now, the contents of config.log are: root:/sources/glibc-build2:# cat config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by GNU C Library configure (see version.h), which was generated by GNU Autoconf 2.68. Invocation command line was $ ../glibc-2.18/configure --prefix=/usr --disable-profile --enable-kernel=2.6.32 --libexecdir=/usr/lib/glibc ## - ## ## Platform. ## ## - ## hostname = shiva-desktop uname -m = i686 uname -r = 3.2.0-50-generic-pae uname -s = Linux uname -v = #76-Ubuntu SMP Tue Jul 9 19:24:55 UTC 2013 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo
