public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> 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 16:16:00 -0000 [thread overview] Message-ID: <20030317161602.4896.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/9953; it has been noted by GNATS. From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: hainque@ACT-Europe.FR (Olivier Hainque) Cc: dave.anglin@nrc-cnrc.gc.ca, gcc-gnats@gcc.gnu.org, hainque@ACT-Europe.FR, bosch@gnat.com Subject: Re: ada/9953: Unsatisfied symbols: U_prep_frame_rec_for_unwind (c Date: Mon, 17 Mar 2003 11:15:12 -0500 (EST) > dave.anglin@nrc-cnrc.gc.ca wrote: > > cd ada/doctools && gnatmake -q xgnatug > > /usr/ccs/bin/ld: Unsatisfied symbols: > > U_prep_frame_rec_for_unwind (code) > > As indicated on other channels, this is because the GNAT run-time library > references functions from the system unwinding library (for call-chain > computation purposes), and this specific one is not provided on HPUX 10. > > The patch below should fix this. [...] > + > TGT_LIB = /usr/lib/libcl.a -lpthread > THREADSLIB = -lpthread -lc_r > SYMLIB = -laddr2line -lbfd $(INTLLIBS) We still have a problem. The first problem is fixed but libpthread (posix threads) isn't available under 10.20: ../../xgcc -B../../ -DIN_GCC `echo -g -W -Wall -Wwrite-strings -Wstrict-protot ypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long |sed -e 's/-pe dantic//g' -e 's/-Wtraditional//g'` -o ../../gnatmake b_gnatm.o ali.o ali-util .o alloc.o atree.o binderr.o butil.o casing.o csets.o debug.o einfo.o elists.o e rrout.o fmap.o fname.o fname-uf.o fname-sf.o gnatmake.o gnatvsn.o hostparm.o kru nch.o lib.o make.o makeusg.o mlib.o mlib-fil.o mlib-prj.o mlib-tgt.o mlib-utl.o namet.o nlists.o opt.o osint.o osint-m.o output.o prj.o prj-attr.o prj-com.o prj -dect.o prj-env.o prj-ext.o prj-nmsc.o prj-pars.o prj-part.o prj-proc.o prj-strt .o prj-tree.o prj-util.o rident.o scans.o scn.o sdefault.o sfn_scan.o sinfo.o si nfo-cn.o sinput.o sinput-l.o sinput-p.o snames.o stand.o stringt.o style.o style sw.o validsw.o switch.o switch-m.o switch-c.o table.o targparm.o tree_io.o types .o uintp.o uname.o urealp.o usage.o widechar.o \ ../../prefix.o ../../version.o ../rts/libgnat.a ../../../libiberty/libiberty.a /usr/lib/libcl.a -lpthread /usr/ccs/bin/ld: Can't find library for -lpthread Dave -- J. David Anglin dave.anglin@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next reply other threads:[~2003-03-17 16:16 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-17 16:16 John David Anglin [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 20:16 Arnaud Charlet 2003-03-17 17:56 John David Anglin 2003-03-17 17:26 Olivier Hainque 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=20030317161602.4896.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --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: 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).