From: Anthony Green <green@redhat.com>
To: Bart Locanthi <bart@sabl.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: rhug status
Date: Mon, 08 Sep 2003 15:59:00 -0000 [thread overview]
Message-ID: <1063036793.3495.9.camel@escape> (raw)
In-Reply-To: <3F5B766B.7020400@sabl.com>
On Sun, 2003-09-07 at 11:18, Bart Locanthi wrote:
> how up to date is all this?
>
> i tried making xalan and 1) had to hack the Makefile to tell gcj to scan
> apache-regexp,
I'm testing this now. I don't remember having to hand tweak this.
> and 2) whether i use the [hacked] libtool-1.4e or the
> current libtool-1.4.3 i get a link error:
Unfortunately, you need special versions of the maintainer tools for
now:
ftp://sources.redhat.com/pub/rhug/rhug-maintainer-tools.tar.gz
>
> the top-level make appears broken as well. it almost immediately fails,
> attempting to build gnu.readline:
It's possible that configuring/building with srcdir==builddir is broken.
I just tried configuring and building outside of the source tree and it
works just fine. Have you tried this?
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
next prev parent reply other threads:[~2003-09-08 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 18:18 Bart Locanthi
2003-09-08 15:59 ` Anthony Green [this message]
[not found] ` <3F5CB32B.3060203@sabl.com>
2003-09-08 16:59 ` Anthony Green
[not found] ` <1063040272.3495.22.camel@escape>
[not found] ` <3F5CB782.5090203@sabl.com>
2003-09-08 17:17 ` Anthony Green
2003-09-08 17:28 ` Bart Locanthi
2003-09-08 17:11 ` Gary Benson
-- strict thread matches above, loose matches on Subject: below --
2001-09-18 12:25 Anthony Green
2001-09-03 23:42 Anthony Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1063036793.3495.9.camel@escape \
--to=green@redhat.com \
--cc=bart@sabl.com \
--cc=rhug-rhats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).