header clash in linux-libc-dev

[Peter Halicky]

Binary package hint: linux-libc-dev

The following little program fails to build on Ubuntu 9.04 x86_64:

    #include <linux/types.h>
    #include <stdint.h>

    int main() { return 0; }

gcc -o test test.c
In file included from test.c:2:
/usr/include/stdint.h:41: error: conflicting types for ‘int64_t’
/usr/include/linux/types.h:98: error: previous declaration of ‘int64_t’ was here
/usr/include/stdint.h:56: error: conflicting types for ‘uint64_t’
/usr/include/linux/types.h:96: error: previous declaration of ‘uint64_t’ was here

(actually, I found this when I was trying to build VDR 1.7.5)

This bug is also reported in Debian (#523424), but for a different version of linux-libc-dev (2.6.29) - in Ubuntu 9.04 currently there is 2.6.28-11.42.

[Luke Yelavich (themuso)]

Should be linux, not linux-ports, as linux-ports doesn't build any amd64 kernels.

[Peter Halicky (peto-halicky)]

Is there a chance this would ever be fixed in jaunty?

[Jeremy Foshee (jeremyfoshee)]

Hi phjr,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 366659

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Peter Halicky (peto-halicky)]

I don't use 9.04 anymore, in 9.10 this bug doesn't exist (I just checked). I suppose this bug can be closed.