[Bug 633846] New: [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)
by Red Hat Bugzilla
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.
12 years, 9 months
[Bug 643801] New: Internal error: Segmentation fault (program ld) when compiling Google Go
by Red Hat Bugzilla
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.
12 years, 9 months
[Bug 609162] New: CVE-2010-2249 libpng: Memory leak when processing Physical Scale (sCAL) images [fedora-all]
by Red Hat Bugzilla
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.
12 years, 9 months
[Bug 571686] New: mingw32 produced DLL's are not stripped
by Red Hat Bugzilla
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.
12 years, 11 months
[Bug 599227] New: mingw <pthread.h> is broken
by Red Hat Bugzilla
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.
12 years, 11 months
[Bug 629209] New: Update mingw32-runtime to 3.18
by Red Hat Bugzilla
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.
12 years, 11 months
Proposal: drop the hard dependency on mingw32-gettext from mingw32-glib2
by Erik van Pienbroek
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
12 years, 11 months
[Bug 642208] Review Request: mingw32-win-iconv - iconv implementation using Win32 API
by Red Hat Bugzilla
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=642208
amorilia(a)users.sourceforge.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amorilia(a)users.sourceforge.
| |net
--- Comment #1 from amorilia(a)users.sourceforge.net 2010-12-28 09:16:28 EST ---
Beware, this is my very first package review. Feedback on the review by a more
experienced packager is welcome, particularly if I missed any crucial steps.
[+] OK
[!] Needs to be looked into
[/] Not applicable
[*] Overridden by MinGW guidelines
Rpmlint
-------
$ rpmlint mingw32-win-iconv.spec
mingw32-win-iconv.spec: W: invalid-url Source0:
http://win-iconv.googlecode.com/files/win-iconv-0.0.1.tar.bz2 HTTP Error 404:
Not Found
0 packages and 1 specfiles checked; 0 errors, 1 warnings.
$ rpmlint mingw32-win-iconv-0.0.1-1.fc14.src.rpm
mingw32-win-iconv.src: W: invalid-url Source0:
http://win-iconv.googlecode.com/files/win-iconv-0.0.1.tar.bz2 HTTP Error 404:
Not Found
1 packages and 0 specfiles checked; 0 errors, 1 warnings.
Harmless warning, URL works:
$ wget http://win-iconv.googlecode.com/files/win-iconv-0.0.1.tar.bz2
--2010-12-28 11:15:59--
http://win-iconv.googlecode.com/files/win-iconv-0.0.1.tar.bz2
Resolving win-iconv.googlecode.com... 209.85.229.82
Connecting to win-iconv.googlecode.com|209.85.229.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17338 (17K) [application/x-bzip2]
Saving to: “win-iconv-0.0.1.tar.bz2”
100%[======================================>] 17,338 --.-K/s in 0.1s
2010-12-28 11:16:00 (165 KB/s) - “win-iconv-0.0.1.tar.bz2” saved [17338/17338]
$ rpm -i mingw32-win-iconv-0.0.1-1.fc14.src.rpm
$ md5sum win-iconv-0.0.1.tar.bz2
22ee1bbaae404fe34dca835f1c669a1e win-iconv-0.0.1.tar.bz2
$ md5sum ~/rpmbuild/SOURCES/win-iconv-0.0.1.tar.bz2
22ee1bbaae404fe34dca835f1c669a1e
/home/amorilia/rpmbuild/SOURCES/win-iconv-0.0.1.tar.bz2
$ diff mingw32-win-iconv.spec ~/rpmbuild/SPECS/mingw32-win-iconv.spec -s
Files mingw32-win-iconv.spec and
/home/amorilia/rpmbuild/SPECS/mingw32-win-iconv.spec are identical
$ rpmbuild -ba mingw32-win-iconv.spec
...
Build succeeds.
$ rpmlint ~/rpmbuild/RPMS/noarch/mingw32-win-iconv-0.0.1-1.fc14.noarch.rpm
1 packages and 0 specfiles checked; 0 errors, 0 warnings
$ rpmlint
~/rpmbuild/RPMS/noarch/mingw32-win-iconv-debuginfo-0.0.1-1.fc14.noarch.rpm
mingw32-win-iconv-debuginfo.noarch: E: debuginfo-without-sources
1 packages and 0 specfiles checked; 1 errors, 0 warnings.
$ rpmlint
~/rpmbuild/RPMS/noarch/mingw32-win-iconv-static-0.0.1-1.fc14.noarch.rpm
mingw32-win-iconv-static.noarch: E:
arch-independent-package-contains-binary-or-object
/usr/i686-pc-mingw32/sys-root/mingw/lib/libiconv.a
mingw32-win-iconv-static.noarch: W: no-documentation
1 packages and 0 specfiles checked; 1 errors, 1 warnings.
Looks fine, follows MinGW guidelines.
Dependencies
------------
$ su -c 'yum install mingw32-iconv*'
$ rpm -qa | grep mingw32-iconv
mingw32-iconv-static-1.12-12.fc12.noarch
mingw32-iconv-debuginfo-1.12-12.fc12.noarch
mingw32-iconv-1.12-12.fc12.noarch
$ su -c 'rpm -Uv /home/amorilia/rpmbuild/RPMS/noarch/mingw32-win-iconv*.rpm'
Preparing packages for installation...
mingw32-win-iconv-0.0.1-1.fc14
mingw32-win-iconv-static-0.0.1-1.fc14
mingw32-win-iconv-debuginfo-0.0.1-1.fc14
$ rpm -qa | grep mingw32-iconv
mingw32-iconv-debuginfo-1.12-12.fc12.noarch
[!] mingw32-iconv-debuginfo-1.12-12.fc12.noarch should have been removed.
$ rpmquery --requires mingw32-win-iconv
rpmlib(VersionedDependencies) <= 3.0.3-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
mingw32-filesystem >= 63
mingw32-runtime
mingw32(kernel32.dll)
mingw32(msvcrt.dll)
rpmlib(PayloadIsXz) <= 5.2-1
$ rpmquery --provides mingw32-win-iconv
mingw32-iconv = 1.12-13.fc14
mingw32(libiconv.dll)
mingw32-win-iconv = 0.0.1-1.fc14
$ rpmquery --requires mingw32-win-iconv-static
mingw32-win-iconv = 0.0.1-1.fc14
rpmlib(VersionedDependencies) <= 3.0.3-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
mingw32-filesystem >= 63
mingw32-runtime
rpmlib(PayloadIsXz) <= 5.2-1
$ rpmquery --provides mingw32-win-iconv-static
mingw32-iconv-static = 1.12-13.fc14
mingw32-win-iconv-static = 0.0.1-1.fc14
$ rpmquery --requires mingw32-win-iconv-debuginfo
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
mingw32-filesystem >= 63
mingw32-runtime
rpmlib(PayloadIsXz) <= 5.2-1
Does not require mingw32-win-iconv, but apparently native debuginfos are
similar, so I guess this is fine.
$ rpmquery --provides mingw32-win-iconv-debuginfo
mingw32-win-iconv-debuginfo = 0.0.1-1.fc14
[!] Must also provide mingw32-iconv-debuginfo = 1.12-13.fc14
$ mock -r fedora-14-x86_64
~/rpmbuild/SRPMS/mingw32-win-iconv-0.0.1-1.fc14.src.rpm
$ mock -r fedora-14-i386
~/rpmbuild/SRPMS/mingw32-win-iconv-0.0.1-1.fc14.src.rpm
Both work.
Testing
-------
$ wget http://win-iconv.googlecode.com/svn-history/r10/trunk/win_iconv_test.c
and apply this patch: http://code.google.com/p/win-iconv/issues/detail?id=2
$ i686-pc-mingw32-gcc win_iconv_test.c -liconv
$ ./a.exe
All tests pass
$ i686-pc-mingw32-gcc win_iconv_test.c -Wl,-Bstatic -liconv
$ ./a.exe
All tests pass
=================================
Fedora MinGW Packaging Guidelines
=================================
[/] Track Fedora native package versions: stay at same version, include all the
same patches as the native Fedora package, and be built with the same
configuration options.
[+] Packages named by prefixing upstream package name with mingw32-
[+] Use of standard mingw RPM macros %{_mingw32_xxx}
[/] Dll dependencies expressed as mingw32(*.dll)
[+] Dependencies: %global _use_internal_dependency_generator 0 %global
__find_requires %{_mingw32_findrequires} %global __find_provides
%{_mingw32_findprovides}
[+] BuildRequires: mingw32-filesystem >= xx
[+] BuildArch: noarch
[+] All files are installed in %{_mingw32_sysroot}
[+] .dll in %{_mingw32_bindir}, .dll.a (and .la and .a where applicable) in
%{_mingw32_libdir}
[/] No man and info files which are already in Fedora native package
[+] Static libraries in -static subpackage
[+] Stripping: %global __strip %{_mingw32_strip} %global __objdump
%{_mingw32_objdump}
Not in guidelines, but seems to be policy:
[+] Debuginfo: %define __debug_install_post %{_mingw32_debug_install_post}
%{_mingw32_debug_package}
[!] Package does not contain .exe files.
Contains %{_mingw32_bindir}/win_iconv.exe; is this required for the
MinGW compile stack?
===========================
Fedora Packaging Guidelines
===========================
[+] MUST: rpmlint must be run on the source rpm and all binary rpms the build
produces. The output should be posted in the review.
[+] MUST: The package must be named according to the Package Naming Guidelines
.
[+] MUST: The spec file name must match the base package %{name}, in the format
%{name}.spec unless your package has an exemption.
[+] MUST: The package must meet the Packaging Guidelines .
[+] MUST: The package must be licensed with a Fedora approved license and meet
the Licensing Guidelines .
[+] MUST: The License field in the package spec file must match the actual
license.
[+] MUST: If (and only if) the source package includes the text of the
license(s) in its own file, then that file, containing the text of the
license(s) for the package must be included in %doc.
readme.txt contains license
[+] MUST: The spec file must be written in American English.
[+] MUST: The spec file for the package MUST be legible.
[+] MUST: The sources used to build the package must match the upstream source,
as provided in the spec URL. Reviewers should use md5sum for this task. If no
upstream URL can be specified for this package, please see the Source URL
Guidelines for how to deal with this.
[+] MUST: The package MUST successfully compile and build into binary rpms on
at least one primary architecture.
[+] MUST: If the package does not successfully compile, build or work on an
architecture, then those architectures should be listed in the spec in
ExcludeArch. Each architecture listed in ExcludeArch MUST have a bug filed in
bugzilla, describing the reason that the package does not compile/build/work on
that architecture. The bug number MUST be placed in a comment, next to the
corresponding ExcludeArch line.
[+] MUST: All build dependencies must be listed in BuildRequires, except for
any that are listed in the exceptions section of the Packaging Guidelines ;
inclusion of those as BuildRequires is optional. Apply common sense.
[/] MUST: The spec file MUST handle locales properly. This is done by using the
%find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.
[*] MUST: Every binary RPM package (or subpackage) which stores shared library
files (not just symlinks) in any of the dynamic linker's default paths, must
call ldconfig in %post and %postun.
[+] MUST: Packages must NOT bundle copies of system libraries.
[/] MUST: If the package is designed to be relocatable, the packager must state
this fact in the request for review, along with the rationalization for
relocation of that specific package. Without this, use of Prefix: /usr is
considered a blocker.
[+] MUST: A package must own all directories that it creates. If it does not
create a directory that it uses, then it should require a package which does
create that directory.
[+] MUST: A Fedora package must not list a file more than once in the spec
file's %files listings. (Notable exception: license texts in specific
situations)
[+] MUST: Permissions on files must be set properly. Executables should be set
with executable permissions, for example. Every %files section must include a
%defattr(...) line.
[+] MUST: Each package must consistently use macros.
[+] MUST: The package must contain code, or permissable content.
[/] MUST: Large documentation files must go in a -doc subpackage. (The
definition of large is left up to the packager's best judgement, but is not
restricted to size. Large can refer to either size or quantity).
[+] MUST: If a package includes something as %doc, it must not affect the
runtime of the application. To summarize: If it is in %doc, the program must
run properly if it is not present.
[*] MUST: Header files must be in a -devel package.
[+] MUST: Static libraries must be in a -static package.
[*] MUST: If a package contains library files with a suffix (e.g.
libfoo.so.1.1), then library files that end in .so (without suffix) must go in
a -devel package.
[/] MUST: In the vast majority of cases, devel packages must require the base
package using a fully versioned dependency: Requires: %{name} =
%{version}-%{release}
[*] MUST: Packages must NOT contain any .la libtool archives, these must be
removed in the spec if they are built.
[/] MUST: Packages containing GUI applications must include a %{name}.desktop
file, and that file must be properly installed with desktop-file-install in the
%install section. If you feel that your packaged GUI application does not need
a .desktop file, you must put a comment in the spec file with your explanation.
[/] MUST: Packages must not own files or directories already owned by other
packages.
[+] MUST: All filenames in rpm packages must be valid UTF-8.
[/] SHOULD: If the source package does not include license text(s) as a
separate file from upstream, the packager SHOULD query upstream to include it.
[/] SHOULD: The description and summary sections in the package spec file
should contain translations for supported Non-English languages, if available.
[+] SHOULD: The reviewer should test that the package builds in mock.
[+] SHOULD: The package should compile and build into binary rpms on all
supported architectures.
Build tested on i386 and x86_64.
[+] SHOULD: The reviewer should test that the package functions as described. A
package should not segfault instead of running, for example.
[/] SHOULD: If scriptlets are used, those scriptlets must be sane. This is
vague, and left up to the reviewers judgement to determine sanity.
[/] SHOULD: Usually, subpackages other than devel should require the base
package using a fully versioned dependency.
[/] SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and
this is usually for development purposes, so should be placed in a -devel pkg.
A reasonable exception is that the main pkg itself is a devel tool not
installed in a user runtime, e.g. gcc or gdb.
[/] SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin,
/usr/bin, or /usr/sbin consider requiring the package which provides the file
instead of the file itself.
[/] SHOULD: your package should contain man pages for binaries/scripts. If it
doesn't, work with upstream to add them where they make sense.
Summary of issues
-----------------
* I could be missing something, but win_iconv.exe should probably be removed
from the package as it is not required to compile against iconv.
* Somehow, mingw32-win-iconv-debuginfo should provide mingw32-iconv-debuginfo,
so mingw32-iconv-debuginfo gets deleted when installing
mingw32-win-iconv-debuginfo.
* Not really an issue, but a new version is available upstream (0.0.2), which
also includes the static compile patch.
* A final obvious comment: the original mingw32-iconv package exposes more (but
non-standard) functions, so switching to mingw32-win-iconv breaks applications
that rely on these non-standard extensions. As indicated by Erik, this is
intentional, and no serious problems are expected?
--
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.
13 years, 3 months
