From: Riccardo-Maria Bianchi <Riccardo-Maria.Bianchi@cern.ch>
To: linux-kernel@vger.kernel.org
Subject: glibc compiling with kernel 2.5.70-bk17
Date: Thu, 19 Jun 2003 03:17:50 +0200 [thread overview]
Message-ID: <3EF10F3E.1090308@cern.ch> (raw)
Good morning,
I'm trying to compiling several version of the glibc but always during
the "make" I obtain these errors:
------------------------------------------ cut
-----------------------------------------------------------------------------------------------------
In file included from
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:29,
from ../sysdeps/unix/sysv/linux/sys/sysctl.h:28,
from ../include/sys/sysctl.h:2,
from ../sysdeps/unix/sysv/linux/dl-osinfo.h:21,
from ../sysdeps/unix/sysv/linux/init-first.c:32:
/lib/modules/2.5.70-bk15/build/include/linux/list.h:521:2: warning:
#warning "don't include kernel headers in userspace"
In file included from ../sysdeps/unix/sysv/linux/sys/sysctl.h:28,
from ../include/sys/sysctl.h:2,
from ../sysdeps/unix/sysv/linux/dl-osinfo.h:21,
from ../sysdeps/unix/sysv/linux/init-first.c:32:
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:39: warning: no
semicolon at end of struct or union
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:39: error: parse
error before '*' token
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:41: error: parse
error before '*' token
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:41: warning: type
defaults to `int' in declaration of `oldval'
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:41: warning: data
definition has no type or storage class
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:42: error: parse
error before '*' token
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:42: warning: type
defaults to `int' in declaration of `oldlenp'
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:42: warning: data
definition has no type or storage class
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:43: error: parse
error before '*' token
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:43: warning: type
defaults to `int' in declaration of `newval'
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:43: warning: data
definition has no type or storage class
/lib/modules/2.5.70-bk15/build/include/linux/sysctl.h:46: error: parse
error before '}' token
make[2]: *** [/home/nptl/glibc_2_3_1/build/csu/init-first.o] Error 1
make[2]: Leaving directory `/home/nptl/glibc_2_3_1/glibc-2.3.1/csu'
make[1]: *** [csu/subdir_lib] Error 2
make[1]: Leaving directory `/home/nptl/glibc_2_3_1/glibc-2.3.1'
make: *** [all] Error 2
---------------------------------------------------- cut
-------------------------------------------------------------------------------------
I have:
2.5.70-bk17 (even if the 2.5.70-bk15 is shown on the path)
gcc 3.3
binutils 2.13.92
Someone have an idea? :)
Thanks,
Riccardo-Maria Bianchi
next reply other threads:[~2003-06-19 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 1:17 Riccardo-Maria Bianchi [this message]
2003-06-19 1:23 ` glibc compiling with kernel 2.5.70-bk17 Kevin P. Fleming
2003-06-19 2:30 ` Chris Meadors
2003-06-19 6:16 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EF10F3E.1090308@cern.ch \
--to=riccardo-maria.bianchi@cern.ch \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox