From: George Georgalis <georgalis@gmail.com>
To: linux-kernel@vger.kernel.org, michal@feix.cz
Subject: Re: Conflicts in kernel 2.6 headers and {glibc,Xorg}
Date: Sun, 9 Jan 2005 11:06:54 -0500 [thread overview]
Message-ID: <d91f4d0c050109080638cf0987@mail.gmail.com> (raw)
In-Reply-To: <20050109110805.GA8688@irc.pl>
On Sun, 9 Jan 2005 12:08:05 +0100, Tomasz Torcz <zdzichu@irc.pl> wrote:
> On Sun, Jan 09, 2005 at 10:20:45AM +0100, Michal Feix wrote:
> > Hello evereyone!
> >
> > First, I'm not on kernel mailing list so please CC any replies to me.
> > Thank you.
> >
> > Yesterday I was recompiling my Linux from Scratch distribution for the
> > first time with Linux kernel 2.6.10 headers as a base for glibc. I've
> > found, that glibc (and XOrg later on too) won't compile, as there is a
> > conflict in certain functions or macros that glibc and Kernel headers
> > both define.
>
> Are you using proper kernel headers - from
> http://ep09.pld-linux.org/~mmazur/linux-libc-headers/ ?
I with 2.6.10 a problem came up that had me looking into this too.
Using gcc 3.3.3, my xfree86 is built from cvs release xf-4_4-branch.
When I tried 2.6.10, it built with no problems.
To the best of my knolege, xfree86 is not including any kernel
headers, my source is not where any package would know to look and
there don't seem to be any distro (woody) kernel header packages
installed. I could be wrong, but I don't know where they might be
found, or that I ever needed them for this xfree86 build.
The problem is running X, my display is littered with flashing bits,
as if the card is rendering some cpu register or bus in 2% of the
display.
02:00.0 VGA compatible controller: nVidia Corporation: Unknown device
01f0 (rev a3) (prog-if 00 [VGA])
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 16
Memory at ea000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Memory at e4000000 (32-bit, prefetchable) [size=512K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
Is this due to namespace collision? Do I have to take extra
precautions with 2.6.10?
// George
--
George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@galis.org
prev parent reply other threads:[~2005-01-09 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 9:20 Conflicts in kernel 2.6 headers and {glibc,Xorg} Michal Feix
2005-01-09 11:06 ` Chris Lingard
2005-01-09 11:08 ` Tomasz Torcz
2005-01-09 11:35 ` Michal Feix
2005-01-09 11:55 ` Tomasz Torcz
2005-01-09 12:25 ` DervishD
2005-01-09 12:31 ` Arjan van de Ven
2005-01-09 15:02 ` DervishD
2005-01-09 12:59 ` Jesper Juhl
2005-01-09 16:06 ` George Georgalis [this message]
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=d91f4d0c050109080638cf0987@mail.gmail.com \
--to=georgalis@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@feix.cz \
/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;
as well as URLs for NNTP newsgroup(s).