From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: is --with-libexpat-prefix broken?
Date: Thu, 28 Feb 2008 18:29:00 -0000 [thread overview]
Message-ID: <20080228171244.GA2501@caradoc.them.org> (raw)
In-Reply-To: <20080227234911.GC19729@adacore.com>
On Wed, Feb 27, 2008 at 03:49:11PM -0800, Joel Brobecker wrote:
> With the latest sources, I don't see the -I switch anymore, and
> I don't see the path to the archive either. All I see is that configure
> tries to build using -lexpat without specifying where the includes
> or the library might be found:
>
> > configure:7028: checking for libexpat
> > configure:7052: gcc -o conftest -g conftest.c -lncurses -lsocket -lnsl -lm -lexpat >&5
> > ld: fatal: library -lexpat: not found
> > ld: fatal: File processing errors. No output written to conftest
> > collect2: ld returned 1 exit status
>
> I'm looking into it, but it's really puzzling. It looks like this
> part is taken care of by config/lib-link.m4:AC_LIB_HAVE_LINKFLAGS.
> And yet, I don't see a change since 6.7.1 that could likely be
> responsible for this change of behavior.
This is a horribly overcomplicated macro, originally from (IIRC)
gettext. I used it because it was there and worked, but when it goes
wrong I'm at a loss. I recommend running the configure script with
sh -x to see what it's doing.
The only thing I noticed in the above was that there was no -I option,
but the test file obviously compiled. Could you have switched
compilers and/or added an expat installation in /usr/local/include
and /usr/local/lib? GCC is ornery about searching /usr/local/include
but not /usr/local/lib in some configurations.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-28 17:13 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 [this message]
2008-02-28 18:36 ` Joel Brobecker
2008-02-28 19:29 ` Daniel Jacobowitz
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=20080228171244.GA2501@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--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