From:	scarpe AT atos-group DOT com (Sebastien Carpe)
Subject:	Re: MB_CUR_MAX troubles
28 Jan 1999 07:14:54 -0800 :
Message-ID:	<36B01DDE.72F1FD5A.cygnus.gnu-win32@atos-group.com>
References:	<13999 DOT 20359 DOT 699446 DOT 503739 AT marcus>
Mime-Version:	1.0
To:	Sigbjorn Finne <sof AT dcs DOT gla DOT ac DOT uk>
Cc:	gnu-win32 AT cygnus DOT com

Not a real fix, but i did the workaround by declaring and setting __mb_cur_max
to 1 (which is hopefully my case, since i don't think i have (or use) multibyte
characters) for compiling things with gtk (MB_CUR_MAX used in gdkim or smthg).
Yet, if someone more accurate with cygwin internal has an answer on that
mystery, i'll be glad to hear of it ..

Sigbjorn Finne wrote:
> 
> Apologies if this one has been reported to the list already, but using
> MB_CUR_MAX leads to trouble:
> 
> sa$ cat foo.c
> #include <stdio.h>
> #include <stdlib.h>
> 
> int
> main()
> {
>  fprintf(stderr, "%d\n", MB_CUR_MAX);
>  return 0;
> }
> 
> sa$ gcc -o main foo.c
> /tmp/ccVF4bqo.o(.text+0x1d):foo.c: undefined reference to `__mb_cur_max'
> sa$ gcc --version
> egcs-2.91.60
> sa$ uname -a
> CYGWIN_NT-4.0 SARK 20.1 (0.3/1/1) 1998-12-3 20:39:18 i686 unknown
> sa$
> 
> MB_CUR_MAX expands to __mb_cur_max, which is present in libc.a, but
> linking with it included leads to multiple defs of _impure_ptr being
> in scope.
> 
> --Sigbjorn
> 
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -