From: Brandon Low <lostlogic@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: GCC 3.1 & ncurses fun
Date: Tue, 11 Jun 2002 09:14:01 -0500 [thread overview]
Message-ID: <20020611091401.A12968@lostlogicx.com> (raw)
In-Reply-To: <1023795490.30653.94.camel@pcianp>; from ianp@tibco.com on Tue, Jun 11, 2002 at 12:37:57PM +0100
There should be a fix for this in our pipes, which revision of gcc-3.1 are
you running? If you are running -r5, and are VERY BRAVE you may want to
try switching to -r6 which has some header file adjustments and other
fixes for gcc-3.1. If not, wait till we have finished testing and poking
at -r6 and it should fix these ncurses problems...
The quicker way to see if our fixes will even work for this particular
problem would be to delete /usr/lib/gcc-lib/${CHOST}/3.1/include/ncurses.h
and /usr/lib/gcc-lib/${CHOST}/3.1/include/curses.h (probably want to back
them up just in case as you are messing with gcc headers here...)
Good Luck, let us know what works for you!
--Brandon
On Tue, 06/11/02 at 12:37:57 +0100, Ian Phillips wrote:
> More info,
>
> > pcianp portage # find /usr/lib -name 'libnc*' -type f -print
> > /usr/lib/libncurses.a
> > /usr/lib/libncurses++.a
>
> but, after some looking around...
>
> pcianp portage # find /lib -name 'libnc*'
> /lib/libncurses.so.5.2
> /lib/libncurses.so
> /lib/libncurses.so.5
>
> and I spotted in the output from dev-util/dialog:
>
> ...
> checking for -lncurses in /usr/lib... no
> checking for -lncurses in /usr/lib/ncurses... no
> checking for -lncurses in /usr/ncurses/lib... no
> checking for -lncurses in /lib... no
> checking for -lncurses in /lib/ncurses... no
> ...
>
> so it's looking in the right place but not finding it apparently.
>
> I'm going to try
>
> emerge -C sys-libs/ncurses && emerge sys-libs/ncurses
>
> to ensure that I've got an up to date build, but portage should
> take care of this anyway for me, right?
>
> Hmmm, that didn't work. I'm going to head on over to #gentoo to
> ask the question there then.
>
> Yours,
> Ian.
>
> --
> #ifndef __COMMON_SENSE__ | Ian Phillips
> #include <std_disclaimer> | TIBCO Software Inc.
> #endif | www.tibco.com
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-06-11 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 11:37 [gentoo-dev] Re: GCC 3.1 & ncurses fun Ian Phillips
2002-06-11 10:15 ` Paul de Vrieze
2002-06-11 14:14 ` Brandon Low [this message]
[not found] <20020611141702.5F77CAC639@chiba.3jane.net>
2002-06-11 16:25 ` Ian Phillips
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=20020611091401.A12968@lostlogicx.com \
--to=lostlogic@gentoo.org \
--cc=gentoo-dev@gentoo.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