From: Tom Rini <trini@kernel.crashing.org>
To: Sam Ravnborg <sam@ravnborg.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
zippel@linux-m68k.org, kai@germaschewski.name
Subject: [PATCH 2.6.9] Fix menuconfig on Solaris
Date: Wed, 27 Oct 2004 14:48:00 -0700 [thread overview]
Message-ID: <20041027214800.GA7223@smtp.west.cox.net> (raw)
Something occured to me after I sent my first round of Solaris patches,
people might want to use 'menuconfig' not just config/oldconfig. The
following two bits are needed to get it working (not as colorful as on
Linux, but it functions) for me. First, unless CURS_MACROS is defined,
scroll(x) doesn't get expanded to wscrl(x, 1). I did some quick
grepping on Cygwin and Linux (debian/unstable) and didn't see
CURS_MACROS show up anywhere else, but to be safe I put it inside of
__sun__. Next this uses libcurses instead of libncurses otherwise we
get a bunch of undefined refs to w32attrset, w32addch, acs32map and few
more.
Signed-off-by: Tom Rini <trini@kernel.crashing.org>
--- linux-2.6.9.orig/scripts/lxdialog/dialog.h
+++ linux-2.6.9/scripts/lxdialog/dialog.h
@@ -26,6 +26,9 @@
#include <stdlib.h>
#include <string.h>
+#ifdef __sun__
+#define CURS_MACROS
+#endif
#include CURSES_LOC
/*
--- linux-2.6.9.orig/scripts/lxdialog/Makefile
+++ linux-2.6.9/scripts/lxdialog/Makefile
@@ -1,5 +1,9 @@
HOST_EXTRACFLAGS := -DLOCALE
+ifeq ($(shell uname),SunOS)
+HOST_LOADLIBES := -lcurses
+else
HOST_LOADLIBES := -lncurses
+endif
ifeq (/usr/include/ncurses/ncurses.h, $(wildcard /usr/include/ncurses/ncurses.h))
HOST_EXTRACFLAGS += -I/usr/include/ncurses -DCURSES_LOC="<ncurses.h>"
--
Tom Rini
http://gate.crashing.org/~trini/
next reply other threads:[~2004-10-27 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 21:48 Tom Rini [this message]
2004-10-30 22:16 ` Sam Ravnborg
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=20041027214800.GA7223@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®