Hi Peter,

       Thank you so much, now the problem is fixed.  But there is a new problem
arised.  that is :

./compile error.c
In file include from /usr/include/error.h:36,
  from error.c:1:
/usr/include/bits/errrno.h:25/
linux/errno.h:
No such file or directory
 make:***[error.0] ERROR 1

Actually, what mistake did I make, I don't experienced this kind of problem when
I was using redhat linux 6.0 but I got so much problem in rehat linux 6.2.

thank you for so much for your help

Mark

Peter Green wrote:

> also sprach markloky:
> > Hi,
> >
> >          Please help me out, I still counldn't find out what the problem
> > is.
> >   I got the following error.  I am following the installation manual
> > from Life with
> > qmail.
> >
> >  After I create my user and group for qmail, then I type in "make setup
> > check" on the command line.  I got the following error messages.
> >
> > ./ compile sig_alarm.c
> > In file included from /usr/include/signal.h:300, from sig_alarm.c:1:
> > /usr/include/bits/sigcontext.h:28: asm/sigcontext.h:
> > No such file or directory
> > make:***[sig_alarm.0] ERROR 1
> >
> > I have checked that I have the file called "sigcontext.h" in my
> > /usr/include/bits directory, what is the problem i am having.  Oh..Can
> > qmail run under redhat 6.2!! Could this be the problem.!!
>
> qmail will run just fine under Redhat 6.x.
>
> The problem isn't with the /usr/include/bits/sigcontext.h file, it's with a
> file (asm/sigcontext.h) included from that file. Usually this means that you
> haven't properly installed the kernel header files. If you really think you
> have, go into /usr/src/linux/include. There should be a link from asm-ARCH
> (probably asm-i386) to asm. If there isn't one there, put it there (ln -s
> asm-i386 asm).
>
> /pg
> --
> Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
> ---
> The new Linux anthem will be "He's an idiot, but he's ok", as performed by
> Monthy Python. You'd better start practicing.
> (Linus Torvalds, announcing another kernel patch.)

Reply via email to