Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 Eric Blake <eblake(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=599227 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 Paolo Bonzini <pbonzini(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |641423 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 Paolo Bonzini <pbonzini(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pbonzini(a)redhat.com --- Comment #3 from Paolo Bonzini <pbonzini(a)redhat.com&gt; 2010-10-09 05:52:59 EDT --- ... however, since libgomp should be required by gcc, fixing this bug would require splitting mingw packages in a "deployment" part and a "devel" part. This way, gcc would bring in mingw32-pthreads but not mingw32-pthreads-devel. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 Paolo Bonzini <pbonzini(a)redhat.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|mingw32-gcc should not drag |mingw32-gcc should not drag |in mingw32-pthreads |in pthreads.h because it's | |buggy --- Comment #5 from Paolo Bonzini <pbonzini(a)redhat.com&gt; 2010-10-11 06:13:18 EDT --- The problem here is having mingw32-libgomp (bug 641423) would only be one step towards fixing the problem. The hypothetical mingw32-libgomp package would still be required by mingw32-gcc (like libgomp is required by gcc for native compilation), so you would still have an indirect dependency mingw32-gcc -> mingw32-libgomp -> mingw32-pthreads However, the real bug here is mingw32-gcc dragging in pthreads.h. And pthreads.h is _not_ required to build OpenMP programs; this is why separating the runtime and devel parts would fix the bug: mingw32-gcc -> mingw32-libgomp -> mingw32-pthreads (pthreadgc*2.dll) | `----> mingw32-pthreads-devel (BuildRequires) That said, rereading Eric's bug report: Since pthreads.h common under POSIX systems, pthreads.h can be a possible source of problems _anyway_ when cross-compiling. With a separate mingw32-pthreads-devel package, the pthreads.h bug that prompted this report would have showed up only for those people who installed mingw32-pthreads-devel. It would have showed up anyway, but likely only later; and I suspect it would have been harder to track it down. So maybe it's better to have the header uniformly installed and close this bug as WONTFIX? (BTW, I also agree that the behavior of lt_cv_deplibs_check_method=pass_all is too tricky and it is probably a bad idea to have it in the RPM macros. Libtool behavior for Windows is sometimes confusing but at least it is safe). -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 --- Comment #7 from Daniel Berrange <berrange(a)redhat.com&gt; 2010-10-11 08:35:20 EDT --- Having a separate '-devel' package seems wrong to me. All mingw32 packages are essentially '-devel' packages, which is why our packaging guidelines never suggest actually creating -devel packages. The 3rd option would be to try and fix pthreads.h so that it doesn't pollute the global namespace. I recall seeing some patches that do this in some other project's mingw32 packages, but I can't find the link right now. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 --- Comment #9 from Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl&gt; 2011-01-28 10:07:28 EST --- I'm currently working on a new Fedora feature called the cross compiler framework. This will be the successor to the MinGW toolchain in Fedora. It will be based on the mingw-w64 project (instead of the mingw.org one) and will use gcc 4.6. With this framework it will be possible to easily build binaries for Win32, Win64 and in the future Mac OS X (depending on legal issues) For that toolchain I've moved the libgomp pieces from the gcc package to a separate subpackage. With gcc 4.6 gcc itself doesn't have a hard dependency on libgomp anymore. So whenever one tries to install 'mingw32-gcc' or 'mingw32-gcc-c++' the libgomp pieces (and thus pthreads) won't be pulled in any more. People who really need libgomp support can install the package manually. I've tried rebuilding all 96 mingw32 packages which are now in Fedora using this method and everything built succesfully without pulling in libgomp More details about the cross compiler framework can be found at https://fedoraproject.org/wiki/MinGW/CrossCompilerFramework and on the Fedora mingw mailing list -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=599567 Kalev Lember <kalev(a)smartlink.ee&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Version|13 |rawhide Resolution| |RAWHIDE Last Closed| |2011-05-12 13:25:08 --- Comment #11 from Kalev Lember <kalev(a)smartlink.ee&gt; 2011-05-12 13:25:08 EDT --- I just built mingw32-pthreads-2.8.0-15.20110511cvs.fc16 for rawhide which should fix the issues mentioned in bug #599227. I am hoping that the <pthread.h> header is now in good enough condition so that it's no longer an issue if gcc install drags it in. Closing the ticket, thanks. Please mention in bug #599227 if there are any more issues with the pthread.h header. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.redhat.com/show_bug.cgi?id=599567 Bug 599567 depends on bug 641423, which changed state. Bug 641423 Summary: mingw32-gcc installs files both inside and outside the sysroot https://bugzilla.redhat.com/show_bug.cgi?id=641423 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution|--- |EOL -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=eMI8pi5jZA&a=cc_unsubscribe