GNU gettext - Bugs: bug #22184, gettext-runtime/intl fails to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #22184: gettext-runtime/intl fails to build when cross-compiling from Linux to Win32
Submitter: | None | ||
Submitted: | Wed 30 Jan 2008 10:14:11 PM UTC | ||
Category: | Build | Severity: | 3 - Normal |
Item Group: | None | Status: | Invalid |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Thu 31 Jan 2008 12:24:42 PM UTC, comment #5: |
Bruno Haible <haible> |
Thu 31 Jan 2008 09:19:40 AM UTC, comment #4: I thought the "msvc" part of the i586-pc-mingw32msvc triplet referred to the MSVCRT.DLL runtime, not the MSVC compiler?
|
Tor Lillqvist <tml1024> |
Thu 31 Jan 2008 01:24:59 AM UTC, comment #3: I don't know if it's a nonsense or not, but that triplet is the prefix of all the mingw binaries on the mingw32 ubuntu package. |
Alberto Ruiz <aruiz> |
Thu 31 Jan 2008 12:11:49 AM UTC, comment #2:
|
Bruno Haible <haible> |
Wed 30 Jan 2008 10:20:37 PM UTC, comment #1: To reproduce the bug, install MinGW and run the following ./configure command:
|
Anonymous |
Wed 30 Jan 2008 10:14:11 PM UTC, original submission:
gettext-runtime/intl/Makefile.in has a hack for the sed version included with MSYS.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-11-26 | haible | Category | None | Build | |
2008-01-31 | haible | Status | None | Invalid | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed | |||
Summary | gettext-runtime/intl fails to build when cross-compiling from Linux ti Win32 | gettext-runtime/intl fails to build when cross-compiling from Linux to Win32 | |||
2008-01-30 | aruiz | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-758e.
Corresponding source code
The Cygwin package uses the triplet i586-pc-mingw32. MSYS does
the same. If the Debian cross package yields the same kind of
executables than these two, there is no reason for it to have
a different triplet. If, however, the Debian cross package
yields different executables and libraries, I don't want to
hear about it. Then it's an unsupported platform.
Sure, I agree with you that if you are not careful, you can
more easily mess up your environment in Cygwin than in MSYS.
But there's an explicit warning against this problem in
gettext's README.woe32.
MSYS is also supported as a build platform by gettext, but is
not recommended. I cannot recommend it due to the amount of
hacks that are in the MSYS runtime.
MSYS also does pathname translation in command-line arguments:
it converts "nul" to "/dev/null" (or vice versa, I don't
remember) when it finds it appropriate. In command-line
arguments!!
MSYS also causes pipes in bash to behave differently when
run inside rxvt. See the groff mailing list for multiple
reports of this bug.
Hope you understand why I cannot recommend MSYS.
Regarding the Debian cross package. Sometimes it is used with
a library called "libgw32c". of which people say
"Use of LibGw32c as a separate development library is very
complicated."
http://gnuwin32.sourceforge.net/packages/libgw32c.htm
That's the second reason why I don't want to hear about
problems with this build environment.