On Monday, 05 January 2009 at 20:52, Gary Johnson wrote: > I just tried compiling mutt-1.5.19 under Cygwin 1.5.25-15. Configure > completes successfully and says, in part, > > checking wchar.h usability... yes > checking wchar.h presence... yes > checking for wchar.h... yes > checking for wchar_t... yes > > but make errors with these messages at the ld step: > > /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: > warning: auto-importing has been activated without --enable-auto-import > specified on the command line. > This should work unless it involves constant data structures referencing > symbols from auto-imported DLLs.handler.o: In function `enriched_wrap': > /usr/local/src/mutt-1.5.19/mutt-1.5.19/handler.c:554: undefined reference > to `_fputws' > /usr/local/src/mutt-1.5.19/mutt-1.5.19/handler.c:554: undefined reference > to `_fputws' > handler.o: In function `text_enriched_handler': > /usr/local/src/mutt-1.5.19/mutt-1.5.19/handler.c:890: undefined reference > to `_ungetwc' > /usr/local/src/mutt-1.5.19/mutt-1.5.19/handler.c:822: undefined reference > to `_fgetwc' > Info: resolving _COLS by linking to __imp__COLS (auto-import) > Info: resolving _COLOR_PAIRS by linking to __imp__COLOR_PAIRS > (auto-import) > Info: resolving _COLORS by linking to __imp__COLORS (auto-import) > Info: resolving _stdscr by linking to __imp__stdscr (auto-import) > Info: resolving _LINES by linking to __imp__LINES (auto-import) > Info: resolving _optind by linking to __imp__optind (auto-import) > Info: resolving _optarg by linking to __imp__optarg (auto-import) > collect2: ld returned 1 exit status > make[2]: *** [mutt.exe] Error 1 > make[2]: Leaving directory `/usr/local/src/mutt-1.5.19/mutt-1.5.19' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/local/src/mutt-1.5.19/mutt-1.5.19' > make: *** [all] Error 2 > > A little research on the Web revealed that ungetwc() is not yet > supported on Cygwin but will be with Cygwin 1.7 > (http://www.gnu.org/software/gnulib/manual/html_node/ungetwc.html and > http://www.mail-archive.com/cygwin-announce@xxxxxxxxxx/msg02612.html). > Does anyone know of a workaround for Cygwin 1.5 in the mean time? We'll have to create proper replacement functions. A patch was submitted on Saturday but I didn't think it was enough. I've created a ticket for this: http://dev.mutt.org/trac/ticket/3148
Attachment:
pgpyA5_sk9v7Z.pgp
Description: PGP signature