From: Arjan van de Ven <arjanv@redhat.com>
To: Martin Zwickel <martin.zwickel@technotrend.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-t1-ac2: unable to compile glibc 2.3.2
Date: 17 Jul 2003 12:15:31 +0200 [thread overview]
Message-ID: <1058436931.5778.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030717114548.5f5d506d.martin.zwickel@technotrend.de>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Thu, 2003-07-17 at 11:45, Martin Zwickel wrote:
> Hi there!
>
> I just tried to update my glibc to 2.3.2 and saw that glibc can't compile
> because of linux/sysctl.h.
>
> I added the line "#include <linux/compiler.h>" to sysctl.h.
> (since sysctl needs the __user)
>
> So someone forgot the line, or did I miss something?
you're probably better off using not-the-kernel headers for building
glibc. eg on a RHL distro it's glibc-kernheaders package, other distros
have different package names for these files.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-17 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 9:45 Martin Zwickel
2003-07-17 10:15 ` Arjan van de Ven [this message]
2003-07-17 17:34 ` Chris Meadors
2003-07-17 12:12 ` Martin Schlemmer
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=1058436931.5778.2.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.zwickel@technotrend.de \
/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
all inboxes | Powered by JetHome®