From: "Steven A. DuChene" <sduchene@mindspring.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] unsatisfied symbols
Date: Tue, 3 Aug 1999 09:43:08 -0400 [thread overview]
Message-ID: <19990803094308.G3443@sduchene.users.mindspring.com> (raw)
In-Reply-To: <19990803114003.A5018@grcbd508.grc.hp.com>; from Ingo Matthaes on Tue, Aug 03, 1999 at 11:40:03AM +0200
On Tue, Aug 03, 1999 at 11:40:03AM +0200, Ingo Matthaes wrote:
> it is not possible to compile the latest CVS-Kernels. I tried
> various configurations, but I still get unsatisfied symbol __delay.
> Is anybody out there, who compiles the actual sources succesfully ?
> make menuconfig seems to be broken too (since 4 weeks)
>
Ingo:
When you say make menuconfig seems to be broken, what exactly doesn't
work? As I understand the current method for compiling kernels takes
place using HP-UX with gcc. Does it also include ncurses or is the
group attempting to use the native HP-UX curses? If the later then
understand that HP-UX has at last count at least three or four
different curses libraries. Some of them are badly broken while others
are only semi broken. My advice is to get ncurses and use it instead
of the various native curses implementations.
If the make menuconfig problem isn't a problem with the curses
implementation on HP-UX I could be barking up the wrong tree here.
--
Steven A. DuChene Linux Fan! http://www.mindspring.com/~sduchene
Outside of a dog, a book is a man's best friend. Inside a dog it's
too dark to read.
-- Groucho Marx
next prev parent reply other threads:[~1999-08-03 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-03 9:40 [parisc-linux] unsatisfied symbols Ingo Matthaes
1999-08-03 13:43 ` Steven A. DuChene [this message]
1999-08-03 13:48 ` Philipp Rumpf
1999-08-03 22:32 ` Helge Deller
1999-08-04 11:28 ` Ingo Matthaes
1999-08-05 12:54 ` [parisc-linux] Pa-risc Linux timetables? Hannu Martikka
1999-08-05 13:32 ` Matthew Wilcox
1999-08-05 13:48 ` Alex deVries
1999-08-05 13:48 ` Philipp Rumpf
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=19990803094308.G3443@sduchene.users.mindspring.com \
--to=sduchene@mindspring.com \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.