* Re: rhug/xalan ChangeLog configure.in configure
[not found] <20030908171322.32106.qmail@sources.redhat.com>
@ 2003-09-09 16:32 ` Gary Benson
2003-09-09 18:31 ` Anthony Green
0 siblings, 1 reply; 5+ messages in thread
From: Gary Benson @ 2003-09-09 16:32 UTC (permalink / raw)
To: rhug-rhats
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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: rhug/xalan ChangeLog configure.in configure
2003-09-09 16:32 ` rhug/xalan ChangeLog configure.in configure Gary Benson
@ 2003-09-09 18:31 ` Anthony Green
2003-09-11 15:43 ` Gary Benson
0 siblings, 1 reply; 5+ messages in thread
From: Anthony Green @ 2003-09-09 18:31 UTC (permalink / raw)
To: Gary Benson; +Cc: rhug-rhats
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: rhug/xalan ChangeLog configure.in configure
2003-09-09 18:31 ` Anthony Green
@ 2003-09-11 15:43 ` Gary Benson
2003-09-11 16:05 ` Anthony Green
0 siblings, 1 reply; 5+ messages in thread
From: Gary Benson @ 2003-09-11 15:43 UTC (permalink / raw)
To: rhug-rhats
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: rhug/xalan ChangeLog configure.in configure
2003-09-11 15:43 ` Gary Benson
@ 2003-09-11 16:05 ` Anthony Green
2003-09-11 16:09 ` Gary Benson
0 siblings, 1 reply; 5+ messages in thread
From: Anthony Green @ 2003-09-11 16:05 UTC (permalink / raw)
To: Gary Benson; +Cc: rhug-rhats
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: rhug/xalan ChangeLog configure.in configure
2003-09-11 16:05 ` Anthony Green
@ 2003-09-11 16:09 ` Gary Benson
0 siblings, 0 replies; 5+ messages in thread
From: Gary Benson @ 2003-09-11 16:09 UTC (permalink / raw)
To: rhug-rhats
> > 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?
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-09-11 16:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20030908171322.32106.qmail@sources.redhat.com>
2003-09-09 16:32 ` rhug/xalan ChangeLog configure.in configure Gary Benson
2003-09-09 18:31 ` Anthony Green
2003-09-11 15:43 ` Gary Benson
2003-09-11 16:05 ` Anthony Green
2003-09-11 16:09 ` Gary Benson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).