public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Fred Fish <fnf@specifix.com>
To: glibc-bugs@sourceware.org
Cc: fnf@specifix.com
Subject: RE: Error when re-compiling libc
Date: Sat, 02 Dec 2006 16:10:00 -0000	[thread overview]
Message-ID: <200612020910.32488.fnf@specifix.com> (raw)


This problem can easily be reproduced with a stripped down copy of the preprocessed source:

    $ cat bug.i
    extern int __signbit (double __value) __attribute__ ((__nothrow__))
         __attribute__ ((__const__));

    extern __inline int
    __attribute__ ((__nothrow__)) __signbit (double __x)
    {
      __extension__ union { double __d; int __i[2]; } __u = { __d: __x };
      return __u.__i[1] < 0;
    }

    int
    __signbit (double x)
    {
    }
    $ gcc -c bug.i
    $ gcc -std=gnu99 -c bug.i
    bug.i:13: error: redefinition of ‘__signbit’
    bug.i:6: error: previous definition of ‘__signbit’ was here
    $

Note that the trigger is the -std=gnu99 option.  Not sure if this error is a bug
in glibc sources or in support for gnu99.

-Fred


             reply	other threads:[~2006-12-02 16:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 16:10 Fred Fish [this message]
2006-12-02 16:14 ` Luca
2006-12-02 17:11 ` Fred Fish
  -- strict thread matches above, loose matches on Subject: below --
2006-12-02  7:17 Luca

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=200612020910.32488.fnf@specifix.com \
    --to=fnf@specifix.com \
    --cc=glibc-bugs@sourceware.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: link
Be 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).