Ok, Thank U __J. I will do that...
Regards
Kartheek

Hello All,

Every thing works fine till installation of gcc [pg47 LFSv6], but when it comes to the installation of linux-libc-headers i am getting confused....

My triplet:i686-pc-linux-gnu

what should be the linuux-libc-header installation commands???

cp -R include/asm-i386 /tools/include/asm
OR
cp -R include/asm-i386 /tools/include/asm-i386
OR
cp -R include/asm-i386 /tools/include

I am asking this because this is causing troubles during the installation of glibc[while running make], thats what i am predicting.....

And also while creating platform specific include asm symlink, what should be the command??

Hi All,

This is what i get when i run the "make" while installing glibc....

[part of it follows..]

../sysdeps/unix/sysv/linux/sys/syscall.h:25:24: asm/unstd.h: No such file or directory
In file included from ../sysdeps/unix/sysv/linux/sys/param.h:24,
from ../sysdeps/i386/i386/hp-timing.h:25,
from ../nptl/descr.h:28,
from ../nptl/i386/i386/../tls.h:98,
from ../nptl/i386/i386/tls.h:34,
from ../include/tls.h:6,
from ../sysdeps/unix/sysv/linux/i386/sysdep.h:29,
from <stdin>:1:
/tools/glibc-kernheaders/linux/param.h:4:23: asm/param.h: No such file or directory
In file included from ../socket/sys/socket.h:35,
from../include/sys/socket.h:2,
from ../inet/netinit/in.h:24,
from ../include/netinit/in.h:3,
from ../resolv/resolv.h:57,
from ../include/resolv.h:11,
from ../nptl/descr.h:39,
from ../nptl/i386/i386/../tls.h:98,
from ../nptl/i386/i386/tls.h:34,
from ../include/tls.h:6,
from ../sysdeps/unix/sysv/linux/i386/sysdep.h:29,
from <stdin>:1:
../sysdeps/unix/sysv/linux/bits/socket.h:305:24: asm/socket.h: No such file or directory
make[2]: *** [/mnt/lfs/sources/glibc-build/tcb-offsets.h] Error 1
make[2]: Leaving directory '/mnt/lfs/sources/glibc-2.3.4-20040701/csu'
make[1]: *** [csu/subdir_lib] Error2
make[1]: Leaving directory '/mnt/lfs/sources/glibc-2.3.4-20040701'
make: ***[all] Error 2



Am I right in predicting that the error is due to improper installation of Linux-Libc_headers????

Thanx

I assume you are building the actual system, you will want this one

Hello,

Same[as put in my previous post] error is turning up when i run "make"during the installtion of of glibc....
I am not able to proceed furthur.....
Regards
KartheeK

is there a directory called /tools/include/asm and does it contain header files?

yes, theris a folder and it contains a lot of header files

By "/tools/include/asm" , i am assuming it as on my LFS partition.... as such ther is no directory "/tools/include/asm" on my host machine...

This is what i am getting still.. when i am running "make" during glibc installation..

In file included from ../sysdeps/unix/sysdep.h:21,
from ../sysdeps/unix/i386/sysdep.h:19,
from ../sysdeps/unix/sysv/linux/i386/sysdep.h:24,
from <stdin>:1:
../sysdeps/unix/sysv/linux/sys/syscall.h:25:24: asm/unistd.h: No such file or directory
In file included from ../sysdeps/unix/sysv/linux/sys/param.h:24,
from ../sysdeps/i386/i686/hp-timing.h:25,
from ../nptl/descr.h:28,
from ../nptl/sysdeps/i386/i686/../tls.h:98,
from ../nptl/sysdeps/i386/i686/tls.h:34,
from ../include/tls.h:6,
from ../sysdeps/unix/sysv/linux/i386/sysdep.h:29,
from <stdin>:1:
/tools/glibc-kernheaders/linux/param.h:4:23: asm/param.h: No such file or directory
In file included from ../socket/sys/socket.h:35,
from ../include/sys/socket.h:2,
from ../inet/netinet/in.h:24,
from ../include/netinet/in.h:3,
from ../resolv/resolv.h:57,
from ../include/resolv.h:11,
from ../nptl/descr.h:39,
from ../nptl/sysdeps/i386/i686/../tls.h:98,
from ../nptl/sysdeps/i386/i686/tls.h:34,
from ../include/tls.h:6,
from ../sysdeps/unix/sysv/linux/i386/sysdep.h:29,
from <stdin>:1:
../sysdeps/unix/sysv/linux/bits/socket.h:305:24: asm/socket.h: No such file or directory
make[2]: *** [/mnt/lfs/sources/gcc-build/tcb-offsets.h] Error 1
make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4-20040701/csu'
make[1]: *** [csu/subdir_lib] Error 2
make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4-20040701'
make: *** [all] Error 2

the red area is your problem, when you configure glibc with --with-headers=/tools/include, in /tools/include there needs to be a directory called asm containing the headers you copied earlier. this should fix it for you:

go back to the linux-libc-headers package you had earlier, extract it and cd into it
next do:
verify that /tools/include/asm has headers in it ( namely socket.h and the rest that are specifically mentioned in your error output above).

Hello __J,
Firstly, tons of thanx for the wonderful and speedy support you are giving..
Everything is in place as u have told. ther surely is a /tools/include/asm folder with all the mentioned header files...
Still the same error.....
But one thing you are mentioning to configure glibc with "--with-headers=/tools/include" whereas in the LFS v6 book pg 51in the topic"Installation Of Glibc", they have asked to configure glibc with "--with-headers=/tools/glibc-kernheaders" ????

if you don't have the /tools/glibc-kernheaders directory, make sure you do this step:
http://lfs.osuosl.org/lfs/view/6.0/c...l-headers.html

Yes, i have done that..
I am thinking of starting everything afresh....
I will get back with any errors[let me hope they wont this time ]...
Some great person has said: "TRY TRY UNTIL YOU SUCCEED" I think I should do it....

Hello All,
After installing afresh each and everything, i am still getting the same error. Ther is some thing mentioned about CLAGS & CXXFLAGS in:
http://lfs.osuosl.org/lfs/view/6.0/chapter05/glibc.html
Is that is what troubling me??? What do i need to do to overcome that??

Thanx
KartheeK

I'd recommend not starting over each time, you will learn more about troubleshooting problems ( you can fix almost anything with the right tools).

here is what you need to make sure of:

you have a directory called /tools/glibc-kernheaders

the /tools/glibc-kernheaders directory contains another directory called asm that contains headers from the linux-2.6.x kernel that comes with the LFS packages.

CFLAGS and CXXFLAGS in the sense that the directions are talking about is optimizations. you can specify what processor to build applications for (either optimizing for a processor while maintaining compatibility for older processors or compiling for a certain processor ( in which breaks compatibility with processors that are not at least equal to or better than the one the build was optimized for). Don't worry about these for now, you probably don't want to start messing around with this until you get a little more comfortable with it all ( overdoing optimizing or incorrectly doing it will result in possible erratic behaving programs/libraries or they will not work at all). Also I should add there are alot more optimizations that gcc supports, not just processor or hardware specific ones.