public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/6852] gnatlib fails to build with newlib because it doesn't set up the include path
Date: Mon, 12 Dec 2005 11:27:00 -0000 [thread overview]
Message-ID: <20051212112741.12249.qmail@sourceware.org> (raw)
In-Reply-To: <bug-6852-288@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from charlet at gcc dot gnu dot org 2005-12-12 11:27 -------
This PR should now be fixed, AFAIK.
Fixed by:
<<
libada:
2005-12-05 Paolo Bonzini <bonzini@gnu.org>
* Makefile.in (FLAGS_TO_PASS): Add GCC_FOR_TARGET.
gcc/ada:
2005-12-05 Paolo Bonzini <bonzini@gnu.org>
* Makefile.in (gnatlib): Fix regex, using \. instead of . when
a period is meant.
>>
--
charlet at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6852
next parent reply other threads:[~2005-12-12 11:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6852-288@http.gcc.gnu.org/bugzilla/>
2005-12-12 11:27 ` charlet at gcc dot gnu dot org [this message]
[not found] <20020528182601.6852.geoffk@redhat.com>
2003-05-27 6:07 ` dhazeghi@yahoo.com
2003-05-27 14:55 ` pinskia@physics.uc.edu
2003-06-02 3:08 ` dhazeghi@yahoo.com
2003-06-02 16:44 ` geoffk@geoffk.org
2003-06-16 18:55 ` dhazeghi@yahoo.com
2003-07-14 3:52 ` dhazeghi at yahoo dot com
2003-07-19 17:43 ` pinskia at physics dot uc dot edu
2003-10-21 17:04 ` charlet at gcc dot gnu dot org
2005-03-15 16:11 ` cvs-commit at gcc dot gnu dot org
2005-03-15 16:32 ` charlet at gcc dot gnu dot org
2005-04-29 7:33 ` 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=20051212112741.12249.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).