I'm attempting to build libxml++1.0 after libxml2-2.6.9 on AIX 5.2 and am having some problems.
I find that "configure" is unable to parse the output of "nm" and so sets "global_symbol_pipe" to "" (null), however the shell does not like the "pipe-space-pipe" line that is ultimately generated. For the short term I've changed it to ":" (colon) as a no-op. I'm not sure what the output is supposed to look like so haven't looked closer. I've also found a double semi-colon in "libxml++/nodes/node.h" the compiler (version 6) dislikes. My real problem is that I'm having trouble with object files with ".lo" extensions that looks something like this
cc -Wl,-bM:SRE -o .libs/libxml++-1.0.so.1 attribute.o dtd.o document.o noncopyable.o keepblanks.o
.libs/libxml++-1.0.lax/libparsers.al/parser.lo .libs/libxml++-1.0.lax/libparsers.al/saxparser.lo
.libs/libxml++-1.0.lax/libparsers.al/domparser.lo .libs/libxml++-1.0.lax/libexceptions.al/exception.lo
.libs/libxml++-1.0.lax/libexceptions.al/parse_error.lo .libs/libxml++-1.0.lax/libexceptions.al/validity_error.lo
.libs/libxml++-1.0.lax/libexceptions.al/internal_error.lo .libs/libxml++-1.0.lax/libnodes.al/cdatanode.lo
.libs/libxml++-1.0.lax/libnodes.al/commentnode.lo .libs/libxml++-1.0.lax/libnodes.al/contentnode.lo
.libs/libxml++-1.0.lax/libnodes.al/entityreference.lo .libs/libxml++-1.0.lax/libnodes.al/element.lo
.libs/libxml++-1.0.lax/libnodes.al/node.lo .libs/libxml++-1.0.lax/libnodes.al/processinginstructionnode.lo
.libs/libxml++-1.0.lax/libnodes.al/textnode.lo .libs/libxml++-1.0.lax/libio.al/outputbuffer.lo
.libs/libxml++-1.0.lax/libio.al/ostreamoutputbuffer.lo -Wl,-bnolibpath -Wl,
-blibpath:/eddea01/infra_local/styerd/xml/install/lib:/usr/lib:/lib
-L/eddea01/infra_local/styerd/xml/install/lib -lxml2 -lpthread -liconv
-lm parsers/.libs/libparsers.al exceptions/.libs/libexceptions.al nodes/.libs/libnodes.al io/.libs/libio.al
-lc ${wl}-berok -Wl,-bnoentry -Wl,-bexport:.libs/libxml++-1.0.exp
Most of the files compiled with xlC as I am setting "CXX=xlC_r", I'm not sure why these are different.
Configure does seem to correctly set "compiler_o_lo" (Can we write directly to a .lo ?) correctly.
Any suggestions would certainly be appreciated.
Darryl Styer --|-- darryl styer lmco com
Lockheed Martin `----(*)=(")=(*)----' Phone: (301)640-2028
Air Traffic Management O o O