From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [patch] configure.in: revert osf5.1 no-noncurses special case
Date: Sat, 08 May 2004 15:58:00 -0000 [thread overview]
Message-ID: <20040508151627.GA13901@nevyn.them.org> (raw)
In-Reply-To: <20040508001135.466384B104@berman.michael-chastain.com>
On Fri, May 07, 2004 at 08:11:35PM -0400, Michael Chastain wrote:
> Daniel Jacobowitz suggests:
>
> CPPFLAGS="-I$MIGCHAIN_DIR_INSTALL/host/ncurses-5.4/include" \
> LDFLAGS="-L$MIGCHAIN_DIR_INSTALL/host/ncurses-5.4/lib" \
> $src/configure
>
> This doesn't work for me. Looking in build.log, nothing is
> using my value of LDFLAGS at all.
That doesn't make sense; CPPFLAGS I expect some directories to skip,
but LDFLAGS is standard. Check gdb/Makefile; did LDFLAGS get
substituted in properly?
> Also, some directories are not using my value of CPPFLAGS.
> Here's a list:
>
> honors $CPPFLAGS
> intl bfd opcodes readline
> no $CPPFLAGS
> libiberty mmalloc gdb
>
> Should I file a PR for this?
>
> I don't know enough auto-fu to enhance gdb/Makefile.in and
> gdb/configure.in to honor $CPPFLAGS and $LDFLAGS.
It's not hard. File a PR, I'll try to take care of it soon.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-08 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 0:11 Michael Elizabeth Chastain
2004-05-08 15:58 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-07 17:05 Michael Elizabeth Chastain
2004-05-07 15:52 Michael Elizabeth Chastain
2004-05-07 16:23 ` Mark Kettenis
2004-05-07 16:45 ` Daniel Jacobowitz
2004-05-07 15:10 Michael Elizabeth Chastain
2004-05-07 15:33 ` Daniel Jacobowitz
2004-05-07 16:19 ` Mark Kettenis
2004-05-07 16:49 ` Daniel Jacobowitz
2004-05-07 15:51 ` Andrew Cagney
2004-05-01 22:27 Michael Elizabeth Chastain
2004-05-07 13:50 ` Mark Kettenis
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=20040508151627.GA13901@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mec.gnu@mindspring.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