Sigh…..
Tracking down something in nabla I decided to start absolutely clean and did a
new SVN checkout.
I did the usual ./configure followed by make and got this:
…..
Undefined symbols for architecture x86_64:
"_libintl_bindtextdomain", referenced from:
_main in apl-main.o
"_libintl_gettext", referenced from:
Command::process_line(UCS_string&) in apl-Command.o
Command::cmd_CHECK(std::ostream&) in apl-Command.o
Command::cmd_DROP(std::ostream&, std::vector<UCS_string,
std::allocator<UCS_string> > const&) in apl-Command.o
Command::cmd_HELP(std::ostream&) in apl-Command.o
Command::cmd_HOST(std::ostream&, UCS_string const&) in apl-Command.o
Command::cmd_IN(std::ostream&, std::vector<UCS_string,
std::allocator<UCS_string> >&, bool) in apl-Command.o
Command::cmd_LIB(std::ostream&, UCS_string const&) in apl-Command.o
...
"_libintl_setlocale", referenced from:
Quad_NLT::Quad_NLT() in apl-SystemVariable.o
Quad_NLT::assign(Value_P, char const*) in apl-SystemVariable.o
"_libintl_textdomain", referenced from:
_main in apl-main.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The reason is this:
"There are two implementations of the standard C++ library available on OS X:
libstdc++ and libc++.
They are not binary compatible.
On OS X 10.8 and earlier libstdc++ is chosen by default, on OS X 10.9 libc++ is
chosen by default. To ensure compatibility add -stdlib=libstdc++ to the linking
command."
I happen to be on 10.8 Mountain Lion. I know 10.9 has been out 6 months and I
have been building on it as a test.
But there are still lots of people on 10.8.
Do you feel it's worthwhile to still support OS X less than 10.9?
respect….
Peter
