RE: include file problem when compiling apps

[Uncle Meat <kcsmart worldinter net>]

On 31-May-99 ottffss opined:
> Whenver I try to compile a GNOME app or lyx I get errors for include
> files.  The
> following is a typical example

<SNIP> 

> looking at line 28 of /usr/include/bits/sigcontext.h I find:
> 
>  #ifndef sigcontext_struct
>  /* Kernel headers before 2.1.1 define a struct sigcontext_struct,
> but
>     we need sigcontext.  */
>  # define sigcontext_struct sigcontext
> 
>  # include <asm/sigcontext.h>
>  #endif
> 
> Looking in the directory /usr/include reveals that there is no
> directory
> 
> called asm.  However, there is a directory asm in the following
> location:
> 
>  /usr/i386-glibc20-linux/include/
> 
> and this directory does contain a file sigcontext.h.
> 
> I've encountered exactly the same type of problem when compiling the
> gnotes applet and
> guppi.  In those cases I eventually got both programs compiled by
> hacking the
> files below:
> 
>  /usr/include/bits/socket.h
>  /usr/src/linux-2.2.5/include/linux/errno.h
>  /usr/i386-glibc20-linux/include/asm/socket.h
> 
> (and backing up the original files as:
> 
>  /usr/include/bits/socket.h-original
>  /usr/src/linux-2.2.5/include/linux/errno.h-original
>  /usr/i386-glibc20-linux/include/asm/socket.h-original.
> )
> 
> I know that this is almost certainly the VERY WRONG way to "fix" the
> problem.
> What is the correct fix?

I dunno a 'correct way' to do it. But, symlinks would work better and
allow the files to stay named just as they are and also make them
available where the compilation wants to find them.

My personal _guess_ would be to edit the Makefile(s) to make sure the
paths are correct. My way's easier and solves it longer-term.

---
   Give me ambiguity or give me something else.