Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [abrt] mingw32-binutils-2.19.51.0.14-1.fc12: pe_implied_import_dll: Process /usr/i686-pc-mingw32/bin/ld was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=633846
Summary: [abrt] mingw32-binutils-2.19.51.0.14-1.fc12:
pe_implied_import_dll: Process
/usr/i686-pc-mingw32/bin/ld was killed by signal 11
(SIGSEGV)
Product: Fedora
Version: 13
Platform: x86_64
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:c2017a691dd6713c319ddb7df56a5c5e8dfb1ea0
Severity: medium
Priority: low
Component: mingw32-binutils
AssignedTo: rjones(a)redhat.com
ReportedBy: gilboad(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, kalev(a)smartlink.ee,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline:
/usr/lib64/gcc/i686-pc-mingw32/4.4.2/../../../../i686-pc-mingw32/bin/ld
--sysroot=/usr/i686-pc-mingw32/sys-root --subsystem console -Bdynamic -o
obj/windows-mingw-user/i686/release/spkinstall.exe
/usr/i686-pc-mingw32/sys-root/mingw/lib/crt2.o
/usr/lib64/gcc/i686-pc-mingw32/4.4.2/crtbegin.o
-L/home/gilboa/work/OSS/SVN/SPK/output/windows-mingw-user/i686/lib
-L/home/gilboa/work/OSS/SVN/SPK/output/windows-mingw-user/i686/bin
-L/usr/lib64/gcc/i686-pc-mingw32/4.4.2
-L/usr/lib64/gcc/i686-pc-mingw32/4.4.2/../../../../i686-pc-mingw32/lib
-L/usr/i686-pc-mingw32/sys-root/mingw/lib -lstdc++ -lansi7zip -lzlibm -lspk
obj/windows-mingw-user/i686/release/spkinstall.o -lstdc++ -lmingwthrd -lmingw32
-lgcc_eh -lgcc -lmoldname -lmingwex -lmsvcrt -luser32 -lkernel32 -ladvapi32
-lshell32 -lmingwthrd -lmingw32 -lgcc_eh -lgcc -lmoldname -lmingwex -lmsvcrt
/usr/lib64/gcc/i686-pc-mingw32/4.4.2/crtfastmath.o
/usr/lib64/gcc/i686-pc-mingw32/4.4.2/crtend.o
component: mingw32-binutils
crash_function: pe_implied_import_dll
executable: /usr/i686-pc-mingw32/bin/ld
kernel: 2.6.34.6-54.fc13.x86_64
package: mingw32-binutils-2.19.51.0.14-1.fc12
rating: 4
reason: Process /usr/i686-pc-mingw32/bin/ld was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1284474412
uid: 800
comment
-----
I'm helping a friend port his project to Linux, moving it my my build system.
(Which supports gcc, mingw and VS)
Attempting to build the project using mingw causes gcc to crash during link.
The same project builds just fine under gcc/Linux.
I suspect that something is broken with the generated DLL.
I'm waiting for his approval before sending upload a tarball of the offending
code.
(Most likely something in my own build system is the cause of the problem.)
- Gilboa
How to reproduce
-----
1. Build project.
--
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.
Summary: Internal error: Segmentation fault (program ld) when compiling Google Go
https://bugzilla.redhat.com/show_bug.cgi?id=643801
Summary: Internal error: Segmentation fault (program ld) when
compiling Google Go
Product: Fedora
Version: 13
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mingw32-gcc
AssignedTo: rjones(a)redhat.com
ReportedBy: fullung(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, kalev(a)smartlink.ee,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Description of problem:
mingw32-gcc's ld segfaults when compiling Google Go.
Version-Release number of selected component (if applicable):
mingw32-gcc-4.4.2-2.fc13.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Read http://golang.org/doc/install.html
2. hg clone -r release https://go.googlecode.com/hg/ go (might need tip)
3. cd go
4. hg patch --no-commit go_make_mingw.diff
5. cd src
6. AR=i686-pc-mingw32-ar GOHOSTARCH=386 CC=i686-pc-mingw32-gcc GOOS=windows
GOARCH=386 ./make.bash
Actual results:
quietgcc -o 8g -L"/home/alberts/go"/lib ../8l/enam.o list.o galign.o gobj.o
ggen.o gsubr.o cgen.o cgen64.o cplx.o peep.o reg.o ../gc/gc.a -lbio -l9 -lm
i686-pc-mingw32-gcc: Internal error: Segmentation fault (program ld)
Please submit a full bug report.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Expected results:
8g command should compile
Additional info:
--
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.
Summary: CVE-2010-2249 libpng: Memory leak when processing Physical Scale (sCAL) images [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=609162
Summary: CVE-2010-2249 libpng: Memory leak when processing
Physical Scale (sCAL) images [fedora-all]
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Keywords: Security, SecurityTracking
Severity: low
Priority: low
Component: mingw32-libpng
AssignedTo: rjones(a)redhat.com
ReportedBy: jlieskov(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: lfarkas(a)lfarkas.org, rjones(a)redhat.com,
erik-fedora(a)vanpienbroek.nl,
fedora-mingw(a)lists.fedoraproject.org
Blocks: 608644
Classification: Fedora
Target Release: ---
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora
versions.
For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.
Forr more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please include the bug IDs of the
respective parent bugs filed against the "Security Response" product.
Please mention CVE ids in the RPM changelog when available.
Bodhi update submission link:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=608644
Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please only close it when all
affected versions are fixed.
[bug automatically created by: add-tracking-bugs]
--
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.
Summary: routeprot.h has bug related to IP_LOCAL_BINDING
https://bugzilla.redhat.com/show_bug.cgi?id=680583
Summary: routeprot.h has bug related to IP_LOCAL_BINDING
Product: Fedora
Version: 13
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: mingw32-w32api
AssignedTo: rjones(a)redhat.com
ReportedBy: greearb(a)candelatech.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, kalev(a)smartlink.ee,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Description of problem:
It seems IP_LOCAL_BINDING is defined after it is used.
Version-Release number of selected component (if applicable):
mingw32-w32api-3.13-5.fc13.noarch
How reproducible:
Always
Steps to Reproduce:
1. Try to compile something that uses routprot.h
2.
3.
Actual results:
In file included from
fea/data_plane/fibconfig/fibconfig_entry_get_iphelper.cc:34:
/usr/i686-pc-mingw32/sys-root/mingw/include/routprot.h:51: error:
'IP_LOCAL_BINDING' does not name a type
scons: ***
[obj/i386-pc-mingw32/fea/data_plane/fibconfig/fibconfig_entry_get_iphelper.o]
Error 1
scons: building terminated because of errors.
Expected results:
Sweet binary goodness.
Additional info:
This seems to fix things:
diff --git a/routprot.h.orig b/routprot.h
index 54fe9ee..2b57df8 100644
--- a/routprot.h.orig
+++ b/routprot.h
@@ -43,6 +43,11 @@ extern "C" {
#define IPX_PROTOCOL_NLSP 0x00020002
/*--- Router Management Reference - Router Management Structures */
#if (_WIN32_WINNT >= 0x0500)
+typedef struct IP_LOCAL_BINDING {
+ DWORD Address;
+ DWORD Mask;
+} IP_LOCAL_BINDING,*PIP_LOCAL_BINDING;
+
typedef struct IP_ADAPTER_BINDING_INFO {
ULONG AddressCount;
DWORD RemoteAddress;
@@ -50,10 +55,7 @@ typedef struct IP_ADAPTER_BINDING_INFO {
ULONGLONG Speed;
IP_LOCAL_BINDING Address[];
} IP_ADAPTER_BINDING_INFO,*PIP_ADAPTER_BINDING_INFO;
-typedef struct IP_LOCAL_BINDING {
- DWORD Address;
- DWORD Mask;
-} IP_LOCAL_BINDING,*PIP_LOCAL_BINDING;
+
typedef struct IPX_ADAPTER_BINDING_INFO {
ULONG AdapterIndex;
UCHAR Network[4];
--
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.
Summary: gcc driver does not pass needed libraries for libgcc_eh.a on collect2 command line
https://bugzilla.redhat.com/show_bug.cgi?id=677153
Summary: gcc driver does not pass needed libraries for
libgcc_eh.a on collect2 command line
Product: Fedora
Version: rawhide
Platform: All
OS/Version: All
Status: NEW
Severity: medium
Priority: unspecified
Component: mingw32-gcc
AssignedTo: rjones(a)redhat.com
ReportedBy: t.sailer(a)alumni.ethz.ch
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, kalev(a)smartlink.ee,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Description of problem:
libgcc_eh.a sometimes needs symbols from libmingw32.a (___mingwthr_key_dtor)
and libkernel32.a (_SetLastError@4, _InterlockedIncrement@4, _TlsAlloc@0,
_TlsSetValue@8), but does not pass -lmingw32 -lkernel32 to collect2 after
-lgcc_eh. The result is that, when compiling glib2-2.28.0, linking
glib-compile-schemas.exe fails; I had to manually call collect2 with added
arguments to make the mingw32-glib2 rpm build.
Version-Release number of selected component (if applicable):
mingw32-gcc-4.5.1-2.fc15
How reproducible:
always
Steps to Reproduce:
see for example the mingw32-glib2-2.28.0-1.fc16.src.rpm and remove the two
lines marked with "evil hack".
Actual results:
Missing symbols during linking of gio/glib-compile-schemas.exe
Expected results:
Linking succeeds
--
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.
Summary: mingw32 produced DLL's are not stripped
https://bugzilla.redhat.com/show_bug.cgi?id=571686
Summary: mingw32 produced DLL's are not stripped
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mingw32-filesystem
AssignedTo: rjones(a)redhat.com
ReportedBy: waananen(a)nbi.dk
QAContact: extras-qa(a)fedoraproject.org
CC: berrange(a)redhat.com, rjones(a)redhat.com,
erik-fedora(a)vanpienbroek.nl,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Description of problem:
Even if the specfile includes:
%define __strip %{_mingw32_strip}
mingw32 cross-compiled packages does not get their DLL's or binaries
stripped.
Version-Release number of selected component (if applicable):
Checked with:
mingw32-filesystem-56-1
How reproducible:
Very easy to reproduce by building a mingw32 package. Also official Fedora
mingw32 packages are not stripped either - I tested the package:
mingw32-pixman-0.14.0-1.fc11.
Steps to Reproduce:
1. cp -p /usr/i686-pc-mingw32/sys-root/mingw/bin/libpixman-1-0.dll /tmp
2. i686-pc-mingw32-strip /tmp/libpixman-1-0.dll
Actual results:
# ls -1s /usr/i686-pc-mingw32/sys-root/mingw/bin/libpixman-1-0.dll
/tmp/libpixman-1-0.dll
252 /tmp/libpixman-1-0.dll
1252 /usr/i686-pc-mingw32/sys-root/mingw/bin/libpixman-1-0.dll
Expected results:
# ls -1s /usr/i686-pc-mingw32/sys-root/mingw/bin/libpixman-1-0.dll
/tmp/libpixman-1-0.dll
252 /tmp/libpixman-1-0.dll
252 /usr/i686-pc-mingw32/sys-root/mingw/bin/libpixman-1-0.dll
Additional info:
--
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.
Summary: mingw <pthread.h> is broken
https://bugzilla.redhat.com/show_bug.cgi?id=599227
Summary: mingw <pthread.h> is broken
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mingw32-pthreads
AssignedTo: rjones(a)redhat.com
ReportedBy: eblake(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: lfarkas(a)lfarkas.org, berrange(a)redhat.com,
rjones(a)redhat.com, erik-fedora(a)vanpienbroek.nl,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
The cross-compilation header
/usr/i686-pc-mingw32/sys-root/mingw/include/pthread.h, installed as part of the
mingw32-pthreads package, has several coding bugs.
Version-Release number of selected component (if applicable):
mingw32-pthreads-2.8.0-10.fc13.noarch
How reproducible:
Always
Steps to Reproduce:
1. Try cross-compiling any code that uses localtime_r with a second argument
with side effects, or try calling (localtime_r)(arg1,arg2).
2. Try cross-compiling any project that uses gnulib's <time.h> replacement
header (libvirt is an example project; it includes a ./autobuild.sh script that
will automatically try a mingw cross-compilation, if you have installed a mingw
portablexdr library, although that library is not yet part of fedora).
Actual results:
The definition of localtime_r is broken, because it evaluates the second
argument twice. And, since POSIX allows one to #undef localtime_r, but there
is no localtime_r function in the library, you get a link failure if you bypass
the function-like macro. Finally, the pthreads-win32 library made the mistake
of installing <config.h>, which is asking for namespace collision with most
other autotooled packages.
Expected results:
<pthread.h> should not define any *_r functions, nor should it interfere with a
proper <time.h>. Also, the library should not install <config.h>, but should
instead modify its installed headers to be self-contained.
Additional info:
See this thread on bug-gnulib for more details:
http://lists.gnu.org/archive/html/bug-gnulib/2010-06/msg00007.html
--
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.
Summary: Update mingw32-runtime to 3.18
https://bugzilla.redhat.com/show_bug.cgi?id=629209
Summary: Update mingw32-runtime to 3.18
Product: Fedora
Version: 14
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mingw32-runtime
AssignedTo: rjones(a)redhat.com
ReportedBy: atkac(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, kalev(a)smartlink.ee,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
When I compile TigerVNC vncviewer for Windows on Fedora 14/rawhide, output
vncviewer.exe binary is broken:
...
Backtrace:
=>0 0x00485e4f in vncviewer (+0x85e4f) (0x00a0fe30)
1 0x0040108d __mingw_CRTStartup+0x6c()
[/builddir/build/BUILD/mingwrt-3.15.2-mingw32/crt1.c:217] in vncviewer
(0x00a0fe70)
2 0x0040108d __mingw_CRTStartup+0x6c()
[/builddir/build/BUILD/mingwrt-3.15.2-mingw32/crt1.c:217] in vncviewer
(0x00a0fe90)
3 0x00401128 WinMainCRTStartup+0x17()
[/builddir/build/BUILD/mingwrt-3.15.2-mingw32/crt1.c:271] in vncviewer
(0x00a0fea8)
4 0x7ede70bc call_process_entry+0xb() in kernel32 (0x00a0fee8)
5 0x7efab570 call_thread_func+0xb() in ntdll (0x00a0fef8)
6 0x7efae1f1 call_thread_entry_point+0x70() in ntdll (0x00a0ffc8)
7 0x7ef83feb call_dll_entry_point+0x65a() in ntdll (0x00a0ffe8)
...
When I updated to the latest mingw runtime from upstream
(mingwrt-3.18-mingw32-src) everything works fine.
Version-Release number of selected component (if applicable):
mingw32-runtime-3.15.2-5.fc13
How reproducible:
always
Steps to Reproduce:
1. compile program for Windows via MinGW build chain
2. run it
Actual results:
crash
Expected results:
working binary
Additional info:
It seems current mingw runtime is not compatible with gcc 4.5. As I wrote above
when I update to 3.18 version, problem disappears.
--
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.
Hi,
Recently I was browsing the upstream GTK website and I noticed that
upstream has used a special trick to build the Win32 binaries for GLib.
In order to make the dependency on gettext a soft one they used a small
static wrapper library called libproxy-intl [1]. With this wrapper
library the GLib DLL doesn't depend directly anymore on libintl-8.dll
(from mingw32-gettext). The wrapper library makes the hard dependency a
runtime one. This means that if libintl-8.dll is bundled with the
application then gettext translations will be used, otherwise nothing
gets translated.
I'd like to propose that we apply this change as well in our Fedora
MinGW toolchain.
Such a change consists of the following smaller changes:
- Bundle the libproxy-intl code (1 .c file and 1 .h file) in
the mingw32-gettext srpm as additional source files
- Compile the libproxy-intl code with these 2 instructions:
%{_mingw32_cc} -c libintl.c -o libintl.o -I.
%{_mingw32_ar} rc libintl.a libintl.o
- Replace the files libintl.{a,.dll.a,.la} generated by the
gettext compilation with the libintl.a file from libproxy-intl.
This makes any binary which tries to link against mingw32-gettext
using '-lintl' have a soft-dependency on libintl.
After this a simple rebuild of mingw32-glib2 should be sufficient enough
to make mingw32-gettext a soft dependency.
Next to glib2 there are also some other packages which have a hard
dependency on libintl-8.dll:
$ repoquery --whatrequires 'mingw32(libintl-8.dll)'
mingw32-atk-0:1.32.0-1.fc14.noarch
mingw32-gdk-pixbuf-0:2.22.0-1.fc14.noarch
mingw32-glib2-0:2.26.0-1.fc14.noarch
mingw32-gnutls-0:2.6.4-3.fc13.noarch
mingw32-gtk-vnc-0:0.4.1-1.fc14.noarch
mingw32-gtk2-0:2.22.0-1.fc14.noarch
mingw32-gtkhtml3-0:3.32.0-1.fc14.noarch
mingw32-gvnc-0:0.4.1-1.fc14.noarch
mingw32-hunspell-0:1.2.8-11.fc12.noarch
mingw32-libglade2-0:2.6.4-4.fc12.noarch
mingw32-libidn-0:1.14-5.fc12.noarch
Most of these packages (if not all) don't use gettext directly, but get
linked against gettext because of it being mentioned in glib2's
pkgconfig and .la files. A rebuild should be sufficient to replace the
hard dependencies on those packages by soft ones. However, in order to
prevent the libproxy-intl functions from being exported in other DLL's
(as mentioned on [1]) I think it's better drop the reference to libintl
from glib2's pkgconfig and .la files. As most of the packages mentioned
above don't use gettext directly, but the GLib gettext functions to
handle translations this shouldn't cause any major problems.
As the glib2 headers depend on the libintl.h header a 'Requires:
mingw32-gettext' also needs to be added to the mingw32-glib2 package.
I already applied these changes in a testing repository for a generic
cross compiler framework (coming soon!) [2][3] and it works fine there.
Another thing GTK upstream has done in their Win32 binaries is using
win-iconv instead of GNU iconv. I just put up a review request for
mingw32-win-iconv at [4]. Could somebody please review that package?
Does everybody agree to these changes?
Kind regards,
Erik van Pienbroek
[1]: http://www.gtk.org/download-windows.html
[2]: http://svn.openftd.org/svn/fedora_cross
[3]: http://svn.openftd.org/viewvc/Fedora%20Cross%20Compiler%
20Framework/
[4]: https://bugzilla.redhat.com/show_bug.cgi?id=642208