> out of simple necessity, therefore I'm thinking it's a > permissions thing or a altered Unix/Linux box where > those files have been moved to another location in > > In file included from /usr/include/signal.h:268, > > from comm.c:90: > > /usr/include/sigcontext.h:26: asm/sigcontext.h: No > > such file or directory
Well, the problem isn't finding the headers for his files, it's finding the headers that the headers include. :) So changing his code likely won't have any positive effect, unless there is another copy of the header files somewhere on the machine that is correct or something (this seems highly unlikely). My guess is that some of the header files are actually missing.. Maybe whoever set up the box didn't install all of the header files or did a half-assed upgrade that left them incomplete. At any rate, I don't think the MUD code is to blame, it's a problem with the compiler installation or configuration, and fixing it will rest on the shoulders of the sys admin. Or if it's your own machine, make sure all of the header, compiler and library packages are installed and of the same version. --Palrich.
