From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
/usr/include/linux/timex.h has a missing /* on line 56 - the comment just
starts without a comment-start delimiter. This causes a syntax error
for anything using this header.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.compile something with #include <linux/timex.h>
Actual Results: Syntax error:
/usr/include/linux/timex.h:56: error: syntax error before "and"
Expected Results: Correct compilation.
Valgrind 2.1.0 doesn't compile on Fedora Core 1 because of this bug.
Chronyd also doesn't compile on FC1 because of this bug...
Why is this bug still open? Thats 2 months for a typo in a header
file. (missing '/' for the comment field) While the fix is trivial,
I'm surprised no one has squashed this.
This was originally in glibc-kernheaders-2.4-8.36 (arjan)
That package is now know as glibc-headers-2.3.2-101.4 (jakub)
Please reassign to Jakub. (firstname.lastname@example.org)
Phil (aka Bryce)
*** Bug 110085 has been marked as a duplicate of this bug. ***
This seems to be fixed in glibc-kernheaders-2.4-8.43 (Raw Hide).
> This was originally in glibc-kernheaders-2.4-8.36 (arjan)
> That package is now know as glibc-headers-2.3.2-101.4 (jakub)
This is not so clear to me. Could you clarify ?
The incorrect file is /usr/include/linux/timex.h and belongs to
$ rpm -qf /usr/include/linux/timex.h
There is another timex.h file in /usr/include/sys that belongs to
# rpm -qf /usr/include/sys/timex.h
but these are very different files, and there is noyhing wrong with
Moreover, glibc-kernheaders are needed by glibc-headers.
$ rpm -e --test glibc-kernheaders
error: Failed dependencies:
kernel-headers is needed by (installed)
kernel-headers >= 2.2.1 is needed by (installed)
Created attachment 101030 [details]
Fixes missing start of comment line
[Argh, forgot to add my comment, sorry.]
Well, this is getting really old. Time to patch it and spin an update
glibc-kernheaders package I think.
Thanks for the bug report.
This bug doesn't seem to be present any more in current versions.