public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rupert Wood <rup@kanat.pair.com>
To: Claudio Bley <bley@cs.uni-magdeburg.de>
Cc: GRE Spam Mail <gre_spam@anora.org>,  <bjensen@fastmail.fm>,
	 <gcc-help@gcc.gnu.org>
Subject: Re: undefined reference to `__errno_location(void)'
Date: Wed, 04 Sep 2002 09:20:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.30.0209041213580.31281-100000@kanat.pair.com> (raw)
In-Reply-To: <15734.11629.151771.241596@wh2-19.st.uni-magdeburg.de>

Claudio Bley wrote:

>     GRE> extern int errno;
>          ^^^^^^^^^^^^^^^^^
>
> Remove this line from your source. You get the error because errno is
> defined as a macro and the line is expanded to
>
> extern int (*__errno_location ());

Which, in that scope, is defined as a C++ symbol. Which is why it
didn't match the C __errno_location in libpthread.

The "d'oh" here is that the clue was in the title: it wouldn't have said
"(void)" if it was trying to match a C symbol because it wouldn't have
that information.

Oh well, we learn. (And good spot, Claudio!)

Rup.

  reply	other threads:[~2002-09-04 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <616BE6A276E3714788D2AC35C40CD18D7D2511@whale.softwire.co.uk>
2002-09-01 23:38 ` Rupert Wood
2002-09-02 10:06   ` GRE Spam Mail
2002-09-02 10:14     ` undefined reference to `__errno_location(void)'x Der Herr Hofrat
2002-09-02 10:53       ` GRE Spam Mail
2002-09-03 13:09         ` GRE Spam Mail
2002-09-04  0:28           ` bjorn rohde jensen
2002-09-04  7:51             ` undefined reference to `__errno_location(void)' GRE Spam Mail
2002-09-04  9:03               ` Claudio Bley
2002-09-04  9:20                 ` Rupert Wood [this message]
2002-09-04 17:27                   ` GRE Spam Mail
2002-09-02 10:07   ` GRE Spam Mail

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=Pine.BSF.4.30.0209041213580.31281-100000@kanat.pair.com \
    --to=rup@kanat.pair.com \
    --cc=bjensen@fastmail.fm \
    --cc=bley@cs.uni-magdeburg.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gre_spam@anora.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).