public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
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 16:59:00 -0000	[thread overview]
Message-ID: <1063040341.3495.24.camel@escape> (raw)
In-Reply-To: <3F5CB32B.3060203@sabl.com>

On Mon, 2003-09-08 at 09:49, Bart Locanthi wrote:
> what's special about the maintainer tools? is it still special? i did 
> try them, but i would prefer not to have older stuff lying around.

I believe they are still special.  I don't recall what the differences
are - but some of the changes are simple (don't add -DPIC to gcj command
line, for instance).

> i have yet to try building outside of the source tree. are there any 
> other ./configure switches you would suggest setting?

--disable-static

> the errors from UTF as illegal chars seem pretty hard. this may be a
new 
> development with gcc-3.3.1.

I don't think you mentioned this error in your mail.  Could you please
describe it?  rhug should build with 3.3.1.

I hope you don't mind that I'm keeping the list on copy.  The archives
are often a useful resource for people looking for help.

Thanks,

AG

-- 
Anthony Green <green@redhat.com>
Red Hat, Inc.

  parent reply	other threads:[~2003-09-08 16: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
     [not found]   ` <3F5CB32B.3060203@sabl.com>
2003-09-08 16:59     ` Anthony Green [this message]
     [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=1063040341.3495.24.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).