Ken Taylor wrote:
> Another problem, this one also apparently Reed's fault (j/k), and this time
> actually crashing the compiler!
> 

Wow, crashed the compiler!

Actually this is actually something you can fault me with, since I 
probably messed up with the dllimport/dllexport declarations. Or, blame 
Windows for requiring that stuff and making it a pain in the neck.

I'll look into it.

Reed


> 
> g++ -DHAVE_CONFIG_H -I. -I. -I../../../libs/vos -I../../../libs -I../../../i
> nplace/include -DVOS_EXPORTS -D_REENTRANT -D_MT -mthreads -I/c/vos-projects/
> current/vos/inplace/include -D_REENTRANT -O1 -D_REENTRANT -D_MT -mthreads -g
>  -Wall -I/c/vos-projects/current/vos/inplace/include -MT
> dateformatfilter.lo -MD -MP -MF .deps/dateformatfilter.Tpo -c
> dateformatfilter.cc  -DDLL_EXPORT -DPIC -o .libs/dateformatfilter.o
> dateformatfilter.cc:9: warning: function
> 'DateFormatter::DateFormatter(VOS::VobjectBase*)' is defined after prior
> declaration as dllimport: attribute ignored
> dateformatfilter.cc: In constructor
> `DateFormatter::DateFormatter(VOS::VobjectBase*)':
> dateformatfilter.cc:227: internal compiler error: in rest_of_handle_final,
> at toplev.c:2064
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.mingw.org/bugs.shtml> for instructions.
> 
> 
> I'm really not sure what's going on here....
> 
> -Ken
> 
> ----- Original Message ----- 
> From: "Reed Hedges" <[EMAIL PROTECTED]>
> To: "VOS Discussion" <vos-d@interreality.org>
> Sent: Saturday, February 24, 2007 8:05 AM
> Subject: Re: [vos-d] Compiling 0.24 with mingw on windows2000
> 
> 
>> Peter Amstutz wrote:
>>> Uh oh.  Blame Reed.  And the fact that I haven't actually built VOS on
>>> Windows for a while...  That particular file was just added recently.  I
>>> need to set up a dedicated Windows box for development so I don't have
>>> to reboot my main machine (which is Linux).  Perhaps I should get up
>>> boot camp and dual boot my MacBook...
>>>
>>> Unless Reed can give you a more specific answer about strftime_r, I'll
>>> have to take when I get around to it.  The worst case scenario may be
>>> that you can #ifdef out the offending lines, as it is probably only
>>> necessary for very specific non-core functionality.
>> Yeah, that's just a hack to set the timezone used by strftime(). (Anyone
>> know if there's a better way to do that?).  You can just put #ifndef
>> WIN32 around those calls in strftime_r.c if you want.
>>
>> However, I'm pretty sure that getenv and setenv exist on MinGW
>> somewhere. strftime_r.h includes stdlib.h but maybe on MinGW they're
>> actually in unistd.h, or maybe even in windows.h or something.
>>
>> Reed
>>
>> _______________________________________________
>> vos-d mailing list
>> vos-d@interreality.org
>> http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
>>
> 
> 
> _______________________________________________
> vos-d mailing list
> vos-d@interreality.org
> http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d


_______________________________________________
vos-d mailing list
vos-d@interreality.org
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d

Reply via email to