From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: is --with-libexpat-prefix broken?
Date: Thu, 28 Feb 2008 19:29:00 -0000 [thread overview]
Message-ID: <20080228183534.GA7296@caradoc.them.org> (raw)
In-Reply-To: <20080228182843.GF19729@adacore.com>
On Thu, Feb 28, 2008 at 10:28:43AM -0800, Joel Brobecker wrote:
> Duh - You're right. I had switch from the slow AIX to a faster
> sparc-solaris machine, but indeed, libexpat is installed in /usr/local.
We get reports of this for ncurses all the time, too (configure will
enable the TUI and then it will fail at link time).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-28 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 0:32 Joel Brobecker
2008-02-28 18:29 ` Daniel Jacobowitz
2008-02-28 18:36 ` Joel Brobecker
2008-02-28 19:29 ` Daniel Jacobowitz [this message]
2008-02-29 4:38 ` is --with-libexpat-prefix broken? NOT! Joel Brobecker
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=20080228183534.GA7296@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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