Alistair Riddoch wrote:
> Mario Frasca writes:
> > login.c: fchown is not defined in my environment, [...]
> [...]If you don't have fchown, this is almost certainly because you did not
>
> build your libc against the correct ELKS kernel.
What do I need to do, besides reading the instructions again? I login into
the CVS server, checkout / update the sources for elks and elkscmd, then you
say I need to build my libc -part of the 8086 development package- against
the correct ELKS kernel. "what do you mean by that? that is not an answer!"
(Pilate ;-)
> > ps.c: and I can't compile it, what are these two <linuxmt/mem.h> and
> > <linuxmt/sched.h> ?
> These include files should be in your ELKS kernel tree. /usr/bcc/include
> should contain links to elks/include/linuxmt and elks/include/arch. Check.
> If it doesn't then build these links by hand.
in my /usr/bcc/include I do have the two arch and linuxmt directories, but
their content is not the same (it's much less) as the ones from the CVS tree
for elks. can I safely remove the two directories and replace them with
links to my local copy of the elks sources? or isn't it safer to add the
switch -I../../elks/include when building ps.c? this is what I did to have ps
compiled.
ciao,
Mario.
p.s.: I did appreciate the references to the problem about copyrighting
algorithms. I simply am astonished and worried about the most recent
proposals at European level. So I could not find a reaction which would not
go too far into politics.
