public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rolf dot ebert dot gcc at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/19959] [4.0/4.1/4.2/4.3 Regression] Can't compile gnattools for the cross targets
Date: Thu, 04 Jan 2007 20:54:00 -0000 [thread overview]
Message-ID: <20070104205421.26040.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19959-283@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from rolf dot ebert dot gcc at gmx dot de 2007-01-04 20:54 -------
> Why does the '--disable-libada' switch disable gnattools-cross?
libada and gnattools-cross are not related, IMHO. I consider the dependancy as
a configure/Makefile bug.
The following patch removes the dependency of gnattols on libada.
--- gcc-4.2-20061226/configure~ Sun Dec 10 22:43:30 2006
+++ gcc-4.2-20061226/configure Thu Jan 4 10:15:19 2007
@@ -1136,9 +1136,6 @@
ENABLE_LIBADA=yes
fi
-if test "${ENABLE_LIBADA}" != "yes" ; then
- noconfigdirs="$noconfigdirs gnattools"
-fi
# Check whether --enable-libssp or --disable-libssp was given.
if test "${enable_libssp+set}" = set; then
If you configure now with --disable-libada, the cross-gnattols get properly
built. Tested on MinGW with gcc-4.2-20061226 targeting AVR.
Rolf
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19959
next prev parent reply other threads:[~2007-01-04 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19959-283@http.gcc.gnu.org/bugzilla/>
2005-10-30 22:13 ` [Bug ada/19959] [4.0/4.1 " pinskia at gcc dot gnu dot org
2006-02-28 20:37 ` [Bug ada/19959] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2006-05-25 2:44 ` mmitchel at gcc dot gnu dot org
2007-01-04 20:54 ` rolf dot ebert dot gcc at gmx dot de [this message]
2007-01-04 21:32 ` [Bug ada/19959] [4.0/4.1/4.2/4.3 " charlet at adacore dot com
2007-01-04 21:39 ` charlet at adacore dot com
2007-02-14 9:32 ` mmitchel at gcc dot gnu dot org
2008-05-12 23:36 ` [Bug ada/19959] [4.1/4.2/4.3/4.4 " 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=20070104205421.26040.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).