public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at adacore dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/27936] [4.2 Regression] gnatbind fails to link on Tru64 UNIX
Date: Thu, 08 Jun 2006 08:17:00 -0000 [thread overview]
Message-ID: <20060608080352.29135.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27936-81@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from charlet at adacore dot com 2006-06-08 08:03 -------
Subject: Re: New: gnatbind fails to link on Tru64 UNIX
> Add ada/s-purexc.o to ada/Make-lang.in (GNATBIND_OBJS).
>
> If this is considered the correct fix, I'll submit a proper patch.
This shouldn't be needed at first sight, so this is likely not the right
fix.
Arno
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27936
next prev parent reply other threads:[~2006-06-08 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 18:04 [Bug ada/27936] New: " gcc-bugzilla at gcc dot gnu dot org
2006-06-07 18:07 ` [Bug ada/27936] [4.2 Regression] " ro at gcc dot gnu dot org
2006-06-08 8:17 ` charlet at adacore dot com [this message]
2006-06-08 17:26 ` ro at techfak dot uni-bielefeld dot de
2006-06-09 7:45 ` pinskia at gcc dot gnu dot org
2006-06-09 9:08 ` ebotcazou at gcc dot gnu dot org
2006-07-04 18:32 ` ro at gcc dot gnu dot org
2006-07-04 19:09 ` charlet at adacore dot com
2006-07-05 17:56 ` mmitchel at gcc dot gnu dot org
2006-10-01 21:50 ` falk at debian dot org
2006-10-03 16:13 ` ebotcazou at gcc dot gnu dot org
2006-11-17 15:10 ` [Bug ada/27936] [4.2/4.3 regression] gnatbind fails to link ebotcazou at gcc dot gnu dot org
2006-11-17 15:11 ` ebotcazou at gcc dot gnu dot org
2006-11-17 15:14 ` ebotcazou at gcc dot gnu dot org
2006-12-01 2:06 ` chaoyingfu 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=20060608080352.29135.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).