From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: guerby@acm.org
Cc: gcc@gcc.gnu.org
Subject: Re: [Ada] Q about building cross gnatlib
Date: Sat, 01 Dec 2001 13:04:00 -0000 [thread overview]
Message-ID: <20011201220406.B28503@dublin.int.act-europe.fr> (raw)
In-Reply-To: <200111302134.fAULY2c00478@ulmo.localdomain>; from guerby@acm.org on Fri, Nov 30, 2001 at 10:34:02PM +0100
> Does the ACT tree (when building for VxWorks for example) have
> specific patches to the Makefile to handle the situation? If they're
We do not have anything special. It works because xgcc will look for the
includes under <prefix>/<target>/include, at least that's the way it works
with GCC 2.8.1.
Arno
next prev parent reply other threads:[~2001-12-01 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 16:27 guerby
2001-11-23 17:38 ` Geert Bosch
2001-11-23 21:59 ` guerby
2001-11-30 15:07 ` guerby
2001-11-23 23:19 ` Joel Sherrill
2001-11-30 15:30 ` Joel Sherrill
2001-11-30 14:30 ` Geert Bosch
2001-11-30 13:40 ` guerby
2001-12-01 13:04 ` Arnaud Charlet [this message]
2001-12-01 13:42 ` guerby
2001-12-02 8:29 ` Andreas Schwab
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=20011201220406.B28503@dublin.int.act-europe.fr \
--to=charlet@act-europe.fr \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).