From: Harry Kalogirou <harkal@gmx.net>
To: Riley Williams <Riley@Williams.Name>
Cc: Linux 8086 <linux-8086@vger.kernel.org>
Subject: Re: [URGENT] elkscmd has a big problem
Date: 30 Apr 2002 20:16:35 +0300 [thread overview]
Message-ID: <1020186998.474.0.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.21.0204301715360.8763-100000@Consulate.UFP.CX>
Την Τρι, 30-04-2002 στις 19:19, ο/η Riley Williams έγραψε:
> Hi Harry.
>
> >> Now that the header files in the kernel use ansi prototypes the
> >> elkscmd has problems :(. There are many programs that are not
> >> compilable now even with the -ansi switch in bcc, because they
> >> don't honor ansi.
>
> > I'll have a look through them tomorrow. However, as an interim
> > measure, perhaps you could drop the current elkscmd tree in with the
> > elks tree of 1st April 2002 (prior to my starting the ANSI'fication)
> > and compile them with that, then see if the result works with the
> > current kernel. If so, create images with the combination on them.
>
> As a first step towards doing this, I've ANSI'fied the elksnet package,
> and it now compiles fine as far as the actual source is concerned.
> However, it fails to link as the function _select is not defined in any
> of the source files.
>
> I would presume that is the select() system call and just needs defining
> somewhere, but I have no idea where. Can you sort this out please, as
> you know this package far better than I do?
>
Ok I will look at it...
Harry
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-04-30 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 16:17 [URGENT] elkscmd has a big problem Harry Kalogirou
2002-04-29 21:30 ` Riley Williams
2002-04-30 16:19 ` Riley Williams
2002-04-30 17:16 ` Harry Kalogirou [this message]
2002-04-30 17:09 ` Harry Kalogirou
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=1020186998.474.0.camel@cool \
--to=harkal@gmx.net \
--cc=Riley@Williams.Name \
--cc=linux-8086@vger.kernel.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 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.