public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/9953: Unsatisfied symbols: U_prep_frame_rec_for_unwind (c
Date: Mon, 17 Mar 2003 20:16:00 -0000 [thread overview]
Message-ID: <20030317201602.18191.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/9953; it has been noted by GNATS.
From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: Olivier Hainque <hainque@ACT-Europe.FR>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
dave.anglin@nrc-cnrc.gc.ca, gcc-gnats@gcc.gnu.org, bosch@gnat.com,
charlet@ACT-Europe.FR
Subject: Re: ada/9953: Unsatisfied symbols: U_prep_frame_rec_for_unwind (c
Date: Mon, 17 Mar 2003 21:10:46 +0100
> Oh, strange. We did have it under 10.20, which is why the Makefile includes
> a setup for a dual build.
>
> > ../../xgcc [...] -o ../../gnatmake /usr/lib/libcl.a -lpthread [...]
Actually no, HP-UX 10.20 only has DCE threads.
What we did was to build two GNAT run time (one for DCE, one for pthread),
with the idea that: under 10.20, only the DCE run time can be used;
under 11.00, both could be used.
We now no longer build dce under 11.00, as this library caused too many
problems (both in terms of posix compliance and reliability).
Arno
next reply other threads:[~2003-03-17 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 20:16 Arnaud Charlet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-25 9:57 Olivier Hainque
2003-03-20 8:36 Olivier Hainque
2003-03-20 2:06 John David Anglin
2003-03-18 16:16 John David Anglin
2003-03-18 16:16 John David Anglin
2003-03-18 15:46 Olivier Hainque
2003-03-18 14:46 Arnaud Charlet
2003-03-18 13:36 Olivier Hainque
2003-03-17 17:56 John David Anglin
2003-03-17 17:26 Olivier Hainque
2003-03-17 16:16 John David Anglin
2003-03-14 18:36 John David Anglin
2003-03-14 9:16 Olivier Hainque
2003-03-14 3:16 John David Anglin
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=20030317201602.18191.qmail@sources.redhat.com \
--to=charlet@act-europe.fr \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).