Hey Tinny and IBM team,

Getting Xerces-Perl to work on different architectures is a bit of a
pain, because Perl only stores configuration information for the
platforms C compiler and not the C++ compiler. 

However, if someone needing Xerces-Perl has built Xerces-C from
source, I can steal all the info I need from the config.status
file. However this strategy only works for source builds, since the
binary builds don't include this file.

For future releases, is it possible to include this file with the
binary releases? Perhaps in an etc/ directory? That way Xerces-Perl
(and other ports) can much more succinctly get the compile information
we need.

Thanks,
jas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to