From: "Rupert Wood" <me@rupey.net>
To: "'GRE Spam Mail'" <gre_spam@anora.org>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: undefined reference to `__errno_location(void)'
Date: Sun, 01 Sep 2002 23:38:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D561765@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D7D2511@whale.softwire.co.uk>
Gordon Ellsworth wrote:
> /home/muvie/muvie/src/socket_class.c:211: undefined reference to
> `__errno_location(void)'
:
> And when you link make sure to add -lpthread,
> since the symbol for errno_location is defined
> in the libpthread library on Linux.
:
> I tried this, but it did not get rid of the problem.
Can I confirm that you tried the '-lpthread' in addition to the #include
in the PR comment? If so, can you confirm that you've got a libpthread.a
or libpthread.so in /lib or /usr/lib and that it contains the symbol
__errno_location?
As you said you haven't upgraded, the system *ought* to work as shipped.
But it's possible (albeit unlikely) that your C library was not build
with threading support or that you're missing the ptherad library -
maybe you need to install it as a separate package?
Good luck,
Rup.
next parent reply other threads:[~2002-09-02 6:38 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 [this message]
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
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=616BE6A276E3714788D2AC35C40CD18D561765@whale.softwire.co.uk \
--to=me@rupey.net \
--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).