Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Klaus Zeitler <kzeitler@lucent.com>
To: gdb@sources.redhat.com
Subject: Re: CVS version doesn't compile (ncurses library found, but no includes)
Date: Wed, 06 Jul 2005 14:07:00 -0000	[thread overview]
Message-ID: <q5gvf3oqb82.fsf@lucent.com> (raw)
In-Reply-To: <20050705132908.GA18507@nevyn.them.org> (Daniel Jacobowitz's message of "Tue, 5 Jul 2005 09:29:08 -0400")

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
    Daniel> 
    Daniel> CFLAGS="-O2 -I/opt/exp/gnu/include".

CFLAGS alone didn't help, configure still wouldn't find ncurses.h, however
with CPPFLAGS="-I/opt/exp/gnu/include" configure found ncurses.h.
But then I ran into compile problems (the ncurses include dir unfortunately
also contained ansidecl.h, that was now found instead of the one that comes
with gdb). Unfortunately setting CFLAGS as above puts the additional include
dir in front of all the other include dirs.
Just out of curiosity I added the additional include dir for ncurses
at the end of INTERNAL_WARN_CFLAGS in gdb/Makefile.in and together with
the setting of CPPFLAGS I could configure and compile gdb.
I also noticed that there's already a comment in configure that it may be
difficult to produce gdb with ncurses in a non-standard dir.

But then again according to Mark's response I think I'll ditch ncurses and go
with the standard curses.

Thanks

Klaus

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             kzeitler@lucent.com  |
 ------------------------------------------
---
The probability of someone watching you is
proportional to the stupidity of your action.


  reply	other threads:[~2005-07-06 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 13:23 Klaus Zeitler
2005-07-05 13:29 ` Daniel Jacobowitz
2005-07-06 14:07   ` Klaus Zeitler [this message]
2005-07-05 22:12 ` 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=q5gvf3oqb82.fsf@lucent.com \
    --to=kzeitler@lucent.com \
    --cc=gdb@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