Skip to contentSkip to conversation

Development tree, PLEASE?

DISCUSSION Chuck Ebbert 3 participants 4 messages Mar 14, 2006 – Mar 16, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 5 lines · Dave Jones

-rw-r--r-- 1 davej davej 1686 Dec 15 23:31 linux-2.6-build-userspace-headers-warning.patch

adds a #error to includes if __KERNEL__ isn't being used (We want people to use the headers from our glibc-kernheaders package, not from the kernel soucre).

Red Hat's headers are way out of date.

Just try compiling this using FC4's latest kernheaders:

        ptrace(PTRACE_SETOPTIONS, child, NULL, PTRACE_O_TRACEFORK);

PTRACE_O_TRACEFORK is undefined.

No wonder people use kernel headers despite being told not to.

Signature · 2 lines
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
#1 lore raw
Quoted 10 lines · Chuck Ebbert

In-Reply-To: <[email protected]>

Quoted 5 lines · Dave Jones

-rw-r--r-- 1 davej davej 1686 Dec 15 23:31 linux-2.6-build-userspace-headers-warning.patch

adds a #error to includes if __KERNEL__ isn't being used (We want people to use the headers from our glibc-kernheaders package, not from the kernel soucre).

Quoted 7 lines

Red Hat's headers are way out of date.

Just try compiling this using FC4's latest kernheaders:

        ptrace(PTRACE_SETOPTIONS, child, NULL, PTRACE_O_TRACEFORK);

PTRACE_O_TRACEFORK is undefined.

what is the bugzilla number for this?

#2 lore raw
Quoted 10 lines
Quoted 10 lines · Dave Jones
Quoted 6 lines

-rw-r--r-- 1 davej davej 1686 Dec 15 23:31 linux-2.6-build-userspace-headers-warning.patch

adds a #error to includes if __KERNEL__ isn't being used (We want people to use the headers from our glibc-kernheaders package, not from the kernel soucre).

Red Hat's headers are way out of date.

Quoted 9 lines
Quoted 5 lines

Just try compiling this using FC4's latest kernheaders:

        ptrace(PTRACE_SETOPTIONS, child, NULL, PTRACE_O_TRACEFORK);

PTRACE_O_TRACEFORK is undefined.

what is the bugzilla number for this?

I created one sometime ago.
Different origin, same problem.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168045

Jan Engelhardt