"Brent Nye" <[EMAIL PROTECTED]> writes:
> Hi guys,
>
> I put another installation of Perl (5.6.1) on the
> HP-UX 11 machine and used cc instead of gcc, and this
> is what I am getting now when I type "make:"
>
> cc -c -I. -IHandler
> -I/pbuild/brentnye/xerces/xerces-c15/include
> -D_POSIX_C_SOURCE=199506L -D_HPUX_SOURCE
> -DDEBUGGING -I/usr/local/include
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Ae -g
> -DVERSION="0.10" -DXS_VERSION="0.10" +z
>
>-I/pbuild/brentnye/perl56/lib/5.6.1/PARISC2.0thread/COREPerlContentCallbackHandler.cpp
Is this an email typo? There should be a space after the -I flag and
before the filename, otherwise PerlContentCallbackHandler.cpp won't
get built.
> LD_RUN_PATH="" ld -b +vnocompatwarnings
> -L/usr/local/lib PerlContentCal
> lbackHandler.o PerlDocumentCallbackHandler.o
> PerlErrorCallbackHandler.o PerlE
> xceptionHandler.o -o
> ../blib/arch/auto/Handler/Handler.sl
>
> ld: Can't open PerlContentCallbackHandler.o
If it wasn't built above becuase of a bogus cc line, that would make
it dificult to open...
Try running the build line for it by hand and then relink.
jas.
<FYI>
All the .cpp files in Handler/ are hand written by me (starting with
ideas from Harmon and the NetArx team) to implement the various
callback XML interfaces. The Xerces-C code expects you to register C++
methods for all the *Handlers. But most perl coders want to register
Perl callback methods. So the Perl*Handler classes act as glue methods
which register themselves with Xerces-C and then call your perl
methods when they get called.
</FYI>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
