public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: ljrittle@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/3314: --enable-threads does not seem to be working for HP-UX 11.00 Date: Tue, 15 Jan 2002 08:46:00 -0000 [thread overview] Message-ID: <20020115164602.24626.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/3314; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: harri.pasanen@trema.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, jdonner@schedsys.com, ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org Cc: Subject: Re: bootstrap/3314: --enable-threads does not seem to be working for HP-UX 11.00 Date: Tue, 15 Jan 2002 11:39:24 -0500 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3314 Information added from PR 5383 which is a duplicate of this: http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3314 --enable-threads configure option does not abort on HP-UX 11, and consequently creates a badly configured compiler. ============================================================================================================ > jpararas@tango ~ >gcc -v > Reading specs from /usr/local/gcc303/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.0.3/specs > Configured with: ../gcc-3.0.3/configure --prefix=/usr/local/gcc303 --with-gnu-as --with-as=/usr/local/bin/as --with-ld=/usr/ccs/bin/ld --enable-threads=posix > Thread model: posix > gcc version 3.0.3 > > > This was compiled with thread support. However, a simple > Hello World app, Foo.cpp fails to link, as follows: > > jpararas@tango ~ >g++ Foo.cpp > /usr/ccs/bin/ld: Unsatisfied symbols: > pthread_once (code) > pthread_key_create (code) > pthread_setspecific (code) > pthread_mutex_unlock (code) > pthread_getspecific (code) > pthread_mutex_lock (code) > collect2: ld returned 1 exit status > > > And even: > > jpararas@tango ~ >g++ -threads Foo.cpp > /usr/ccs/bin/ld: Unsatisfied symbols: > pthread_key_create (code) > collect2: ld returned 1 exit status > > A precompiled, single-thread gcc 3.0.1 (binary from HP) > > jpararas@tango ~ >gcc -v > Reading specs from /opt/gcc/lib/gcc-lib/hppa2.0n-hp-hpux11.00/3.0.1/specs > Configured with: ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure : (reconfigured) ./configure > Thread model: single > gcc version 3.0.1 > > compiles & runs fine: > jpararas@tango ~ >g++ Foo.cpp > jpararas@tango ~ >./a.out > Hello world > >
next reply other threads:[~2002-01-15 16:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-15 8:46 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 8:16 Dara Hazeghi 2002-02-18 15:01 ljrittle 2002-01-14 19:16 Craig Rodrigues 2001-06-21 14:34 ljrittle 2001-06-21 1:36 harri.pasanen
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=20020115164602.24626.qmail@sources.redhat.com \ --to=rodrigc@mediaone.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=ljrittle@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: linkBe 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).