public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dave.anglin@nrc-cnrc.gc.ca To: gcc-gnats@gcc.gnu.org Subject: ada/9953: Unsatisfied symbols: U_prep_frame_rec_for_unwind (code) Date: Tue, 04 Mar 2003 21:26:00 -0000 [thread overview] Message-ID: <20030304212438.18163.qmail@sources.redhat.com> (raw) >Number: 9953 >Category: ada >Synopsis: Unsatisfied symbols: U_prep_frame_rec_for_unwind (code) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Mar 04 21:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Dave Anglin >Release: 3.2 branch >Organization: >Environment: hppa1.1-hp-hpux10.20 >Description: ada in 3.3 branch fails to build with 3.2.3 (prerelease): mkdir -p ada/doctools cp ../../gcc/gcc/ada/xgnatug.adb ada/doctools cd ada/doctools && gnatmake -q xgnatug /usr/ccs/bin/ld: Unsatisfied symbols: U_prep_frame_rec_for_unwind (code) collect2: ld returned 1 exit status gnatlink: cannot call /opt/gnu/bin/gcc gnatmake: *** link failed. make[2]: *** [ada/doctools/xgnatug] Error 4 The undefined symbol is from gnatlib.a: # nm /opt/gnu/lib/gcc-lib/hppa1.1-hp-hpux10.20/3.2.3/adalib/libgnat.a ... s-traceb.o: 00000000 t $CODE$ 00000000 t $CODE$ 00000000 t $CODE$ 00000000 t $CODE$ 00000000 t $CODE$ 00000000 t $CODE$ 00000000 t L$text0000 00000000 t L$text_end0000 U U_IS_STUB_OR_CALLX U U_get_previous_frame_x U U_get_shLib_text_addr U U_get_shLib_unw_tbl U U_get_unwind_entry U U_get_unwind_table U U_init_frame_record U U_is_shared_pc U U_prep_frame_rec_for_unwind This is a regression. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-04 21:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-04 21:26 dave.anglin [this message] 2003-03-13 16:16 Olivier Hainque
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=20030304212438.18163.qmail@sources.redhat.com \ --to=dave.anglin@nrc-cnrc.gc.ca \ --cc=gcc-gnats@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).