From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,e083e2da6a3c57ad
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
X-Received: by 10.180.188.52 with SMTP id fx20mr649620wic.3.1366886959405;
        Thu, 25 Apr 2013 03:49:19 -0700 (PDT)
Path: 
 p18ni25640wiv.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.138.MISMATCH!xlned.com!feeder5.xlned.com!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx05.eternal-september.org!.POSTED!not-for-mail
From: Brian Drummond <brian@shapes.demon.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: GNATBind with a GNAT =?UTF-8?b?Y3Jvc3PigJFjb21waWxlcg==?=
Date: Thu, 25 Apr 2013 10:46:09 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <klb1hh$ves$1@dont-email.me>
References: <op.wv2tmg2cule2fv@cardamome>
Mime-Version: 1.0
Injection-Date: Thu, 25 Apr 2013 10:46:09 +0000 (UTC)
Injection-Info: mx05.eternal-september.org;
 posting-host="da745e888d4a5182b5fda6212bbb0a63";
	logging-data="32220"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18LH3Ql5Me71n0fTqPZkXF0a8layLS8K9k="
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508
	git://git.gnome.org/pan2)
Cancel-Lock: sha1:DxTJCkQVFlNq0uXCS9qOcmtoDAw=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Date: 2013-04-25T10:46:09+00:00
List-Id: <comp.lang.ada>

On Thu, 25 Apr 2013 05:07:18 +0200, Yannick Duchêne (Hibou57) wrote:

> Hi people,
> 
> While trying to figure the cause of some weird errors while compiling
> with a GNAT cross‑compiler, 
[...] 
> I noticed there is a `<target>-gcc`, and a `<target>-ld`  and so
> on, for each of my targets including the native one, but only a
> `<target>-gnatbind` for non‑native target, and the native one only exist
> as unprefixed.

> I don't really have any question, that's just to tell people in case any
> one encounter a similar issue. I still wonder why, as compilation of GCC
> and Binutils generates a prefixed version of all of their tools, why
> don't compilation of GNAT do the same.

Where did this crosscompiler come from?

My non-native target builds have the full set of tools. However...

If you built it from source, with --disable-libada, you may have fallen 
foul of a longstanding GCC "feature" whereby building "gnattools" is also 
(I believe incorrectly) disabled by this configure option.

This leaves you with "<target>-gnat" and ""<target>-gnatbind" but 
"<target>-gnat*" for other values of * are missing. (You should still 
have "<target>-ld" though; it is a binutils product : perhaps it was 
"<target>-gnatlink" that was missing?)

Possible fixes : 
after "make" when building the crosscompiler, "make -c gcc gnattools" may 
build the remaining targets for you. 

If that protests, then you may need to patch the gcc "configure" file to 
allow the missing targets to be built, as in the following patch.

http://sourceforge.net/p/msp430ada/code/ci/tip/tree/patches/23-gcc-4.7-
ada-Makefile.patch

found on

http://sourceforge.net/p/msp430ada/code/ci/tip/tree/patches/

Having applied the patch, obviously you need to re-run configure/make/
[make gnattools if utils missing in build dir]/make install. 

(The AVR-Ada project has also faced this issue with essentially the same 
solution. Some upstream gcc discussion on 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19959 )

If you try this and it works - or if and how it fails - it would be 
useful to follow up.