From: Jeffrey Holle <jeff.holle@verizon.net>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem with gcc v3.4.3?
Date: Fri, 26 Nov 2004 07:09:00 -0000 [thread overview]
Message-ID: <co6krr$dme$1@sea.gmane.org> (raw)
In-Reply-To: <co69li$t9l$1@sea.gmane.org>
Answered my own question.
I needed to link to pthread in these applications.
The link error confused me in that I thought pthread was being linked to
and was the component making the undefined reference.
Guess not....
Jeffrey Holle wrote:
> I'm running Mandrake linux v10.0 offical release.
>
> I've developed a problem recently in linking cpp applications that use
> shared libraries.
>
> This may have been caused by:
> a. upgrading to gcc v3.4.3 from v3.4.2, or
> b. rebuilding my linux system.
>
> In multiple applications, I get:
> /lib/tls/libpthread.so.0: undefined reference to `errno@GLIBC_PRIVATE'
> /lib/tls/libpthread.so.0: undefined reference to
> `__libc_dl_error_tsd@GLIBC_PRIVATE'
>
> In the past, I didn't need to explicitly link to libc.so, I assume that
> it auto-linked as needed. Now it doesn't matter if I link to it or not.
>
> Can someone point of the cause of this error?
>
>
prev parent reply other threads:[~2004-11-26 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 3:58 Jeffrey Holle
2004-11-26 7:09 ` Jeffrey Holle [this message]
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='co6krr$dme$1@sea.gmane.org' \
--to=jeff.holle@verizon.net \
--cc=gcc-help@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: 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).