From: "m h" <sesquile@gmail.com>
To: gentoo-osx@lists.gentoo.org
Subject: [gentoo-osx] Re: [PREFIX] texinfo not finding ncurses
Date: Tue, 11 Apr 2006 10:43:21 -0700 [thread overview]
Message-ID: <e36b84ee0604111043u1ecd5b16y25b5bff5fd358b66@mail.gmail.com> (raw)
In-Reply-To: <e36b84ee0604101815s428b5042tf5fa5b9f9792976a@mail.gmail.com>
> ....
>
> Later the build fails with:
>
> ....
> gcc -Os -march=pentium4 -pipe -L/opt/portage/Apr7/usr/lib
> -L/opt/portage/Apr7/lib -o ginfo dir.o display.o dribble.o
> echo-area.o filesys.o footnotes.o gc.o indices.o info-utils.o info.o
> infodoc.o infomap.o m-x.o man.o nodemenu.o nodes.o search.o session.o
> signals.o terminal.o tilde.o variables.o window.o doc.o
> ../lib/libtxi.a
> terminal.o: In function `terminal_goto_xy':
> terminal.c:(.text+0x48): undefined reference to `tgoto'
> terminal.c:(.text+0x51): undefined reference to `tputs'
> terminal.o: In function `terminal_clear_to_eol':
I got around this by setting LDFLAGS to " -L${PREFIX}/lib -lncurses "
(without ${PREFIX}/usr/lib) in the ebuild.
-matt
--
gentoo-osx@gentoo.org mailing list
prev parent reply other threads:[~2006-04-11 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 1:15 [gentoo-osx] [PREFIX] texinfo not finding ncurses m h
2006-04-11 17:43 ` m h [this message]
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=e36b84ee0604111043u1ecd5b16y25b5bff5fd358b66@mail.gmail.com \
--to=sesquile@gmail.com \
--cc=gentoo-osx@lists.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