[Bug ada/19489] New: gnat tools not buildable cross

[Bug ada/19489] New: gnat tools not buildable cross

[joel at gcc dot gnu dot org]

The Makefile stanzas for building the gnat tools cross is somehow confused and
mixing use of the newly built cross compiler and the native compiler.  The gnat
tools should be built to execute on the host.  I posted a message about this to
the gcc mailing list (http://gcc.gnu.org/ml/gcc/2005-01/msg00904.html).  I will
attach a section from a log.

-- 
           Summary: gnat tools not buildable cross
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: joel at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,laurent at guerby dot
                    net
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: *-rtems*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at gcc dot gnu dot org]

------- Additional Comments From joel at gcc dot gnu dot org  2005-01-17 20:08 -------
Created an attachment (id=7975)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7975&action=view)
Build Log from powerpc-rtems gnat attempt

Build log of failure case.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |19488


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[bonzini at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bonzini at gcc dot gnu dot
                   |                            |org
            Summary|gnat tools not buildable    |gnat tools not buildable
                   |cross                       |cross


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[bonzini at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |neroden at gcc dot gnu dot
                   |                            |org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[bonzini at gcc dot gnu dot org]

------- Additional Comments From bonzini at gcc dot gnu dot org  2005-01-27 14:09 -------
You may try adding a gnattools directory, whose makefile and configury is based
on libada's, but which is a host module rather than a target module.

Nathanael knows best, I think.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

------- Additional Comments From neroden at gcc dot gnu dot org  2005-01-29 22:19 -------
>You may try adding a gnattools directory, whose makefile and configury is   
based   
>on libada's, but which is a host module rather than a target module.   
   
Correct (dammit).  :-)   
 
I've already done this on the libada-gnattools-branch,   
but I've also done some other things there, which wouldn't be suitable for 
stage 3.  Please try a snapshot of the libada-gnattools-branch from... hmm, 
let's see...  December 1, 2004.  
  
If it works correctly (and I know it works correctly for native tools),  
it's safe enough to merge to mainline even in stage 3.  I would have done so 
already, but without a bug report, it wasn't stage-3-suitable. 
  
If it doesn't, come back to me; I expect that there's some incremental change 
on top of it which should sort out any remaining problems.   

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-01-29 22:19:59
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[laurent at guerby dot net]

------- Additional Comments From laurent at guerby dot net  2005-01-29 22:39 -------
Since it is clearly a regression (vs 3.2 cross RTEMS/Ada capabilities), would
you mind proposing a patch to current 4.0 libada? I've included Arnaud in CC.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |charlet at adacore dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[charlet at adacore dot com]

------- Additional Comments From charlet at adacore dot com  2005-01-31 09:21 -------
Subject: Re:  gnat tools not buildable cross

> Since it is clearly a regression (vs 3.2 cross RTEMS/Ada capabilities), would
> you mind proposing a patch to current 4.0 libada? I've included Arnaud in CC.

There must be a simpler way to fix this regression. I am not even convinced
that this change would fix this particular bug anyway, so we first need this
info before proceeding.

Such major addition is not suitable for stage 3 in my opinion (but very
welcome for stage 1), we want a much more localized change, which is certainly
possible here.

Arno


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-01-31 15:24 -------
Subject: Re:  gnat tools not buildable cross

charlet at adacore dot com wrote:
> ------- Additional Comments From charlet at adacore dot com  2005-01-31 09:21 -------
> Subject: Re:  gnat tools not buildable cross
> 
> 
>>Since it is clearly a regression (vs 3.2 cross RTEMS/Ada capabilities), would
>>you mind proposing a patch to current 4.0 libada? I've included Arnaud in CC.

If he can prepare a patch vs 4.0 CVS, I am willing to test it.

> There must be a simpler way to fix this regression. I am not even convinced
> that this change would fix this particular bug anyway, so we first need this
> info before proceeding.

Agreed.  If it doesn't work on the libada branch, there there is
no fix at hand.  Even if it does, then a patch against 4.0 would have
to be evaluated.

> Such major addition is not suitable for stage 3 in my opinion (but very
> welcome for stage 1), we want a much more localized change, which is certainly
> possible here.

That's what the RM is for.  Let's get a solution first and then see if 
it meets the criteria.  No point saying it doesn't without knowing.

--joel


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-01-31 15:23 -------
Subject: Re:  gnat tools not buildable cross

neroden at gcc dot gnu dot org wrote:
> ------- Additional Comments From neroden at gcc dot gnu dot org  2005-01-29 22:19 -------
> 
>>You may try adding a gnattools directory, whose makefile and configury is   
> 
> based   
> 
>>on libada's, but which is a host module rather than a target module.   
> 
>    
> Correct (dammit).  :-)   
>  
> I've already done this on the libada-gnattools-branch,   
> but I've also done some other things there, which wouldn't be suitable for 
> stage 3.  Please try a snapshot of the libada-gnattools-branch from... hmm, 
> let's see...  December 1, 2004.  

Where are these snapshots?  Or exactly how do you want it checked out
from CVS.

> If it works correctly (and I know it works correctly for native tools),  
> it's safe enough to merge to mainline even in stage 3.  I would have done so 
> already, but without a bug report, it wasn't stage-3-suitable. 

There is now a bug report against 4.x and there was at least a lot of
whining for 3.3 and 3.4. :)

> If it doesn't, come back to me; I expect that there's some incremental change 
> on top of it which should sort out any remaining problems.   

Great.  Point me in the right direction and I will be happy to test.

--joel


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[bonzini at gcc dot gnu dot org]

------- Additional Comments From bonzini at gcc dot gnu dot org  2005-01-31 15:56 -------
> Such major addition is not suitable for stage 3 in my opinion (but very
> welcome for stage 1), we want a much more localized change, which is certainly
> possible here.

I don't think so.  When you get into the libada directory, CC="$(CC_FOR_TARGET)"
and all hope is lost of having the tools work in a cross configuration.

Paolo

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[charlet at adacore dot com]

------- Additional Comments From charlet at adacore dot com  2005-01-31 16:38 -------
Subject: Re:  gnat tools not buildable cross

> I don't think so.  When you get into the libada directory, CC="$(CC_FOR_TARGET)"
> and all hope is lost of having the tools work in a cross configuration.

That is wrong, ada/Makefile.in is designed to support this configuration,
and use the native gnat bootstrap compiler instead of $(CC) to build the
tools in the case of cross compilation.

Arno


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-02-01 00:46 -------
Subject: Re:  gnat tools not buildable cross

charlet at adacore dot com wrote:
> ------- Additional Comments From charlet at adacore dot com  2005-01-31 16:38 -------
> Subject: Re:  gnat tools not buildable cross
> 
> 
>>I don't think so.  When you get into the libada directory, CC="$(CC_FOR_TARGET)"
>>and all hope is lost of having the tools work in a cross configuration.
> 
> 
> That is wrong, ada/Makefile.in is designed to support this configuration,
> and use the native gnat bootstrap compiler instead of $(CC) to build the
> tools in the case of cross compilation.

FWIW I get the same error on the gcc-libada-gnattools-branch.

Nathaniel are there any special instructions for cross Ada
or is it just supported to work?

--joel



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-02 04:21 -------
Oh, drat, I may have figured it out. 
I need the gcc/libada.mk file produced during the build.  I believe there's 
something wrong with it, but until I see what's produced, I don't know exactly 
what.  Please attach to bug report.  :-) 
    
      

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-02 04:22 -------
Sorry, that's "gcc/libada-mk", not "gcc/libada.mk". 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-02 04:32 -------
Oh -- while we're at it, please make sure that the "gnattools-cross" target is 
being invoked from the libada directory, and that it is invoking the targets 
which crash.  If it isn't -- if they're being invoked by gnattools-native, for 
instance -- there's a whole different sort of bug going on. 
 
The partial build log did not make that clear.  
  

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |neroden at gcc dot gnu dot
                   |dot org                     |org
             Status|NEW                         |ASSIGNED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[laurent at guerby dot net]

------- Additional Comments From laurent at guerby dot net  2005-02-02 07:45 -------
Here's what I got as gcc/libada-mk:

[...]
# GCC's Makefile fragment for libada.
# libada needs some information from the GCC configure file at the moment,
# and this exists to transfer that information in as clean a way as possible.

exeext=
libdir=${exec_prefix}/lib
gcc_version=4.0.0
NOCOMMON_FLAG=-fno-common
WARN_CFLAGS=$(GCC_WARN_CFLAGS)
cc_set_by_configure=$(CC)
gcc_tmake_file= $(srcdir)/config/rs6000/t-rs6000
$(srcdir)/config/rs6000/t-fprules $(srcdir)/config/rs6000/t-rtems
$(srcdir)/config/t-rtems $(srcdir)/config
/rs6000/t-ppccomm
gcc_xmake_file= $(srcdir)/config/x-linux

# This really shouldn't be needed, but for now...
CC=gcc

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[laurent at guerby dot net]

------- Additional Comments From laurent at guerby dot net  2005-02-02 12:08 -------
Do I need to regenerate configure stuff after your patch (I don't know
how to do it):

...
make -C tools -f ../Makefile "CC=@cc_for_cross_gnattools@" "CFLAGS=-O2 -g -O2 
-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common"
"LDFLAGS=" "ADAFLAGS=-gnatpg -gnata" "INCLUDES=-I. -I.. -I../..
-I/home/guerby/work/gcc/version-head/gcc/ada
-I/home/guerby/work/gcc/version-head/gcc/ada/../config
-I/home/guerby/work/gcc/version-head/gcc/ada/../../include
-I/home/guerby/work/gcc/version-head/gcc/ada/.."
"ADA_INCLUDES=-I/home/guerby/work/gcc/install/install-20050126T091837/lib/gcc/i686-pc-linux-gnu/4.0.0/adalib/../adainclude
-I/home/guerby/work/gcc/install/install-20050126T091837/lib/gcc/i686-pc-linux-gnu/4.0.0/adalib/
-I. -I/home/guerby/work/gcc/version-head/gcc/ada"
"libsubdir=/home/guerby/work/gcc/cross/install/lib/gcc/powerpc-rtems/4.0.0"
"exeext=" "fsrcdir=/home/guerby/work/gcc/version-head/gcc/ada"
"srcdir=/home/guerby/work/gcc/version-head/gcc/ada" "TOOLS_LIBS= ../../prefix.o
../../version.o link.o ../../../libiberty/libiberty.a  " "GNATMAKE=gnatmake"
"GNATLINK=gnatlink" "GNATBIND=gnatbind" \
  TOOLSCASE=cross INCLUDES="" gnatmake-re gnatlink-re
make[3]: Entering directory `/home/guerby/work/gcc/cross/build/gcc/ada/tools'
rm -f tools/*
rm -rf tools
mkdir -p tools
(cd tools; ln -s ../sdefault.adb .)
touch ../stamp-tools
/bin/sh: cc_for_cross_gnattools@: command not found
make[3]: *** [link.o] Error 127
make[3]: Leaving directory `/home/guerby/work/gcc/cross/build/gcc/ada/tools'
make[2]: *** [gnattools1-re] Error 2
make[2]: Leaving directory `/home/guerby/work/gcc/cross/build/gcc/ada'
make[1]: *** [gnattools-cross] Error 2
make[1]: Leaving directory `/home/guerby/work/gcc/cross/build/powerpc-rtems/libada'
make: *** [all-target-libada] Error 2

My build tree gcc/libada-mk is

# GCC's Makefile fragment for libada.
# libada needs some information from the GCC configure file at the moment,
# and this exists to transfer that information in as clean a way as possible.

exeext=
libdir=${exec_prefix}/lib
gcc_version=4.0.0
NOCOMMON_FLAG=-fno-common
WARN_CFLAGS=$(GCC_WARN_CFLAGS)
cc_set_by_configure=@cc_for_cross_gnattools@
gcc_tmake_file= $(srcdir)/config/rs6000/t-rs6000
$(srcdir)/config/rs6000/t-fprules $(srcdir)/config/rs6000/t-rtems
$(srcdir)/config/t-rtems $(srcdir)/config/rs6000/t-ppccomm
gcc_xmake_file= $(srcdir)/config/x-linux

# This really shouldn't be needed, but for now...
CC=gcc



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[laurent@guerby.net]

------- Additional Comments From laurent at guerby dot net  2005-02-06 10:02 -------
(In reply to comment #19)

Nathanel I confirm your small patch (+autoconf) restores Ada cross x86 to
powerpc-rtems build, and I've even been able to powerpc-rtems-gnatmake Ada
examples and run them on gdb psim. It also does not break native bootstrap as
far as I can tell, so all looks good for commit testing wise.

Thanks for helping!

-- 
Bug 19489 depends on bug 19488, which changed state.

Bug 19488 Summary: RTEMS Ada RTS doesn't compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19488

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-02-07 22:41 -------
Subject: Re:  gnat tools not buildable cross

laurent at guerby dot net wrote:
> ------- Additional Comments From laurent at guerby dot net  2005-02-06 10:02 -------
> (In reply to comment #19)
> 
> Nathanel I confirm your small patch (+autoconf) restores Ada cross x86 to
> powerpc-rtems build, and I've even been able to powerpc-rtems-gnatmake Ada
> examples and run them on gdb psim. It also does not break native bootstrap as
> far as I can tell, so all looks good for commit testing wise.
> 
> Thanks for helping!

Is everything in CVS?  I can't reproduce this yet.   I had trouble with 
previously installed cross toolsets getting in the way but removed them
and got past that.

I checked my procedure versus Laurent's revised instructions and end 
with this.

checking for gcc... 
/usr3/ftp_archive/gnu/gcc/ss/b-head/b-powerpc-rtems4.7/gcc/xgcc 
-B/usr3/ftp_archive/gnu/gcc/ss/b-head/b-powerpc-rtems4.7/gcc/ -nostdinc 
-B/usr3/ftp_archive/gnu/gcc/ss/b-head/b-powerpc-rtems4.7/powerpc-rtems4.7/newlib/ 
-isystem 
/usr3/ftp_archive/gnu/gcc/ss/b-head/b-powerpc-rtems4.7/powerpc-rtems4.7/newlib/targ-include 
-isystem 
/usr3/ftp_archive/gnu/gcc/ss/b-head/gcc-libada-gnattools-branch/newlib/libc/include 
-B/opt/rtems-test/powerpc-rtems4.7/bin/ 
-B/opt/rtems-test/powerpc-rtems4.7/lib/ -isystem 
/opt/rtems-test/powerpc-rtems4.7/include -isystem 
/opt/rtems-test/powerpc-rtems4.7/sys-include
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C 
compiled programs.
If you meant to cross compile, use `--host'.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[laurent at guerby dot net]

------- Additional Comments From laurent at guerby dot net  2005-02-07 22:52 -------
Nathanael patch is not in CVS, as mentionned on RTEMSAda wiki
http://www.rtems.com/phpwiki/index.php/RTEMSAda

A few things you may have missed:

1. configure for target "powerpc-rtems" and no variation allowed
("powerpc-rtems4.7-elf" for example is known *not* to work, I haven't investigated
why but I assume it's a broken configure in the millions of configure in newlib)

2. for GCC apply first the patch from comment #16, and rerun autoconf in
cvs-gcc/gcc/

3. don't forget to put INSTALL/bin in path before binutils and all other steps,
INSTALL being an empty dir to start with (--prefix=INSTALL for all steps)

4. build GCC,newlib with C only first, install, then rebuild with c,ada

5. for GDB/psim you need to edit one broken configure as documented

Hope this helps, if not please send me the exact list of PATH=,configure,make
and make install you used so I can check where we diverge :).

Laurent

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[cvs-commit at gcc dot gnu dot org]

------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-02-07 23:11 -------
Subject: Bug 19489

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	neroden@gcc.gnu.org	2005-02-07 23:11:05

Modified files:
	gcc            : libada-mk.in configure.ac configure ChangeLog 

Log message:
	PR ada/19489
	* libada-mk.in: Use cc_for_cross_gnattools, not cc_set_by_configure.
	* configure.ac: Set cc_for_cross_gnattools.
	* configure: Regenerate.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/libada-mk.in.diff?cvsroot=gcc&r1=2.1&r2=2.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/configure.ac.diff?cvsroot=gcc&r1=2.93&r2=2.94
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/configure.diff?cvsroot=gcc&r1=1.884&r2=1.885
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.7415&r2=2.7416



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-07 23:15 -------
Closing.  Laurent, I may ask you to test my alternate solution later (when 
it's ready) though, OK? 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-02-08 00:01 -------
Subject: Re:  gnat tools not buildable cross

neroden at gcc dot gnu dot org wrote:
> ------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-07 23:15 -------
> Closing.  Laurent, I may ask you to test my alternate solution later (when 
> it's ready) though, OK? 

Is a fix likely to get into 4.0?

FYI Once I am able to build, the next issue is that the Ada libraries
do not look into newlib's headers and do not have a way to let a
target add specific include directories.  See gcc/config/t-rtems for
the OS specific newlib include directory we need.  With that resolved,
I think it could build in a single pass.

--joel


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at gcc dot gnu dot org]

------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-08 18:30 -------
>Is a fix likely to get into 4.0? 
Yes, the hackish fix is in.  I hope to get the cleaner fix in, but who knows. 
 
>FYI Once I am able to build, the next issue is that the Ada libraries 
>do not look into newlib's headers and do not have a way to let a 
>target add specific include directories.  See gcc/config/t-rtems for 
>the OS specific newlib include directory we need.  With that resolved, 
>I think it could build in a single pass. 
I wouldn't want to touch this until substantially more of the branch went in, 
so that's probably a 4.1 issue. 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-02-08 19:16 -------
Subject: Re:  gnat tools not buildable cross

neroden at gcc dot gnu dot org wrote:
> ------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-08 18:30 -------
> 
>>Is a fix likely to get into 4.0? 
> 
> Yes, the hackish fix is in.  I hope to get the cleaner fix in, but who knows. 
>  
> 
>>FYI Once I am able to build, the next issue is that the Ada libraries 
>>do not look into newlib's headers and do not have a way to let a 
>>target add specific include directories.  See gcc/config/t-rtems for 
>>the OS specific newlib include directory we need.  With that resolved, 
>>I think it could build in a single pass. 
> 
> I wouldn't want to touch this until substantially more of the branch went in, 
> so that's probably a 4.1 issue. 

I need to get to test this first but I think the mistake in the 
gcc/ada/Makefile.in is actually quite simple.  It has this:


GNATLIBCFLAGS_FOR_C = $(GNATLIBCFLAGS) $(TARGET_LIBGCC2_CFLAGS) 
-fexceptions \
         -DIN_RTS


$(TARGET_LIBGCC2_CFLAGS) is not sufficient to find all the newlib
headers.  But the gcc/Makefile.in also uses $(LIBGCC2_INCLUDES) which is
target specific when compiling libgcc2.  LIBGCC2_INCLUDES is primarily 
set by RTEMS, VxWorks, and Cygwin.

What do you think?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[neroden at twcny dot rr dot com]

------- Additional Comments From neroden at twcny dot rr dot com  2005-02-09 07:13 -------
Subject: Re:  gnat tools not buildable cross

joel at oarcorp dot com wrote:
> ------- Additional Comments From joel at oarcorp dot com  2005-02-08 19:16 -------
> Subject: Re:  gnat tools not buildable cross
> 
> neroden at gcc dot gnu dot org wrote:
> 
>>------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-08 18:30 -------
>>
>>
>>>Is a fix likely to get into 4.0? 
>>
>>Yes, the hackish fix is in.  I hope to get the cleaner fix in, but who knows. 
>> 
>>
>>
>>>FYI Once I am able to build, the next issue is that the Ada libraries 
>>>do not look into newlib's headers and do not have a way to let a 
>>>target add specific include directories.  See gcc/config/t-rtems for 
>>>the OS specific newlib include directory we need.  With that resolved, 
>>>I think it could build in a single pass. 
>>
>>I wouldn't want to touch this until substantially more of the branch went in, 
>>so that's probably a 4.1 issue. 
> 
> 
> I need to get to test this first but I think the mistake in the 
> gcc/ada/Makefile.in is actually quite simple.  It has this:
> 
> 
> GNATLIBCFLAGS_FOR_C = $(GNATLIBCFLAGS) $(TARGET_LIBGCC2_CFLAGS) 
> -fexceptions \
>          -DIN_RTS
> 
> 
> $(TARGET_LIBGCC2_CFLAGS) is not sufficient to find all the newlib
> headers.  But the gcc/Makefile.in also uses $(LIBGCC2_INCLUDES) which is
> target specific when compiling libgcc2.  LIBGCC2_INCLUDES is primarily 
> set by RTEMS, VxWorks, and Cygwin.
> 
> What do you think?

Hmm.  You could be right.  :-)

The trouble is that there's several layers of Makefiles and Makefile 
fragments and configures and configure fragments taking bits from each 
other, and so it's not as absolutely trivial to get LIBGCC2_INCLUDES in 
the right places cleanly -- without misapplying it in cross cases -- as 
it ought to be.  This, of course, is what my cleanups are designed to 
fix; it *should* be trivial to get it in the right places.  :-)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[joel at oarcorp dot com]

------- Additional Comments From joel at oarcorp dot com  2005-02-09 12:44 -------
Subject: Re:  gnat tools not buildable cross

neroden at twcny dot rr dot com wrote:
> ------- Additional Comments From neroden at twcny dot rr dot com  2005-02-09 07:13 -------
> Subject: Re:  gnat tools not buildable cross
> 
> joel at oarcorp dot com wrote:
> 
>>------- Additional Comments From joel at oarcorp dot com  2005-02-08 19:16 -------
>>Subject: Re:  gnat tools not buildable cross
>>
>>neroden at gcc dot gnu dot org wrote:
>>
>>
>>>------- Additional Comments From neroden at gcc dot gnu dot org  2005-02-08 18:30 -------
>>>
>>>
>>>
>>>>Is a fix likely to get into 4.0? 
>>>
>>>Yes, the hackish fix is in.  I hope to get the cleaner fix in, but who knows. 
>>>
>>>
>>>
>>>
>>>>FYI Once I am able to build, the next issue is that the Ada libraries 
>>>>do not look into newlib's headers and do not have a way to let a 
>>>>target add specific include directories.  See gcc/config/t-rtems for 
>>>>the OS specific newlib include directory we need.  With that resolved, 
>>>>I think it could build in a single pass. 
>>>
>>>I wouldn't want to touch this until substantially more of the branch went in, 
>>>so that's probably a 4.1 issue. 
>>
>>
>>I need to get to test this first but I think the mistake in the 
>>gcc/ada/Makefile.in is actually quite simple.  It has this:
>>
>>
>>GNATLIBCFLAGS_FOR_C = $(GNATLIBCFLAGS) $(TARGET_LIBGCC2_CFLAGS) 
>>-fexceptions \
>>         -DIN_RTS
>>
>>
>>$(TARGET_LIBGCC2_CFLAGS) is not sufficient to find all the newlib
>>headers.  But the gcc/Makefile.in also uses $(LIBGCC2_INCLUDES) which is
>>target specific when compiling libgcc2.  LIBGCC2_INCLUDES is primarily 
>>set by RTEMS, VxWorks, and Cygwin.
>>
>>What do you think?
> 
> 
> Hmm.  You could be right.  :-)
> 
> The trouble is that there's several layers of Makefiles and Makefile 
> fragments and configures and configure fragments taking bits from each 
> other, and so it's not as absolutely trivial to get LIBGCC2_INCLUDES in 
> the right places cleanly -- without misapplying it in cross cases -- as 
> it ought to be.  This, of course, is what my cleanups are designed to 
> fix; it *should* be trivial to get it in the right places.  :-)

I played with this overnight and the variable missing in ada/Makefile.in 
is  FLAGS_FOR_TARGET.  It shoudl be included in GNATLIBCFLAGS_FOR_C and 
I can't seem to get it from the top level configure all the way down.

Do you have any idea how to get it down that far?

--joel




-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489

[Bug ada/19489] gnat tools not buildable cross

[pinskia at gcc dot gnu dot org]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.0.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489