Package: linux-kernel-headers
Version: 2.6.13+0rc3-2
Severity: serious
Justification: causes an FTBFS for dctc and dcgui
Including linux/sem.h results in the following error on mips and mipsel:
casals.debian.org$ echo '#include linux/sem.h' | cpp /dev/null
In file included from
On Mon, Oct 31, 2005 at 10:45:55AM +0100, Matej Vela wrote:
Package: linux-kernel-headers
Version: 2.6.13+0rc3-2
Severity: serious
Justification: causes an FTBFS for dctc and dcgui
Including linux/sem.h results in the following error on mips and mipsel:
casals.debian.org$ echo
Daniel Jacobowitz [EMAIL PROTECTED] writes:
On Mon, Oct 31, 2005 at 10:45:55AM +0100, Matej Vela wrote:
Including linux/sem.h results in the following error on mips and mipsel:
[...]
Why are you using this header from userspace? In general it's the
wrong choice.
The only advantage over
On Mon, Oct 31, 2005 at 05:51:45PM +0100, Matej Vela wrote:
Daniel Jacobowitz [EMAIL PROTECTED] writes:
On Mon, Oct 31, 2005 at 10:45:55AM +0100, Matej Vela wrote:
Including linux/sem.h results in the following error on mips and mipsel:
[...]
Why are you using this header from
tags 336577 normal
thanks
On Mon, Oct 31, 2005 at 10:45:55AM +0100, Matej Vela wrote:
Justification: causes an FTBFS for dctc and dcgui
This is not a sufficient justification for a RC bug against l-k-h.
Note that I explained in my bugs against dctc/dcgui the right fix for
it and did not file a
etch-ignore.
Bug#336577: linux-kernel-headers: linux/sem.h broken on mips, mipsel
There were no tags set.
Tags added:
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE
Frank Lichtenheld [EMAIL PROTECTED] writes:
On Mon, Oct 31, 2005 at 10:45:55AM +0100, Matej Vela wrote:
Justification: causes an FTBFS for dctc and dcgui
This is not a sufficient justification for a RC bug against l-k-h.
Note that I explained in my bugs against dctc/dcgui the right fix for
On Mon, Oct 31, 2005 at 06:32:21PM +0100, Matej Vela wrote:
Since Daniel Jacobowitz's reply hasn't reached the BTS either, here's
what he said:
In general, most of these headers are not intended or supported for
userspace use; so the correct thing to do is either to use the POSIX
8 matches
Mail list logo