Re: Weird parse error when compiling with Slack linux?

1999-04-05 Thread jaharkes
Can you find out if libc5 actually defines register_t anywhere?? i.e. 'grep register_t /usr/include/*/*.h' otherwise you need to add typedef int register_t; to the top of lwp.c. Jan

Re: Weird parse error when compiling with Slack linux?

1999-04-05 Thread Magnus Ahltorp
> Unfortunately it does not make any difference. It failed at the same > point with the same errors. Any other ideas? >From your error messages, it seems register_t isn't defined anywhere. If you could look through your include files and search for a typedef of register_t, including that file wou

Re: Weird parse error when compiling with Slack linux?

1999-04-05 Thread Peter T. Breuer
"A month of sundays ago Magnus Ahltorp wrote:" > > >From your error messages, it seems register_t isn't defined > anywhere. If you could look through your include files and search for I'll help. oboe:/usr/include% grep -w register_t `find . -type f -name "*.h"` oboe:/usr/include% just def

Re: coda win95/98 client question

1999-04-05 Thread Marc Schnieder
Subbarao Meduri wrote: > > If I understand correctly, code win95 client is > blocking in ring 0 (kernel) for servicing I/O requests > from a user space process (ring 3). This should cause > a deadlock since win95 kernel32 acquires a global > lock before dispatching I/O request to kernel and > exp

Re: Other OSes?

1999-04-05 Thread Peter J. Braam
Hi Anders, A compile on Solaris would be most welcome. I think it might be a good idea to ignore the client kernel code in the first instance and get venus and the servers going. For the client kernel code, there are a couple of alternatives. First with the Solaris kernel development kit, it

Re: Weird parse error when compiling with Slack linux?

1999-04-05 Thread Jesse Brown
No it does not. WHen I added the typedef in lwp.c (in fact it was #ifdef'd out for another platform) it compiled just fine. Would it be possible to add that check into the config script? Either way, I am getting a number of other non-fatal errors when compiling. I will let you all know of any wei

Re: Weird parse error when compiling with Slack linux?

1999-04-05 Thread Jesse Brown
It is a Slackware 3.5 machine, however I have tryed to compile it on a fresh 3.6 machine with the same errors. Perhaps a glibc problem? Either way, manually definining it worked. Now I have some other errors. :) ../../../lib-src/mlwp/lwp.c: In function `Trace_Swapped_Stack': ../../../lib-src/mlwp

Re: Weird parse error when compiling with Slack linux?

1999-04-05 Thread jaharkes
[EMAIL PROTECTED] said: | make[2]: *** No rule to make target `-lreadline', needed by `filcon'. Stop. | make[1]: *** [fail] Error 2 | make: *** [coda-src] Error 2 Hi Jesse, The warnings are annoying, but most likely harmless. For the compile error, you could try this patch against coda-src/fai