This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Fix gdbserver build with x86_64-w64-mingw32 -m32

On 01/12/2015 05:54 PM, Zach Welch wrote:
> On 01/09/2015 08:17 PM, Joel Brobecker wrote:
>>> This patch allows a x86_64-w64-mingw32 toolchain to build a 32-bit
>>> gdbserver.  Without it, gdbserver attempts to link to the 64-bit
>>> register files, resulting in undefined references.
>>> 	* Add check for -m32 on x86_64-*-mingw*.
>>> 	* configure.srv: If using -m32 on x86_64-*-mingw*, use i386
>>> 	instead of amd64 registers.
>>> 	* configure: Regenerated.
>>> 	* aclocal.m4: Regenerated.
>> Intuitively, I would say that the proper way to achive a 32bit
>> gdbserver is by configuring it using a 32bit triplet, no?
>> What happens if you do:
>>     ./configure --build=i686-pc-mingw32 CFLAGS='-m32'
> Actually, I am using i686-pc-linux-gnu as $build.  I think you meant to
> ask for --host.  I am using --host=x86_64-w64-mingw32 CFLAGS=-m32, which
> is distinctly different than i686-pc-mingw32.  For example, they use
> completely different runtime libraries.  I think it would be an error to
> conflate the two toolchains.  

Not offhand objecting to the patch, but the right triplet would
be i686-w64-mingw32.  It's what Fedora uses, for example.  In practice,
it'd be the same as i686-pc-mingw32 though.  AFAIK, nowhere do we need
to distinguish them.

> Thus, I stand by my patch as the correct solution for this issue.

Pedro Alves

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]