public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3992] New: stdlib/fmtmsg.c: missing stdint.h include Date: Wed, 07 Feb 2007 14:19:00 -0000 [thread overview] Message-ID: <20070207141850.3992.aurelien@aurel32.net> (raw) stdlib/fmtmsg.c is using a uint32_t type, but does not include stdint.h. This make the glibc to fail to build on Hurd. On other architectures, I guess stdint.h is included by one of the architecture specific headers. The patches below fixes the problem: Index: stdlib/fmtmsg.c =================================================================== RCS file: /cvs/glibc/libc/stdlib/fmtmsg.c,v retrieving revision 1.20 diff -u -d -p -r1.20 stdlib/fmtmsg.c --- stdlib/fmtmsg.c 15 May 2006 18:41:18 -0000 1.20 +++ stdlib/fmtmsg.c 7 Feb 2007 14:06:37 -0000 @@ -20,6 +20,7 @@ #include <fmtmsg.h> #include <bits/libc-lock.h> #include <stdio.h> +#include <stdint.h> #include <stdlib.h> #include <string.h> #include <sys/syslog.h> -- Summary: stdlib/fmtmsg.c: missing stdint.h include Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: aurelien at aurel32 dot net CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i686-unknown-gnu0.3 GCC host triplet: i686-unknown-gnu0.3 GCC target triplet: i686-unknown-gnu0.3 http://sourceware.org/bugzilla/show_bug.cgi?id=3992 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2007-02-07 14:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-07 14:19 aurelien at aurel32 dot net [this message] 2007-02-07 17:00 ` [Bug libc/3992] " drepper at redhat dot com
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=20070207141850.3992.aurelien@aurel32.net \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).