Why is this necessary? I couldn't find a single place in xalan where
jakarta-regexp is referenced...
Gary
green@sources.redhat.com wrote:
> CVSROOT: /cvs/rhug
> Module name: rhug
> Changes by: green@sourceware.org 2003-09-08 17:13:22
>
> Modified files:
> xalan : ChangeLog configure.in configure
>
> Log message:
> Add jakarta-regexp to classpath.
>
> Patches:
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/rhug/xalan/ChangeLog.diff?cvsroot=rhug&r1=1.26&r2=1.27
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/rhug/xalan/configure.in.diff?cvsroot=rhug&r1=1.6&r2=1.7
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/rhug/xalan/configure.diff?cvsroot=rhug&r1=1.7&r2=1.8
>
On Tue, 2003-09-09 at 01:40, Gary Benson wrote:
> Why is this necessary? I couldn't find a single place in xalan where
> jakarta-regexp is referenced...
It's referenced in BCEL, which is used by Xalan. The rhug build will,
under some conditions, put the BCEL source tree on the classpath.
Hmm.. is the solution just to make sure that it uses the BCEL jar file
from the build tree?
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
Anthony Green wrote:
> On Tue, 2003-09-09 at 01:40, Gary Benson wrote:
> > Why is this necessary? I couldn't find a single place in xalan
> > where jakarta-regexp is referenced...
>
> It's referenced in BCEL, which is used by Xalan. The rhug build
> will, under some conditions, put the BCEL source tree on the
> classpath.
I've never had a problem with this. I'm using gcc 3.3.
Gary
On Thu, 2003-09-11 at 08:43, Gary Benson wrote:
> I've never had a problem with this. I'm using gcc 3.3.
Perhaps because it's building with an installed BCEL.
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
> > I've never had a problem with this. I'm using gcc 3.3.
>
> Perhaps because it's building with an installed BCEL.
Nah, it was in the RHUG tree so it should have been using the BCEL
sources. What file in xalan fails?