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 16:35:28 +0100
- Subject: Re: [RFA] Fix bin2c executable generation for cross-generation
- References: <001e01cb7c35$11ca4290$355ec7b0$@muller@ics-cnrs.unistra.fr>
On Nov 4, 2010, at 4:29 PM, Pierre Muller wrote:
> I was trying to compile binutils (under others) for mingw64
> on cygwin.
>
> I used
> ../src/configure --host=x86_64-w64-mingw32 CFLAGS="-gstabs+ -O0"
> --disable-libgui --disable-gdbtk --enable-targets=all
>
> make all-gdb all-binutils all-gas all-ld
>
>
> It failed on bin2c because this is a executable that is built
> using gcc compiler instead of x86_64-w64-mingw32-gcc
> but the compilation still used $(LIBINTL).
> $(LIBINTL) is set to the just compiled library ../intl/libintl.a
> which is compiled for w64 target, not cygwin
> hence the build failure.
>
> 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 ?
Tristan.