On 28/06/2011, at 9:26 AM, Rodrigo Rosa wrote:

> i tried
> ./configure --enable-mantainer-mode  --enable-ft2232-libftdi
> --host=x86_64-w64-mingw32 CFLAGS=-D__MINGW32__
> 
> and i got a bit further, now i'm stuck with this:
> .
> .
> .
> jim-eventloop.o jim-eventloop.c
> jim-eventloop.c:53:21: error: windows.h: No such file or directory
> jim-eventloop.c:54:21: error: winsock.h: No such file or directory
> jim-eventloop.c: In function ‘JimELAfterCommand’:
> jim-eventloop.c:637: warning: implicit declaration of function ‘Sleep’
> make[2]: *** [jim-eventloop.o] Error 1
> .
> .
> .
> 
> can i solve that with another configure param?
> the files are at
> /usr/amd64-mingw32msvc/include/
> and at
> /usr/i586-mingw32msvc/include/
> 
> and it does not complain about the Sleep if i change the define at
> jim-eventloop.c:55 to:
> #define msleep sleep
> (instead of #define msleep Sleep)
> 
> thanks!

It's obviously going to need some work.
What platform are you building on?
What mingw packages are you using?

Cheers,
Steve

> 
> On Mon, Jun 27, 2011 at 3:11 PM, Steve Bennett <[email protected]> wrote:
>> On 28/06/2011, at 6:33 AM, Rodrigo Rosa wrote:
>> 
>>> i'm trying to cross compile for win XP, with the following config:
>>> ./configure --enable-mantainer-mode  --enable-ft2232-libftdi
>>> --host=x86_64-w64-mingw32
>>> 
>>> i get the following errors:
>>> jim-win32compat.c: In function ‘gettimeofday’:
>>> jim-win32compat.c:36: error: storage size of ‘tb’ isn’t known
>>> jim-win32compat.c:38: warning: implicit declaration of functgpion ‘_ftime’
>>> jim-win32compat.c:36: warning: unused variable ‘tb’
>>> jim-win32compat.c: At top level:
>>> jim-win32compat.c:58: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
>>> ‘__attribute__’ before ‘*’ token
>>> jim-win32compat.c:91: error: expected ‘)’ before ‘*’ token
>>> jim-win32compat.c:106: error: expected ‘)’ before ‘*’ token
>>> 
>>> i've attached the configure output.
>>> 
>>> i've never done cross compiling before, so any help is welcome.
>>> 
>>> thanks!
>> 
>> It seems that the __MINGW32__ symbol isn't defined. It should be.
>> Perhaps add CFLAGS=-D__MING32__ to the configure line and see if that gets 
>> you any further.
>> 
>> Cheers,
>> Steve
>> 
>>> On Mon, Jun 13, 2011 at 3:49 PM, Liam Redmond (Rock Software)
>>> <[email protected]> wrote:
>>>> It has been a while and I think my msys is quite out of date. Have reverted
>>>> to building on Linux.
>>>> 
>>>> Thanks.
>>>> 
>>>> ----- Original Message ----- From: "Freddie Chopin" <[email protected]>
>>>> To: <[email protected]>
>>>> Sent: Monday, June 13, 2011 4:22 PM
>>>> Subject: Re: [Openocd-development] Status of building using Mingw64?
>>>> 
>>>> 
>>>>> OpenOCD versions from my website ( www.freddiechopin.info ) - 32- and
>>>>> 64-bit, the most recent one is a week old - are built with this compiler,
>>>>> but with the most recent version (GCC 4.7.0) and on Linux, as I found that
>>>>> easier than using Cygwin or MSYS directly in Windows.
>>>>> 
>>>>> 4\/3!!
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Openocd-development mailing list
>>>>> [email protected]
>>>>> https://lists.berlios.de/mailman/listinfo/openocd-development
>>>> 
>>>> _______________________________________________
>>>> Openocd-development mailing list
>>>> [email protected]
>>>> https://lists.berlios.de/mailman/listinfo/openocd-development
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Rodrigo.
>>> <configure_make>_______________________________________________
>>> Openocd-development mailing list
>>> [email protected]
>>> https://lists.berlios.de/mailman/listinfo/openocd-development
>> 
>> --
>> µWeb: Embedded Web Framework - http://uweb.workware.net.au/
>> WorkWare Systems Pty Ltd
>> W: www.workware.net.au      P: +61 434 921 300
>> E: [email protected]   F: +61 7 3391 6002
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> 
> -- 
> Rodrigo.
> 

--
µWeb: Embedded Web Framework - http://uweb.workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au      P: +61 434 921 300
E: [email protected]   F: +61 7 3391 6002





_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to