From:	sof AT dcs DOT gla DOT ac DOT uk (Sigbjorn Finne)
Subject:	MB_CUR_MAX troubles
27 Jan 1999 15:05:43 -0800 :
Message-ID:	<13999.20359.699446.503739.cygnus.gnu-win32@marcus>
Mime-Version:	1.0
To:	gnu-win32 AT cygnus DOT com

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".

- Raw text -