From: Andrew Hall <halla3@corp.earthlink.net>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: brobecker@gnat.com, gdb@sources.redhat.com
Subject: Re: compile error on solaris 8 and 2.6
Date: Wed, 20 Oct 2004 21:19:00 -0000 [thread overview]
Message-ID: <1098303035.27340.134.camel@flagg> (raw)
In-Reply-To: <1098301417.27340.114.camel@flagg>
Scratch that...it's --disable-tui not --without-tui. So now thats its
compiling, what is the impact of disabling tui. What will I not be able
to use w/in gdb now that I have disabled tui?
Drew
On Wed, 2004-10-20 at 15:43, Andrew Hall wrote:
> Thanks for all the suggestions. I have tried using --without-tui and I
> still get the same error. Any idea why it would be still trying to
> link against tui when I use --without-tui in my configure step?
>
> Drew
>
>
> On Wed, 2004-10-20 at 14:29, Michael Chastain wrote:
> > Joel Brobecker <brobecker@gnat.com> wrote:
> > > I don't
> > > know if it's possible to make it work or not (I think Michael Chastain
> > > tried on Tru64), but you could try by adding -I/path/to/ncurses/include
> > > to your CFLAGS (make CFLAGS='-g -O2 -I/blablabla).
> >
> > I tried this on native alphaev68-dec-osf5.1 with gdb 6.2.1:
> >
> > CPPFLAGS="-I$MIGCHAIN_DIR_INSTALL/host/ncurses-5.4/include"
> > export CPPFLAGS
> > LDFLAGS="-L$MIGCHAIN_DIR_INSTALL/host/ncurses-5.4/lib"
> > export LDFLAGS
> >
> > It didn't work, though. The CPPFLAGS/LDFLAGS did not propagate
> > all the way down. I haven't looked further than that.
> >
> > Michael
>
next prev parent reply other threads:[~2004-10-20 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 18:34 Andrew Hall
2004-10-20 19:17 ` Joel Brobecker
2004-10-20 19:44 ` Michael Chastain
2004-10-20 20:11 ` Joel Brobecker
2004-10-20 20:26 ` Michael Chastain
2004-10-20 20:29 ` Andrew Hall
2004-10-20 21:19 ` Andrew Hall [this message]
2004-10-20 21:22 ` Michael Chastain
2004-10-20 21:36 ` Andrew Hall
2004-10-20 21:46 ` Andrew Hall
2004-10-20 23:11 ` Michael Chastain
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=1098303035.27340.134.camel@flagg \
--to=halla3@corp.earthlink.net \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--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