From: Albert Chin <gcc-help@mlists.thewrittenword.com>
To: gcc-help@gcc.gnu.org
Subject: pthread_mutex_init() with gcc-3.4.3 on Tru64 UNIX
Date: Fri, 08 Jul 2005 23:44:00 -0000 [thread overview]
Message-ID: <20050708234415.GH10913@mail1.thewrittenword.com> (raw)
$ uname -a
OSF1 [name] V4.0 878 alpha
$ uname -a
OSF1 [name] V5.1 732 alpha
$ cat mutex.c
#include <stdlib.h>
#include <pthread.h>
int
main (void) {
pthread_mutex_t lck;
if (pthread_mutex_init(&lck, 0) != 0)
exit (2);
if (pthread_mutex_lock(&lck) != 0)
exit (3);
if (pthread_mutex_unlock(&lck) != 0)
exit (4);
if (pthread_mutex_destroy(&lck) != 0)
exit (5);
exit (0);
}
$ cc mutex.c
ld:
Unresolved:
__pthread_mutex_init
__pthread_mutex_destroy
__pthread_mutex_lock
__pthread_mutex_unlock
$ cc -pthread mutex.c
$ ls -ld a.out
-rwxrwxr-x 1 china china 20288 Jul 8 18:40 a.out
$ nm a.out | grep pthread_mutex
__pthread_mutex_destroy | 0000000000000000 | U | 0000000000000008
__pthread_mutex_init | 0000000000000000 | U | 0000000000000008
__pthread_mutex_lock | 0000000000000000 | U | 0000000000000008
__pthread_mutex_unlock | 0000000000000000 | U | 0000000000000008
$ /opt/TWWfsw/gcc343/bin/gcc -v
Reading specs from
/opt/TWWfsw/gcc343/lib/gcc/alpha-dec-osf5.1/3.4.3/specs
Configured with: /opt/build/gcc-3.4.3/configure --enable-nls
--with-included-gettext --enable-shared --enable-threads
--host=alpha-dec-osf5.1 --with-local-prefix=/opt/TWWfsw/gcc343
--prefix=/opt/TWWfsw/gcc343
Thread model: posix
gcc version 3.4.3 (TWW)
$ /opt/TWWfsw/gcc343/bin/gcc mutex.c
$ ls -ld a.out
-rwxrwxr-x 1 china china 41072 Jul 8 18:40 a.out
$ nm a.out | grep pthread_mutex
__pthread_mutex_destroy | 0000004831844816 | T | 0000000000000008
__pthread_mutex_init | 0000004831844800 | T | 0000000000000008
__pthread_mutex_lock | 0000004831844640 | T | 0000000000000008
__pthread_mutex_trylock | 0000004831844656 | T | 0000000000000008
__pthread_mutex_unlock | 0000004831844672 | T | 0000000000000008
$ /opt/TWWfsw/gcc332/bin/gcc -v
Reading specs from
/opt/TWWfsw/gcc332/lib/gcc-lib/alphaev67-dec-osf5.1/3.3.2/specs
Configured with: /opt/build/gcc-3.3.2/configure --enable-nls
--with-included-gettext --enable-shared --enable-threads
--with-local-prefix=/opt/TWWfsw/gcc332 --prefix=/opt/TWWfsw/gcc332
Thread model: single
gcc version 3.3.2 (TWW)
$ /opt/TWWfsw/gcc332/bin/gcc mutex.c
__pthread_mutex_init
__pthread_mutex_lock
__pthread_mutex_unlock
__pthread_mutex_destroy
collect2: ld returned 1 exit status
So, why does /opt/TWWfsw/gcc343/bin/gcc resolve the pthread_mutex_*
symbols and cc does not? Should the GCC behavior mirror the cc
behavior?
--
albert chin (china@thewrittenword.com)
next reply other threads:[~2005-07-08 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 23:44 Albert Chin [this message]
2005-07-09 13:17 ` Ishwar Rattan
2005-07-09 15:03 ` Albert Chin
2005-07-09 17:27 ` Ishwar Rattan
2005-07-11 10:55 ` Albert Chin
2005-07-11 11:24 ` Eljay Love-Jensen
2005-07-11 14:22 ` Albert Chin
2005-07-11 15:13 ` Ishwar Rattan
2005-07-11 15:25 ` Albert Chin
2005-07-11 15:54 ` Ishwar Rattan
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=20050708234415.GH10913@mail1.thewrittenword.com \
--to=gcc-help@mlists.thewrittenword.com \
--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).