* [URGENT] elkscmd has a big problem
@ 2002-04-29 16:17 Harry Kalogirou
2002-04-29 21:30 ` Riley Williams
0 siblings, 1 reply; 5+ messages in thread
From: Harry Kalogirou @ 2002-04-29 16:17 UTC (permalink / raw)
To: Linux-8086
Hi Riley,
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 honer ansi.
Harry
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [URGENT] elkscmd has a big problem
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:09 ` Harry Kalogirou
0 siblings, 2 replies; 5+ messages in thread
From: Riley Williams @ 2002-04-29 21:30 UTC (permalink / raw)
To: Harry Kalogirou; +Cc: Linux 8086
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.
Best wishes from Riley.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [URGENT] elkscmd has a big problem
2002-04-29 21:30 ` Riley Williams
@ 2002-04-30 16:19 ` Riley Williams
2002-04-30 17:16 ` Harry Kalogirou
2002-04-30 17:09 ` Harry Kalogirou
1 sibling, 1 reply; 5+ messages in thread
From: Riley Williams @ 2002-04-30 16:19 UTC (permalink / raw)
To: Harry Kalogirou; +Cc: Linux 8086
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?
Best wishes from Riley.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [URGENT] elkscmd has a big problem
2002-04-30 16:19 ` Riley Williams
@ 2002-04-30 17:16 ` Harry Kalogirou
0 siblings, 0 replies; 5+ messages in thread
From: Harry Kalogirou @ 2002-04-30 17:16 UTC (permalink / raw)
To: Riley Williams; +Cc: Linux 8086
Την Τρι, 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [URGENT] elkscmd has a big problem
2002-04-29 21:30 ` Riley Williams
2002-04-30 16:19 ` Riley Williams
@ 2002-04-30 17:09 ` Harry Kalogirou
1 sibling, 0 replies; 5+ messages in thread
From: Harry Kalogirou @ 2002-04-30 17:09 UTC (permalink / raw)
To: Riley Williams; +Cc: Linux 8086
Την Τρι, 30-04-2002 στις 00:30, ο/η 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.
>
Good idea, hope it works...
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-04-30 17:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2002-04-30 17:09 ` Harry Kalogirou
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox