On Sun, Sep 20, 2009 at 6:42 PM, Erik de Castro Lopo
wrote:
> NightStrike wrote:
>
>> Add TARGET_ARCH=i686-w64-mingw32 to your make command line.
>
> Shouldn't that be i686-w32-mingw32 or maybe even i686-pc-mingw32?
The w64 is a very poorly named vendor key to specify all the stuff at
mingw-w64.s
JonY wrote:
> Was it clear?
Yes, much clearer. Thank you.
Cheers,
Erik
--
--
Erik de Castro Lopo
http://www.mega-nerd.com/
--
Come build with us! Th
On 9/21/2009 09:48, Erik de Castro Lopo wrote:
> JonY wrote:
>
>> On 9/21/2009 06:42, Erik de Castro Lopo wrote:
>>> NightStrike wrote:
>>>
Add TARGET_ARCH=i686-w64-mingw32 to your make command line.
>>>
>>> Shouldn't that be i686-w32-mingw32 or maybe even i686-pc-mingw32?
>>
>> "w64" is alrea
JonY wrote:
> On 9/21/2009 06:42, Erik de Castro Lopo wrote:
> > NightStrike wrote:
> >
> >> Add TARGET_ARCH=i686-w64-mingw32 to your make command line.
> >
> > Shouldn't that be i686-w32-mingw32 or maybe even i686-pc-mingw32?
>
> "w64" is already a vendor key recognized by gcc. It will add suppo
On 9/21/2009 06:42, Erik de Castro Lopo wrote:
> NightStrike wrote:
>
>> Add TARGET_ARCH=i686-w64-mingw32 to your make command line.
>
> Shouldn't that be i686-w32-mingw32 or maybe even i686-pc-mingw32?
>
> Erik
Hi,
"w64" is already a vendor key recognized by gcc. It will add support for
mingw-w
NightStrike wrote:
> Add TARGET_ARCH=i686-w64-mingw32 to your make command line.
Shouldn't that be i686-w32-mingw32 or maybe even i686-pc-mingw32?
Erik
--
--
Erik de Castro Lopo
http://www.mega-nerd.com/
--
Add TARGET_ARCH=i686-w64-mingw32 to your make command line.
On Sat, Sep 19, 2009 at 8:02 PM, Erik de Castro Lopo
wrote:
> HI all,
>
> I've had a bit of a look at the makebuildroot.mk build script. It
> seems like this may be able to make both a win32 and a win64 cross
> compiler.
>
> Is that cor
On Sun, Sep 20, 2009 at 12:05 PM, Erik de Castro Lopo
wrote:
> Ozkan Sezer wrote:
>
>> Should I commit this then:
>>
>> Index: _mingw.h
>> ===
>> --- _mingw.h (revision 1397)
>> +++ _mingw.h (working copy)
>> @@ -441,20 +441,10 @@
>
Ozkan Sezer wrote:
> Should I commit this then:
>
> Index: _mingw.h
> ===
> --- _mingw.h (revision 1397)
> +++ _mingw.h (working copy)
> @@ -441,20 +441,10 @@
> #define _TRUNCATE ((size_t)-1)
> #endif
>
> -#ifndef __USE_MINGW_AN
On Sun, Sep 20, 2009 at 12:00 PM, Kai Tietz wrote:
> 2009/9/20 Ozkan Sezer :
>> On Sun, Sep 20, 2009 at 11:52 AM, Kai Tietz wrote:
>>> To solve those kind of issues inttypes.h is there, and is btw also
>>> adjusted by our header-set when __USE_MINGW_ANSI_STDIO is defined. A
>>> mix mode between p
2009/9/20 Ozkan Sezer :
> On Sun, Sep 20, 2009 at 11:52 AM, Kai Tietz wrote:
>> To solve those kind of issues inttypes.h is there, and is btw also
>> adjusted by our header-set when __USE_MINGW_ANSI_STDIO is defined. A
>> mix mode between platform M$ printf formats and gnu'ish one is in
>> general
On Sun, Sep 20, 2009 at 11:52 AM, Kai Tietz wrote:
> To solve those kind of issues inttypes.h is there, and is btw also
> adjusted by our header-set when __USE_MINGW_ANSI_STDIO is defined. A
> mix mode between platform M$ printf formats and gnu'ish one is in
> general a bad idea.
>
> Kai
>
Should
To solve those kind of issues inttypes.h is there, and is btw also
adjusted by our header-set when __USE_MINGW_ANSI_STDIO is defined. A
mix mode between platform M$ printf formats and gnu'ish one is in
general a bad idea.
Kai
2009/9/20 Kai Tietz :
> 2009/9/20 Ozkan Sezer :
>> On Sun, Sep 20, 2009
2009/9/20 Ozkan Sezer :
> On Sun, Sep 20, 2009 at 2:55 AM, Erik de Castro Lopo
> wrote:
>>
>> Please note, I am subscribed to the list. No need to CC me on reply.
>>
>> Ozkan Sezer wrote:
>>
>>> A question, though: Are you using gcc-3.4.5 or 4.4.0 as the mingw.org
>>> compiler for your w32 builds?
On Sun, Sep 20, 2009 at 2:55 AM, Erik de Castro Lopo
wrote:
>
> Please note, I am subscribed to the list. No need to CC me on reply.
>
> Ozkan Sezer wrote:
>
>> A question, though: Are you using gcc-3.4.5 or 4.4.0 as the mingw.org
>> compiler for your w32 builds? I think the warning may be a gcc-
On Sun, Sep 20, 2009 at 3:02 AM, Erik de Castro Lopo
wrote:
> HI all,
>
> I've had a bit of a look at the makebuildroot.mk build script. It
> seems like this may be able to make both a win32 and a win64 cross
> compiler.
>
> Is that correct?
>
> Cheers,
> Erik
> --
> -
16 matches
Mail list logo