This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [RFA] Fix bin2c executable generation for cross-generation
- From: Tristan Gingold <gingold at adacore dot com>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: <binutils at sourceware dot org>
- Date: Thu, 4 Nov 2010 17:01:20 +0100
- Subject: Re: [RFA] Fix bin2c executable generation for cross-generation
- References: <001e01cb7c35$11ca4290$355ec7b0$@muller@ics-cnrs.unistra.fr> <ACB7C5BA-C11C-400C-AC96-11C744BC5D4C@adacore.com> <002f01cb7c37$b2ca50c0$185ef240$@muller@ics-cnrs.unistra.fr>
On Nov 4, 2010, at 4:48 PM, Pierre Muller wrote:
>> The patch below uses -lintl instead of $(LIBINTL)
>> for bin2c$(EXEEXT_FOR_BUILD) rule.
>> This allowed me to complete this build.
>>
>>
>> Is this patch OK?
>
> I don't think so because libintl is not required (ie you can build with
> --disable-libintl).
> I can't find the issue but why this concerns only bin2c ?
>
>
> Hi Tristan,
>
> The fact is that it is the only rule that
> uses $(LIBINTL) for a rule that has to be build
> with build gcc, while $(LIBINTL) is a host file,
> thus of incompatible type.
Right.
> Should "--disable-libintl" apply to host or to build
> or to both?
>
> If you know how to change -lintl into "" if --disable-libintl
> is set, this would be fine for me, but I am still not
> really at ease when it comes to configure subtleties.
Neither I am...
> Anyhow, something needs to be changed...
Alan should know much more than me about this tool, but
if this is a build-tool only, I think we could simply remove its dependency on libintl.
(On the other side I don't see any use of it).
If this is a normal tool, we can simply treat it like the other binutils.
Tristan.