Re: [Mingw-w64-public] Unable to link OpenCL for i686

Nakai, Does that imply that there is something wrong with the .def file? I added -A and -k and still get the same error. Thanks, Kyle -Original Message- From: Nakai Yuta [mailto:nak5...@live.jp] Sent: Saturday, September 5, 2015 1:50 AM To: mingw-w64-public@lists.sourceforge.net Subj

[Mingw-w64-public] Unable to link OpenCL for i686

I'm unable to link OpenCL for i686, but x86_64 works. I'm creating the library files (.a) from a def file using dlltool. The def file and headers come from the ICD archive found here: https://www.khronos.org/registry/cl/ I'm attempting to run the following bash compile script: for arch in "i686"

[Mingw-w64-public] GStreamer Crash

I'm trying to cross compile GStreamer 1.0.6 with the latest version of MinGW-w64. I keep getting an instant crash when trying to run GStreamer under Wine. Here is the output from Wine: > wine ./gst-inspect-1.0.exe > ALSA lib ../../../src/seq/seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq > fa

Re: [Mingw-w64-public] undefined reference to `opj_version'

On 12/10/2012 1:52 PM, Ruben Van Boxem wrote: > Are you using the binary package on their website? > > I just compiled openjpeg with both my x64 and x86 compilers and I get no > undefined references. Running "nm" on the produced libopenjp2.dll.a > gives me: > I __imp__opj_version@0 > 0

[Mingw-w64-public] undefined reference to `opj_version'

I'm trying to compile an example program that uses openjpeg 2.0.0 and am getting an undefined reference to `opj_version'. I'm using the latest MinGW-w64 svn along with gcc 4.7.2. The example program is: extern int opj_version(); int main(void){ opj_version(); } I'm compiling it with: i686-w64-m

[Mingw-w64-public] error: Link tests are not allowed after GCC_NO_EXECUTABLES.

ges/gcc/packages/ppl/ppl-1.0-x86_64 --with-isl=/home/kyle/software/mingw-w64/packages/gcc/packages/isl/isl-0.10-x86_64 --enable-threads=win32 --enable-fully-dynamic-string --enable-languages=c,c++,lto --program-transform-name=s&^&i686-w64-mingw32-& --disable-opti

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

rmance-issue-question-maybe-my-misunderstanding-td4652757.html > which makes me wonder if it's stuck in a spinlock or something (his > still progress fine, though, I'd imagine...) Ping? Any help/info/updates on this issue would be

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

if I compiled a debug version of x264 to test with? The threading issue might just be in x264, so having only x264 and not FFmepg might help. Any ideas are welcome. Best regards, Kyle Schwarz -- Live Security Vi

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

h a build that is compiled with -pg. I'm a bit rusty in C, but I'm very motivated to fix this so just walk me though anything you would like tested and I'll see that it's done. > Have you used gprof before? It can be daunting

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

On 8/8/2012 8:49 PM, Kyle wrote: > On 8/7/2012 3:06 AM, Kai Tietz wrote: >> 2012/8/7 Kyle Schwarz : >>> On 8/6/2012 4:58 PM, Kai Tietz wrote: >>>> I have attached a modified version of winpthread (uncomress it and >>>> rename it back to .dll). It would be

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

I copied the libwinpthread-1.dll you sent into the debug build and replaced the old one. I had the same issue. Do I need to recompile x264+FFmpeg with the new libwinpthread-1.dll? Any idea as to what it might be? Best regards, Kyl

Re: [Mingw-w64-public] apparent "hang" using the experimental pthread library

take? If winpthreads are no longer the best option I'm just curious as to if it's worth it to try other options. I'm available to test any sort of patch that is believed to help. I strongly support MinGW-w64 and winpthreads. Best regards, Kyle Schwarz --

Re: [Mingw-w64-public] experimental/winpthreads/src/version.rc:36: syntax error

On 7/27/2012 4:03 PM, Kai Tietz wrote: > 2012/7/27 niXman : >> 2012/7/27 Kyle Schwarz: >>> Hi, >>> >>> I'm getting a syntax error when trying to compile the latest winpthread. >> >> Hmm... This is strange. I've built winpthreads a hour ago

[Mingw-w64-public] experimental/winpthreads/src/version.rc:36: syntax error

gards, Kyle Schwarz -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoin

Re: [Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

On Sat, Sep 10, 2011 at 3:55 PM, Kai Tietz wrote: > 2011/9/10 Kyle : >> On 9/10/2011 6:52 AM, PcX wrote: >> >> 于 2011/9/10 18:51, PcX 写道: >> >> i686-w64-mingw32-gcc -Wl,--as-needed -Wl,--warn-common >> -Wl,-rpath-link=libpostproc:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil

[Mingw-w64-public] ffmpeg.c:4492: undefined reference to `_avdevice_register_all'

I'm having issues compiling FFmpeg for Windows with MinGW-w64. I'm using the latest MinGW-w64 and the latest FFmpeg. A bug report can be found here: https://ffmpeg.org/trac/ffmpeg/ticket/282 A mailing list post can be found here: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2011-September/00224