Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: mec.gnu@mindspring.com, Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] configure.in: revert osf5.1 no-noncurses special case
Date: Fri, 07 May 2004 16:45:00 -0000	[thread overview]
Message-ID: <20040507164549.GA24613@nevyn.them.org> (raw)
In-Reply-To: <200405071623.i47GN8u1066198@elgar.kettenis.dyndns.org>

On Fri, May 07, 2004 at 06:23:08PM +0200, Mark Kettenis wrote:
>    Date: Fri,  7 May 2004 11:52:27 -0400 (EDT)
>    From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>    > Personally, I don't see the point in worrying about this.  If you've got
>    > a broken ncurses installation - one where the linker finds -lncurses but
>    > gcc doesn't, or vice versa, is broken in my book - it's your problem.
> 
>    Right now I have *no way to fix it*.  I built ncurses 5.2, ncurses 5.3,
>    and ncurses 5.4 on this system, and I built gdbtui with each of them and
>    ran each of them.  All of them work.  But I had to hack the Makefile to
>    do it, because there is no configuration option to tell gdb to use
>    $MIGCHAIN_DIR_INSTALL/host/ncurses-5.4.  (And I can't install any
>    software as root on this system).
> 
>    Suppose I want to test a new version of ncurses?
> 
>    Suppose I have an oddball platform and I need to patch ncurses in
>    order to use it?
> 
> The way this is supposed to work with autoconf is that you set the
> right environment variables (CPPFLAGS, LDFLAGS) before running
> configure.  Unfortunately most configure scripts out there don't
> respect these variables, because folks overide these variables in
> their Makefile.in.

But we don't.  Michael, is there any reason this wouldn't have worked
for you?

CPPFLAGS="-I$MIGCHAIN_DIR_INSTALL/host/ncurses-5.4/include" \
 LDFLAGS="-L$MIGCHAIN_DIR_INSTALL/host/ncurses-5.4/lib" \
 $src/configure

Or even:

CPPFLAGS="-I/usr/local/include" \
 LDFLAGS="-L/usr/local/lib" \
 $src/configure

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-05-07 16:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 15:52 Michael Elizabeth Chastain
2004-05-07 16:23 ` Mark Kettenis
2004-05-07 16:45   ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-08  0:11 Michael Elizabeth Chastain
2004-05-08 15:58 ` Daniel Jacobowitz
2004-05-07 17:05 Michael Elizabeth Chastain
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=20040507164549.GA24613@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