On Fri, Jul 8, 2011 at 8:34 AM, Alen Skondro wrote:
> This helped!
> binutils can now create i686 and x86_64 targets and GCC discovered this!
> Thank you guys for your expertise!
>
> The only problem I'm still having is that the $PREFIX\i686-w64-mingw32\lib
> contains 32bit libraries but GCC looks
This helped!
binutils can now create i686 and x86_64 targets and GCC discovered this!
Thank you guys for your expertise!
The only problem I'm still having is that the $PREFIX\i686-w64-mingw32\lib
contains 32bit libraries but GCC looks only in this one folder regardless
whether linking to 64bit or
Please read proper. This option is for binutils configure and you will
find this option in bfd/
Kai
2011/7/8 JonY :
> On 7/8/2011 13:26, Kai Tietz wrote:
>> 2011/7/8 JonY :
>>> On 7/8/2011 04:56, Alen Skondro wrote:
Hello,
I'm stuck again.
After successfully building gcc
On 7/8/2011 13:26, Kai Tietz wrote:
> 2011/7/8 JonY :
>> On 7/8/2011 04:56, Alen Skondro wrote:
>>> Hello,
>>>
>>> I'm stuck again.
>>>
>>> After successfully building gcc 4.6 targeting only i686-w64-mingw32 I'm
>>> getting errors while creating a cross compiler for multilib target
>>> (i686-w64-mi
2011/7/8 JonY :
> On 7/8/2011 04:56, Alen Skondro wrote:
>> Hello,
>>
>> I'm stuck again.
>>
>> After successfully building gcc 4.6 targeting only i686-w64-mingw32 I'm
>> getting errors while creating a cross compiler for multilib target
>> (i686-w64-mingw32 + x86_64-w64-mingw32).
>>
>> binutils is
On 7/8/2011 04:56, Alen Skondro wrote:
> Hello,
>
> I'm stuck again.
>
> After successfully building gcc 4.6 targeting only i686-w64-mingw32 I'm
> getting errors while creating a cross compiler for multilib target
> (i686-w64-mingw32 + x86_64-w64-mingw32).
>
> binutils is configure like this:
>
Hello,
I'm stuck again.
After successfully building gcc 4.6 targeting only i686-w64-mingw32 I'm
getting errors while creating a cross compiler for multilib target
(i686-w64-mingw32 + x86_64-w64-mingw32).
binutils is configure like this:
=
$../binutils/configure --target=i686
