Summary: | dev-util/mingw-runtime-3.18 fails to build on amd64 host (dev-util/w32api-3.14 has incorrect --libdir) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergei Trofimovich (RETIRED) <slyfox> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mingw-runtime-failure-build.log
w32api-3.14.ebuild.patch mingw-runtime-3.18.ebuild.patch - amends --libdir path |
Description
Sergei Trofimovich (RETIRED)
2010-11-22 21:52:14 UTC
Created attachment 255139 [details]
mingw-runtime-failure-build.log
Created attachment 255143 [details]
w32api-3.14.ebuild.patch
fixes only 3.14 part, but should be applied 3.13 and 3.15 as well
user32 is installed to proper place after patch:
/usr/i686-pc-mingw32/usr/lib/libuser32.a
and mingw-runtime does not fail.
My patch looks quite hackish. Similar problem should bite mingw64-runtime (when build mingw64 on x86).
Something more general, based on $CHOST/$CTARGET in econf (or get_libdir) itself might be better. What do you think?
Created attachment 255145 [details]
mingw-runtime-3.18.ebuild.patch - amends --libdir path
And the same disease with mingw-runtime. It prevents cross/gcc from being built:
/usr/libexec/gcc/i686-pc-mingw32/ranlib libgcc.a
/usr/libexec/gcc/i686-pc-mingw32/ld: dllcrt2.o: No such file: No such file or directory
Contents of cross-i686-pc-mingw32/mingw-runtime-3.18 before the patch:
/usr/i686-pc-mingw32/usr/lib64/dllcrt2.o
and after:
/usr/i686-pc-mingw32/usr/lib/dllcrt2.o
*** This bug has been marked as a duplicate of bug 261070 *** |