pkgsrc-WIP-discuss archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: dealing with curses/ncurses conflict in pkgsrc



No, not at all. The point is that I don't want it to use ncurses, but I
can't remove /usr/pkg/include from the compilation path unless I
hand-hack it just for that program (resize). The ncurses unctrl.h
(under /usr/pkg/include) is unfortunately getting called instead of the
one under /usr/include from /usr/include/curses.h.

Thanks,
- Greg S.

On Fri, 2005-05-06 at 23:10 +0200, Thomas Klausner wrote:
> On Fri, May 06, 2005 at 02:54:16PM -0600, Greg Schenzel wrote:
> > I've been working on pkglint'ing and polishing my mxterm port before
> > sending it for review and cvs import. I'm down to the last problem,
> > which is that when compiling the small "resize" program after the
> > main compile is done, NetBSD curses and pkg of ncurses run in
> > conflict of each other over curses.h->unctrl.h and the compile will
> > not complete. Simply running the same command without the
> > "-I/usr/pkg/include" argument results as expected, however I can not
> > remove /usr/pkg/include from the default compile command because
> > "mxterm" requires openmotif, which is under /usr/pkg. Any suggestions?
> 
> Does the package really need ncurses (instead of curses)?
>  Thomas



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss



Home | Main Index | Thread Index | Old Index