I don't think it's a problem in your environment. STDCXX-404
describes the same issue on FreeBSD. We still need to look
into it: http://issues.apache.org/jira/browse/STDCXX-404
If you could add your comments to this issue or file a new
one that would be great.
Martin
Eric Lemings wrote:
For everyone else's viewing pleasure:
________________________________
From: Eric Lemings
Sent: Thursday, July 12, 2007 6:30 PM
To: Andrew Black
Cc: Martin Sebor
Subject: Built STDCXX On Mac Lately?
Has anyone built STDCXX on Mac lately? I just tried and got some
compile errors in util/localedef.cpp. At first glance, it looks like
the change that conditionally includes <iconv.h> is the culprit. There
are still symbols from that header file still being used in the source
file even when the header is not included.
Here's the error:
gcc runall.o cmdopt.o output.o util.o exec.o display.o -o exec
-L/Users/elemings/Developer/Build/stdcxx/lib -lstd -lsupc++ -lgcc_eh -lm
gcc -c -I/Users/elemings/Developer/Work/stdcxx/include/ansi
-D_RWSTDDEBUG -I/Users/elemings/Developer/Work/stdcxx/include
-I/Users/elemings/Developer/Build/stdcxx/include -pedantic -nostdinc++
-g -W -Wall -Wcast-qual -Winline -Wshadow -Wwrite-strings
-Wno-long-long -Wcast-align
/Users/elemings/Developer/Work/stdcxx/util/localedef.cpp
In file included from
/Users/elemings/Developer/Work/stdcxx/util/def.h:45,
from
/Users/elemings/Developer/Work/stdcxx/util/localedef.cpp:30:
/Users/elemings/Developer/Work/stdcxx/util/charmap.h:167: error:
'iconv_t' does not name a type
/Users/elemings/Developer/Work/stdcxx/util/charmap.h:230: error:
'iconv_t' does not name a type
/Users/elemings/Developer/Work/stdcxx/util/charmap.h:233: error:
'iconv_t' does not name a type
/Users/elemings/Developer/Work/stdcxx/util/localedef.cpp: In function
'bool process_command_line(ProgramOptions*, int, char**)':
/Users/elemings/Developer/Work/stdcxx/util/localedef.cpp:475: warning:
unused variable 'errors'
make[2]: *** [localedef.o] Error 1
make[1]: *** [util] Error 2
make: *** [libstd] Error 2
I was about to file a Jira issue but thought I'd make sure this is
really an error and not my environment.
Brad.
