This is the mail archive of the
mailing list for the binutils project.
Re: Cross ld build problems
- From: Nicholas Clifton <nickc at redhat dot com>
- To: JonY <10walls at gmail dot com>, binutils <binutils at sourceware dot org>
- Date: Wed, 02 Apr 2014 15:22:38 +0100
- Subject: Re: Cross ld build problems
- Authentication-results: sourceware.org; auth=none
- References: <533BF251 dot 3020900 at gmail dot com>
I think the fix is to compile it as default-manifest-new.o but install
it as default-manifest.o, though I'm not too familiar with the Makefile
to do this.
The problem here is that if you are running a built but not installed
linker then it will fail to find the default manifest. Running an
uninstalled linker is not uncommon either - I do it all the time when
I am having second thoughts about using the linker as the agent to
install the default manifest however. IMHO it would be better if
gcc/libgcc did this - after all they already have the multilib mechanism
in place and they already build files like crt0.o and crtend.o. Why
not add default-manifest.o to the list ? The answer, as I understand
it, is that the Cygwin developers want the manifest added even if gcc
is not used to link the application. So maybe it is time to impose a
requirement to use gcc to link all Cygwin and Mingw binaries ?