public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/24356] Unable to build gnatmake
Date: Sun, 23 Oct 2005 16:36:00 -0000	[thread overview]
Message-ID: <20051023163610.7454.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24356-6116@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]



------- Comment #2 from bugzilla-gcc at thewrittenword dot com  2005-10-23 16:36 -------
  $ nm /usr/lib/libcl.a | egrep 'U_IS_STUB_OR_CALLX|U_is_shared_pc'
U_IS_STUB_OR_CALLX  |          |undef |code   |
U_IS_STUB_OR_CALLX  |       572|extern|entry  |$CODE$
U_is_shared_pc      |          |undef |code   |
U_is_shared_pc      |       124|extern|entry  |$CODE$

There is one libcl patch for 11.23, PHSS_33405, but the defect
description doesn't indicate anything that will help this situation.

The only thing interesting in the release notes (but for Itanium):
  Itanium®-based Unwind Library (libunwind.so): Changes include a new set of
  “Unwind Express” APIs that perform stack unwinding considerably faster, and
  new header files <uwx.h> and <uwx_self.h>.

Release notes are available at:
  http://docs.hp.com/en/oshpux11iv2oe.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24356


  parent reply	other threads:[~2005-10-23 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 20:08 [Bug ada/24356] New: " bugzilla-gcc at thewrittenword dot com
2005-10-23  4:48 ` [Bug ada/24356] " danglin at gcc dot gnu dot org
2005-10-23 16:36 ` bugzilla-gcc at thewrittenword dot com [this message]
2006-01-06 22:18 ` laurent at guerby dot net
2006-01-06 22:32 ` bugzilla-gcc at thewrittenword dot com
2006-01-06 23:04 ` dave at hiauly1 dot hia dot nrc dot ca
2006-01-06 23:18 ` bugzilla-gcc at thewrittenword dot com
2006-01-07  0:10 ` dave at hiauly1 dot hia dot nrc dot ca
2006-01-26  8:02 ` laurent at guerby dot net
2007-04-30  9:49 ` charlet at gcc dot gnu dot org

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=20051023163610.7454.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).