public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: <guerby@acm.org>
To: gcc@gcc.gnu.org
Subject: [Ada] Q about building cross gnatlib
Date: Fri, 30 Nov 2001 13:40:00 -0000	[thread overview]
Message-ID: <200111302134.fAULY2c00478@ulmo.localdomain> (raw)
Message-ID: <20011130134000.iHEhGkdycDvmElGS53bBia3CFaa65L27BKovZzj7BWc@z> (raw)

I'm trying to build GCC cross sparc-rtems from my i686-linux. After
installing the apropriate cross binutils, I succeed in building the
cross compiler then newlib thanks to Joel Sherrill detailed
instructions :).

I'm wondering wether the current ada/Makefile.in supports building
gnatlib in a cross setup, unless I'm missing something obvious I see
no way it can build the C part of the Ada RTS using the target newlib
since there seem to be no obvious place to specify where to find the
target includes in the current invocation:

gnatlib: ../stamp-gnatlib1 ../stamp-gnatlib2
#	../xgcc -B../ -dD -E ../tconfig.h $(INCLUDES) > rts/tconfig.h
	$(MAKE) -C rts CC="../../xgcc -B../../" \
	        INCLUDES="$(INCLUDES_FOR_SUBDIR) -I./../.." \
                CFLAGS="$(GNATLIBCFLAGS) $(TARGET_LIBGCC2_CFLAGS) -DIN_RTS" \
		ADA_CFLAGS="$(GNATLIBCFLAGS)" \
		srcdir=$(fsrcdir) \
	        -f ../Makefile $(LIBGNAT_OBJS)

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.)

-- 
Laurent Guerby <guerby@acm.org>

             reply	other threads:[~2001-11-30 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 16:27 guerby [this message]
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
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=200111302134.fAULY2c00478@ulmo.localdomain \
    --to=guerby@acm.org \
    --cc=gcc@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).