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
--
--
Erik de Castro Lopo
http://www.mega-ner
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-4.4+
> thing and not actually a mingw-w64 issue, but I don't know for
On Sun, Sep 20, 2009 at 1:08 AM, Erik de Castro Lopo
wrote:
> Ozkan Sezer wrote:
>
>> OK, applied this as rev. 1395:
>> http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=rev&revision=1395
>> Please test.
>
> Real close!
>
> I get the proper C99 behaviour if I compile with:
>
> x86_64-
Ozkan Sezer wrote:
> OK, applied this as rev. 1395:
> http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=rev&revision=1395
> Please test.
Real close!
I get the proper C99 behaviour if I compile with:
x86_64-w64-mingw32-gcc -Wall -std=c99 test.c -o test
but with this:
x86_64-
OK, applied this as rev. 1395:
http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=rev&revision=1395
Please test.
--
Ozkan
On Sat, Sep 19, 2009 at 1:41 PM, Ozkan Sezer wrote:
> On Sat, Sep 19, 2009 at 1:38 PM, Kai Tietz wrote:
>> Ok, add it to our _mingw.h file, too. We can then simplif
On Sat, Sep 19, 2009 at 1:38 PM, Kai Tietz wrote:
> Ok, add it to our _mingw.h file, too. We can then simplify our logic
Will do.
> in our _mingw_printf_(push/pop).h headers, too, as we know that
> __USE_MINGW_ANSI_STDIO is defined in any case to zero or one, isn't
> it?
If you are referring to
Ok, add it to our _mingw.h file, too. We can then simplify our logic
in our _mingw_printf_(push/pop).h headers, too, as we know that
__USE_MINGW_ANSI_STDIO is defined in any case to zero or one, isn't
it?
Cheers,
Kai
2009/9/19 Ozkan Sezer :
> On Sat, Sep 19, 2009 at 1:13 PM, Erik de Castro Lopo
>
On Sat, Sep 19, 2009 at 1:13 PM, Erik de Castro Lopo
wrote:
> Ozkan Sezer wrote:
>
>> You need it with both. (Although, if your w32 toolchain is
>> a mingw.org toolchain and not ours, they may have automatically
>> defined __USE_MINGW_ANSI_STDIO as 1 upon seeing -std=c99. Kai,
>> should we do th
Ozkan Sezer wrote:
> You need it with both. (Although, if your w32 toolchain is
> a mingw.org toolchain and not ours, they may have automatically
> defined __USE_MINGW_ANSI_STDIO as 1 upon seeing -std=c99. Kai,
> should we do that?)
Yes, please!
Cheers,
Erik
--
---
On Sat, Sep 19, 2009 at 11:02 AM, Erik de Castro Lopo
wrote:
> Ozkan Sezer wrote:
>
>> Hmm, with my versions gcc-4.4.2 (svn r151768, patched but
>> nothing that would affect this) and mingw-w64 r1375-r1378,
>> I get:
>>
>> x86_64-pc-mingw32-gcc -Wall -std=gnu99 test.c
>> test.c: In function 'main'
Ozkan Sezer wrote:
> Hmm, with my versions gcc-4.4.2 (svn r151768, patched but
> nothing that would affect this) and mingw-w64 r1375-r1378,
> I get:
>
> x86_64-pc-mingw32-gcc -Wall -std=gnu99 test.c
> test.c: In function 'main':
> test.c:6: warning: unknown conversion type character 'z' in format
11 matches
Mail list logo
