From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28430 invoked by alias); 30 Nov 2001 21:40:27 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 28336 invoked from network); 30 Nov 2001 21:40:12 -0000 Received: from unknown (HELO mahonia.wanadoo.fr) (193.252.19.58) by hostedprojects.ges.redhat.com with SMTP; 30 Nov 2001 21:40:12 -0000 Received: from ulmo.localdomain (193.251.48.242) by mahonia.wanadoo.fr; 30 Nov 2001 22:40:11 +0100 Received: (from guerby@localhost) by ulmo.localdomain (8.11.6/8.11.6) id fAULY2c00478; Fri, 30 Nov 2001 22:34:02 +0100 Date: Fri, 23 Nov 2001 16:27:00 -0000 Message-Id: <200111302134.fAULY2c00478@ulmo.localdomain> X-Authentication-Warning: ulmo.localdomain: guerby set sender to guerby@acm.org using -f From: To: gcc@gcc.gnu.org Subject: [Ada] Q about building cross gnatlib Reply-to: guerby@acm.org X-SW-Source: 2001-11/txt/msg01144.txt.bz2 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: To: gcc@gcc.gnu.org Subject: [Ada] Q about building cross gnatlib Date: Fri, 30 Nov 2001 13:40:00 -0000 Message-ID: <200111302134.fAULY2c00478@ulmo.localdomain> X-SW-Source: 2001-11/msg01645.html Message-ID: <20011130134000.iHEhGkdycDvmElGS53bBia3CFaa65L27BKovZzj7BWc@z> 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