In all fairness to the maintainers of the Build FAQ, this is not a Solaris-only issue nor is it really a xerces-c build issue. The -L and -l flags are needed when linking an app that uses the xerces library not when building the library. These flags are common to most (if not all) un*x OSs. The text from the Solaris section refer (my assumption) to ABI and other issues that arrise due to a lack of an ABI standard across compilers available on Solaris (Forte vs. SunPro 4.x vs. gcc, etc.)
> -----Original Message----- > From: Todd Keen [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, March 14, 2002 11:52 AM > To: [EMAIL PROTECTED] > Subject: RE: Linking Error on Solaris 8, Xerces C 1_7_0 > > I resolved this by including the following flags when linking the > libraries: > -L$(XERCESCROOT)/lib -lxerces-c1_7_0 -lc -lgen > > The result was my linking line looked like this at link time: > -L/space/u01/downloads/xerces-c-src1_7_0/lib/ -lxerces-c1_7_0 -lc -lgen > > > I thought that this type of information should be included in the Build > FAQ, although I do not know how to add it. > I nice place would be in the section heading: > > Why does my application gives unresolved linking errors on Solaris? > > On Solaris there are a few things that need to be > done before you execute your > application using Xerces-C++. In case you're using > the binary build of Xerces-C++ > make sure that the OS and compiler are the same > version as the ones used to build > the binary (please refer to FAQ: What compilers are > being used on the supported > platforms?). Different OS and compiler versions > might cause unresolved linking > problems or compilation errors. If the versions are > different, rebuild the Xerces-C++ > library on your system before building your > application. If you're using ICU (which is > packaged with XML4C) you need to rebuild the > compatible version of ICU first. > > Also check that the library path is set properly > and that the correct versions of gmake > and autoconf are on your system. > > I think these flags are most likely needed on other platforms as well, > although I don't really know. I know I looked in the Solaris section > since the heading described my issue exactly. Unresolved linking errors > on Solaris. > > I only realized I needed these after noticing them when compiling the > sample code. Maybe this is obvious to some to look for this, but it > wasn't to me. > > Thoughts and feedback are welcome, places I should have looked to get this > information, etc., > > T.K. > > -----Original Message----- > From: Todd Keen > Sent: Monday, March 11, 2002 5:19 PM > To: [EMAIL PROTECTED] > Subject: Linking Error on Solaris 8, Xerces C 1_7_0 > > > I receive the following link errors when I attempt to build Xerces into > my executable: > > -L/space/u01/downloads/xerces-c-src1_7_0/lib/ > ild: (undefined symbol) __RTTI__1nMXMLException_ -- referenced in the > data segment of bin/forte32dbg/DVT.o > ild: (undefined symbol) void XMLPlatformUtils::Terminate() -- referenced > in the text segment of bin/forte32dbg/DVT.o > ild: (undefined symbol) unsigned short*XMLString::transcode(const > char*const) -- referenced in the text segment of bin/forte32dbg/DVT.o > ild: (undefined symbol) void XMLPlatformUtils::Initialize() -- > referenced in the text segment of bin/forte32dbg/DVT.o > ild: (undefined symbol) SAX2XMLReaderImpl::SAX2XMLReaderImpl() -- > referenced in the text segment of bin/forte32dbg/DVT.o > make[1]: *** [bin/forte32dbg/DVT] Error 5 > make[1]: Leaving directory `/export/home/tkeen/projects/DVT' > make: *** [current_dir] Error 2 > > echo $XERCESCROOT > /space/u01/downloads/xerces-c-src1_7_0 > > > ********** > > I have already downloaded and built the libxerces-c1_7_0.so on my > machine using the forte C++ compiler. > All sample Xerces code builds and runs, etc ... > I am not sure what else to try. > > Thanks in advance for any help you can provide, > > Todd Keen > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > **************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
