public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at mvista dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/12100] time.h:402: error: previous declaration of `clock'\revious declaration of `clock' Date: Fri, 29 Aug 2003 00:55:00 -0000 [thread overview] Message-ID: <20030829005548.19066.qmail@sources.redhat.com> (raw) In-Reply-To: <20030829004420.12100.danglin@gcc.gnu.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12100 ------- Additional Comments From drow at mvista dot com 2003-08-29 00:55 ------- Subject: Re: New: time.h:402: error: previous declaration of `clock'evious declaration of `clock' On Fri, Aug 29, 2003 at 12:44:25AM -0000, danglin at gcc dot gnu dot org wrote: > | /* System header to define __stub macros and hopefully few prototypes, > | which can conflict with char clock (); below. > | Prefer <limits.h> to <assert.h> if __STDC__ is defined, since > | <limits.h> exists even on freestanding compilers. */ > | #ifdef __STDC__ > | # include <limits.h> > | #else > | # include <assert.h> > | #endif > sys/time.h is included by limits.h when _HPUX_SOURCE is defined. Blast. I guess this is a bug in autoconf; you may wish to report it to the autoconf developers. In the meantime, it should be possible to avoid this by writing our own test for clock (and any other affected functions) which does not include <limits.h> if _HPUX_SOURCE is defined. It looks like that's only for the __stub macros, which are a glibcism anyway. Or you could copy/paste the definition of AC_LANG_FUNC_LINK_TRY(C) from c.m4 into libiberty/aclocal.m4 and fix it there. I just verified that that will generate appropriate checks.
next prev parent reply other threads:[~2003-08-29 0:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-29 0:44 [Bug bootstrap/12100] New: time.h:402: error: previous declaration of `clock'evious " danglin at gcc dot gnu dot org 2003-08-29 0:55 ` drow at mvista dot com [this message] 2003-08-29 13:20 ` [Bug bootstrap/12100] [3.4 Regression] " pinskia at gcc dot gnu dot org 2003-09-02 23:29 ` cvs-commit at gcc dot gnu dot org 2003-11-01 0:04 ` neroden at gcc dot gnu dot org 2003-11-01 0:56 ` drow at mvista dot com 2003-11-01 0:58 ` danglin at gcc dot gnu dot org
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=20030829005548.19066.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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).