public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Anthony Green <green@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: BCEL question
Date: Mon, 16 Dec 2002 10:44:00 -0000	[thread overview]
Message-ID: <87y96pvm53.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1039667582.2883.59.camel@escape>

Anthony> Don't hesitate to patch rhug.  It contains a number of work-arounds
Anthony> already.

I checked in my BCEL fixlet.
On to the latest problem:

/home/tromey/gnu/baseline-gdb/install/bin/ld: cannot find -l-org-apache-regexp

This happens while doing a huge link in BCEL.
I haven't investigated.  I probably won't be able to get to it this
week (and next week I'm not around).

Note that rhug is one of the release criteria for gcj 3.3.
It would be great to have everything ironed out pretty soon...

Tom

  reply	other threads:[~2002-12-16 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 15:57 Tom Tromey
2002-12-11 20:31 ` Anthony Green
2002-12-16 10:44   ` Tom Tromey [this message]
2002-12-18  2:07     ` Gary Benson
2002-12-30 16:39       ` Dhek Bhun Kho
2003-01-05  0:01       ` rhino Dhek Bhun Kho

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=87y96pvm53.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=green@redhat.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).