On Tue, Mar 16, 2010 at 12:43 PM, Doug Semler wrote:
>>
>> Do you mean that your toolchain is multilib with 32-bit as the
>> primary? Otherwise, I don't see how a 32-bit chain builds a 64-bit
>> lib.
>>
>
> Yes, of course...
>
> binutils compiled with --target=i686-w64-mingw32
> --enable-targets=
>
> Do you mean that your toolchain is multilib with 32-bit as the
> primary? Otherwise, I don't see how a 32-bit chain builds a 64-bit
> lib.
>
Yes, of course...
binutils compiled with --target=i686-w64-mingw32
--enable-targets=i686-w64-mingw32,x86_64-w64-mingw32
gcc configured appropriately f
On Tue, Mar 16, 2010 at 12:09 PM, Doug Semler wrote:
> Found a bug in the build system of the crt when using a 32 bit (ie.
> i386-w64-mingw32) toolchain to build the 64 bit crt --- the correct
> --as-flags are not passed to dlltool for the 64 bit libraries. This
> means that when dlltool compiles
Found a bug in the build system of the crt when using a 32 bit (ie.
i386-w64-mingw32) toolchain to build the 64 bit crt --- the correct
--as-flags are not passed to dlltool for the 64 bit libraries. This
means that when dlltool compiles its generated assembler, the
assembler, if it picks up the 32
It would help to know how redc.s is built (directly compiled from the
assembler it looks like...), and how the file is linked...
if it is hand assembly, did you remember run as with the -g option so
that source information is saved in the object?
If it is linked in a dll, did you try to load the
On Tue, Mar 16, 2010 at 7:18 AM, David Cleaver wrote:
> Any suggestions on how I should proceed? I don't know how to use gdb very
> well.
> If anyone has any tips or tricks on how to trouble shoot this problem I'd
> appreciate it very much. Thanks for your time.
Email the asm file to this lis
On Tue, Mar 16, 2010 at 2:18 PM, David Cleaver wrote:
>
> Ozkan Sezer wrote:
>> AFAIK, you may not tell the difference, and I'm afraid
>> that the 20100123 version you just tried may not have
>> been compiled against expat either. FWIW, I will compile
>> gdb against expat in my next personal build
Ozkan Sezer wrote:
> AFAIK, you may not tell the difference, and I'm afraid
> that the 20100123 version you just tried may not have
> been compiled against expat either. FWIW, I will compile
> gdb against expat in my next personal builds. ... and
> even made a version just now, see if this works f
On Tue, Mar 16, 2010 at 5:15 AM, David Cleaver wrote:
>
> Kai Tietz wrote:
>> Hello David,
>>
>> The problem you've shown is reasoned by using a gdb built without
>> libexpat. You can download a more current version from our SF file
>> sections (see Tools), which is build with libexpat. If gdb isn
