Re: [Mingw-w64-public] error: unknown type name 'VIDEO_STREAM_CONFIG_CAPS'

2012-05-22 Thread Ozkan Sezer
On Wed, May 23, 2012 at 6:02 AM, Phillip Hellewell wrote: > Phillip Hellewell writes: >> >> I'm not sure that's the whole story. I think there may be an issue with >> strmif.h. >> > > FYI, I don't know if this was the right fix, but I moved the > VIDEO_STREAM_CONFIG_CAPS struct and AUDIO_STREAM_C

Re: [Mingw-w64-public] error: unknown type name 'VIDEO_STREAM_CONFIG_CAPS'

2012-05-22 Thread Phillip Hellewell
Phillip Hellewell writes: > > I'm not sure that's the whole story. I think there may be an issue with > strmif.h. > FYI, I don't know if this was the right fix, but I moved the VIDEO_STREAM_CONFIG_CAPS struct and AUDIO_STREAM_CONFIG_CAPS below it to just above the #ifndef __IAMStreamConfig_INTE

Re: [Mingw-w64-public] error: unknown type name 'VIDEO_STREAM_CONFIG_CAPS'

2012-05-22 Thread Phillip Hellewell
Ozkan Sezer writes: > > That's because your libavdevice/dshow.h is misfortunately named > "dshow.h". It is attempting to include system's dshow.h by an > #include directive, which is wrong: you should use #include_next > instead (or rename the header). If system's dshow.h is included, > it incl

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Antony Riakiotakis
On 22 May 2012 20:10, Antony Riakiotakis wrote: > I mean in terms of processors supported by the compiler itself. As far > as operating systems go we support up to windows 2000 I think? Not > quite sure. Bad phrasing, compiler supports all processors: I meant processors that the compile is able t

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Antony Riakiotakis
I mean in terms of processors supported by the compiler itself. As far as operating systems go we support up to windows 2000 I think? Not quite sure. -- Live Security Virtual Conference Exclusive live event will cover all

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Earnie Boyd
On Tue, May 22, 2012 at 9:06 AM, Ruben Van Boxem wrote: > > My new builds (along with the 4.5.3) will be built with > -march=nocona -mtune=core2 > Have you considered passing the options directly to the assembler. You can be specific with your refinements of the extensions added. -- Earnie -- h

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Earnie Boyd
On Tue, May 22, 2012 at 10:13 AM, Antony Riakiotakis wrote: >  Personally I don't mind using a toolchain with sse3 support > requirements but we have a policy towards backwards compatibility for > the program itself going back to 32 bit single core systems. For the > build systems I am not sure...

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Antony Riakiotakis
Hi, Trying your latest 4.7 build here without problems (on an i5 :) ).Looks like indeed I had -march in mind when criticizing the use of -mtune. The two are similar but -march impiles -mtune rather than the opposite. Personally I don't mind using a toolchain with sse3 support requirements but we

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Ruben Van Boxem
2012/5/22 Antony Riakiotakis > Hi, thanks for the quick response. I will try to get a backtrace > though last time I tried I remember I got some assembly mumbo-jumbo, > related to openmp for certain(If memory serves right, something like > omp_get_thread_name hit a null pointer or something simil

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Antony Riakiotakis
Hi, thanks for the quick response. I will try to get a backtrace though last time I tried I remember I got some assembly mumbo-jumbo, related to openmp for certain(If memory serves right, something like omp_get_thread_name hit a null pointer or something similar). Unfortunately I don't have a unix

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Ruben Van Boxem
2012/5/22 Antony Riakiotakis > Hi Ruben, I have been looking into some openmp crashes we've had with > blender and i have read the info in your first email on this thread. > It looks like we may have been experiencing the same problem > unfortunately. We are using the ray-linn build so if the def

Re: [Mingw-w64-public] rubenvb GCC 4.7.0 release build

2012-05-22 Thread Antony Riakiotakis
Hi Ruben, I have been looking into some openmp crashes we've had with blender and i have read the info in your first email on this thread. It looks like we may have been experiencing the same problem unfortunately. We are using the ray-linn build so if the default behaviour is this for every MinGW6