Hi John! On Fri, 15 Mar 2002, John Utz wrote:
> Hello; > > i finally had a work at home day that could be appropriately utilized by > getting xerces-c to build *and* run the samples on my FreeBSD 4.5-RELEASE > box. > > perhaps there are people out there who got this to work without a > problem, but i never saw them chime in when i was helping the *other* > freebsd person who was having trouble, so i suspect otherwise. It's me, it's me :) The pre-sane-includes version (modified 1.6) works for me fine...B > So, I'll write this in a form suitable for adding to the build > instructions: > > Building xerces-c version 1.7 on FreeBSD 4.5-RELEASE > > KEY PREREQUISITES: > > 1. current gnu libiconv and gnu make successfully installed > > note that the convention for freebsd is to symlink gnu make to be gmake This is not necessary, you can "export MAKE=gmake" before building the library... > > 2. hand repair bug 7162 "IconvFreeBSDTransService.cpp needs an #include > statement fixed to use xercesc" > > change line 284 in > xerces-c-src1_7_0/src/xercesc/util/Transcoders/IconvFBSD/IconvFreeBSDTransService.cpp > > from # include <util/Mutexes.hpp> > > to # include <xercesc/util/Mutexes.hpp> It seems to be caused by the sane-includes (hope Tiny will apply the patch you've supplied) ... > Building xerces-c > > sh runConfigure -pfreebsd -d -tIconvFBSD > > if this completes successfully, which it should; > > gmake > > if this completes successfully, which it should; > > su to root and > > gmake install > > > Building and running the samples: > > pass the LDFLAG variable on the command line so that the samples will link > in libiconv successfully: > > gmake LDFLAGS="-L/usr/local/lib/ -liconv" The samples source tree has to be reviewed (I mean the building procedure should) in the same way I did with the tests tree. Unfortunately I did not get enough time to spend with it... -- With best regards, Max. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
