Menu
▾
▴
devil-linux-develop
|
From: <hzu...@ra...> - 2004-01-13 13:43:49
|
On 01/13/2004 07:46:06 AM Oliver Jehle wrote: >the same at my run... i'm not sure, but i think, it applies after >configure the glibc and build up the system dependencies.. > >will look on it after i finished compile all packages with 2.6 :-) >hopefully this afternoon happens !! I guess you didn't start with a fresh lfssystem, or? The glibc compile fails here, I guess because of a missing version.h in the kernel include dir. I'll keep you posted. Heiko |
|
From: <hzu...@ra...> - 2004-01-13 14:04:28
|
On 01/13/2004 08:42:36 AM Heiko Zuerker wrote: >On 01/13/2004 07:46:06 AM Oliver Jehle wrote: >>the same at my run... i'm not sure, but i think, it applies after >>configure the glibc and build up the system dependencies.. >> >>will look on it after i finished compile all packages with 2.6 :-) >>hopefully this afternoon happens !! > >I guess you didn't start with a fresh lfssystem, or? >The glibc compile fails here, I guess because of a missing version.h in >the kernel include dir. Yes that was the problem, the fix is in CVS. 'uname' now always reports the kernel version we use in the source tree. Heiko |
|
From: Oliver J. <oli...@mo...> - 2004-01-13 13:47:56
|
thats correct.. the missing version.h... of 2.6.. i've copied the one from the host system :-(, in the begining and forgot to do a proper fix... sooo.. there is another bug to fix !!! will look, when 2.6 will write this include file. and make a patch for the glibc procedure.. . On Tue, 2004-01-13 at 14:42, hzu...@ra... wrote: > On 01/13/2004 07:46:06 AM Oliver Jehle wrote: > >the same at my run... i'm not sure, but i think, it applies after > >configure the glibc and build up the system dependencies.. > > > >will look on it after i finished compile all packages with 2.6 :-) > >hopefully this afternoon happens !! > > I guess you didn't start with a fresh lfssystem, or? > The glibc compile fails here, I guess because of a missing version.h in the > kernel include dir. > > I'll keep you posted. > > Heiko > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
|
From: Oliver J. <oli...@mo...> - 2004-01-13 14:05:59
Attachments:
glibc_version_h.diff
|
perhaps this will help ???? works for me.... On Tue, 2004-01-13 at 14:42, hzu...@ra... wrote: > On 01/13/2004 07:46:06 AM Oliver Jehle wrote: > >the same at my run... i'm not sure, but i think, it applies after > >configure the glibc and build up the system dependencies.. > > > >will look on it after i finished compile all packages with 2.6 :-) > >hopefully this afternoon happens !! > > I guess you didn't start with a fresh lfssystem, or? > The glibc compile fails here, I guess because of a missing version.h in the > kernel include dir. > > I'll keep you posted. > > Heiko > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
|
From: Diego T. <dt...@co...> - 2004-01-14 22:42:00
|
On Tue, Jan 13, 2004 at 03:05:46PM +0100, Oliver Jehle wrote: > > I guess you didn't start with a fresh lfssystem, or? > > The glibc compile fails here, I guess because of a missing version.h in the > > kernel include dir. are we/you/us aware of this? (fresh cvs/install/ftp'ed one hour ago) /usr/include/linux/list.h:594:2: warning: #warning "don't include kernel headers in userspace" mkdosfs.c: In function `do_check': mkdosfs.c:399: warning: implicit declaration of function `llseek' gcc mkdosfs.o -o mkdosfs mkdosfs.o(.text+0x200): In function `do_check': : warning: the `llseek' function may be dangerous; use `lseek64' instead. make[2]: Leaving directory `/data/build/tmp/dosfstools-2.8/mkdosfs' make -C dosfsck all make[2]: Entering directory `/data/build/tmp/dosfstools-2.8/dosfsck' gcc -c -O2 -fomit-frame-pointer -Wall boot.c boot.c: In function `read_boot': boot.c:324: error: `MSDOS_FAT12' undeclared (first use in this function) boot.c:324: error: (Each undeclared identifier is reported only once boot.c:324: error: for each function it appears in.) make[2]: *** [boot.o] Error 1 make[2]: Leaving directory `/data/build/tmp/dosfstools-2.8/dosfsck' make[1]: *** [all] Error 2 make[1]: Leaving directory `/data/build/tmp/dosfstools-2.8' ERROR /data/build/scripts/dosfstools build failed -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-01-14 22:56:16
|
Diego Torres wrote: > On Tue, Jan 13, 2004 at 03:05:46PM +0100, Oliver Jehle wrote: > > >>>I guess you didn't start with a fresh lfssystem, or? >>>The glibc compile fails here, I guess because of a missing version.h in the >>>kernel include dir. > > > are we/you/us aware of this? (fresh cvs/install/ftp'ed one hour ago) > > /usr/include/linux/list.h:594:2: warning: #warning "don't include kernel headers in userspace" > mkdosfs.c: In function `do_check': > mkdosfs.c:399: warning: implicit declaration of function `llseek' > gcc mkdosfs.o -o mkdosfs > mkdosfs.o(.text+0x200): In function `do_check': > : warning: the `llseek' function may be dangerous; use `lseek64' instead. > make[2]: Leaving directory `/data/build/tmp/dosfstools-2.8/mkdosfs' > make -C dosfsck all > make[2]: Entering directory `/data/build/tmp/dosfstools-2.8/dosfsck' > gcc -c -O2 -fomit-frame-pointer -Wall boot.c > boot.c: In function `read_boot': > boot.c:324: error: `MSDOS_FAT12' undeclared (first use in this function) > boot.c:324: error: (Each undeclared identifier is reported only once > boot.c:324: error: for each function it appears in.) > make[2]: *** [boot.o] Error 1 > make[2]: Leaving directory `/data/build/tmp/dosfstools-2.8/dosfsck' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/data/build/tmp/dosfstools-2.8' > ERROR > /data/build/scripts/dosfstools build failed > Actually we didn't do any changes to dosfstools. Did you also start with a new lfssystem? Heiko |
|
From: Diego T. <dt...@co...> - 2004-01-14 23:45:31
|
On Wed, Jan 14, 2004 at 05:53:47PM -0500, Heiko Zuerker wrote: > >ERROR > >/data/build/scripts/dosfstools build failed > > > > Actually we didn't do any changes to dosfstools. > Did you also start with a new lfssystem? yes, everything was fresh and new :) i've a box only for compiling versions from cvs, and i've configured it to test the new 2.6 :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dtorres at anthalia dot org - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2004-01-14 23:56:18
|
Diego Torres wrote: > On Wed, Jan 14, 2004 at 05:53:47PM -0500, Heiko Zuerker wrote: > >>>ERROR >>>/data/build/scripts/dosfstools build failed >>> >> >>Actually we didn't do any changes to dosfstools. >>Did you also start with a new lfssystem? > > > yes, everything was fresh and new :) i've a box only for compiling versions from cvs, and i've configured it to test the new 2.6 :) Aaaah 2.6..... Right now it only works if you do NOT select anything in menuconfig. ;-) Don't forgett that we're in a very early stage. I guess it will take a few weeks until we'll have a usable version. Heiko |
|
From: Oliver J. <oli...@mo...> - 2004-01-15 05:45:38
|
On Wed, 2004-01-14 at 23:40, Diego Torres wrote: > are we/you/us aware of this? (fresh cvs/install/ftp'ed one hour ago) > > /usr/include/linux/list.h:594:2: warning: #warning "don't include kernel headers in userspace" the kernel headers have such warning in 2.6, because, normally userspaces programms not use directly the kernel headers... > mkdosfs.c: In function `do_check': > mkdosfs.c:399: warning: implicit declaration of function `llseek' > gcc mkdosfs.o -o mkdosfs > mkdosfs.o(.text+0x200): In function `do_check': > : warning: the `llseek' function may be dangerous; use `lseek64' instead. > make[2]: Leaving directory `/data/build/tmp/dosfstools-2.8/mkdosfs' > make -C dosfsck all > make[2]: Entering directory `/data/build/tmp/dosfstools-2.8/dosfsck' > gcc -c -O2 -fomit-frame-pointer -Wall boot.c > boot.c: In function `read_boot': > boot.c:324: error: `MSDOS_FAT12' undeclared (first use in this function) > boot.c:324: error: (Each undeclared identifier is reported only once > boot.c:324: error: for each function it appears in.) > make[2]: *** [boot.o] Error 1 > make[2]: Leaving directory `/data/build/tmp/dosfstools-2.8/dosfsck' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/data/build/tmp/dosfstools-2.8' > ERROR > /data/build/scripts/dosfstools build failed take the latest version from cvs, should compile... |
