From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: Geert Bosch <bosch@gnat.com>
Cc: guerby@acm.org, gcc@gcc.gnu.org
Subject: Re: [Ada] Q about building cross gnatlib
Date: Fri, 23 Nov 2001 23:19:00 -0000 [thread overview]
Message-ID: <3C0809EA.E8B657BE@OARcorp.com> (raw)
In-Reply-To: <E64405F9-E5E1-11D5-A27C-00039344BF4A@gnat.com>
Geert Bosch wrote:
>
> On Friday, November 30, 2001, at 04:34 , <guerby@acm.org> wrote:
>
> > Does the ACT tree (when building for VxWorks for example) have
> > specific patches to the Makefile to handle the situation? If they're
> > not completely ready for the FSF tree yet, could someone send them to
> > me, it would help a lot my efforts to setup a cross testing
> > environment for the various RTEMS targets. (Right now I'm kluding
> > around
> > the Makefile in random places and not completely successful yet.)
>
> There are no specific patches, and we do nightly cross-builds of GNAT on
> for a whole set of hosts/targets. This is with the old gcc 2.8.1
> setup though,
> so any differences should be due to the differences between the current
> setup and the old one (which you know well).
GNAT/RTEMS built fine for 3.13p. The problem seems to be centered on
the Ada rts makefile not using the FLAGS_FOR_TARGET defined in the top
level Makefile. This lets you see newlib's include and include/sys
directories.
It may also be necessary to use LIBGCC2_FLAGS_FOR_TARGET (sp?) as well.
I know this is how you find the RTEMS limits.h down inside newlib.
> -Geert
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
WARNING: multiple messages have this Message-ID
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: Geert Bosch <bosch@gnat.com>
Cc: guerby@acm.org, gcc@gcc.gnu.org
Subject: Re: [Ada] Q about building cross gnatlib
Date: Fri, 30 Nov 2001 15:30:00 -0000 [thread overview]
Message-ID: <3C0809EA.E8B657BE@OARcorp.com> (raw)
Message-ID: <20011130153000._5KiPkGlwGmlC7gNSuqxTLbrZUyXZNi2_AZP1WSYPxc@z> (raw)
In-Reply-To: <E64405F9-E5E1-11D5-A27C-00039344BF4A@gnat.com>
Geert Bosch wrote:
>
> On Friday, November 30, 2001, at 04:34 , <guerby@acm.org> wrote:
>
> > Does the ACT tree (when building for VxWorks for example) have
> > specific patches to the Makefile to handle the situation? If they're
> > not completely ready for the FSF tree yet, could someone send them to
> > me, it would help a lot my efforts to setup a cross testing
> > environment for the various RTEMS targets. (Right now I'm kluding
> > around
> > the Makefile in random places and not completely successful yet.)
>
> There are no specific patches, and we do nightly cross-builds of GNAT on
> for a whole set of hosts/targets. This is with the old gcc 2.8.1
> setup though,
> so any differences should be due to the differences between the current
> setup and the old one (which you know well).
GNAT/RTEMS built fine for 3.13p. The problem seems to be centered on
the Ada rts makefile not using the FLAGS_FOR_TARGET defined in the top
level Makefile. This lets you see newlib's include and include/sys
directories.
It may also be necessary to use LIBGCC2_FLAGS_FOR_TARGET (sp?) as well.
I know this is how you find the RTEMS limits.h down inside newlib.
> -Geert
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2001-11-30 23:30 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 [this message]
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
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=3C0809EA.E8B657BE@OARcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=bosch@gnat.com \
--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).