From: Jonathon Tidswell (jont@hydro.hsa.com.au)
Date: 07/13/93


From: jont@hydro.hsa.com.au (Jonathon Tidswell)
Subject: Re: bsd/signal.h problem w/ gcc 2.4.3, libc 4.4.1
Date: Wed, 14 Jul 1993 00:59:09 GMT

In article <ins122a.742447702@aurora.cc.monash.edu.au> ins122a@aurora.cc.monash.edu.au (Mike Battersby) writes:
>I get the following error when trying to compile the "angband"
>game on my system (386-40, no co-pro, gcc 2.4.3, libc 4.4.1):
>
>---------------------------------------------------------------------------
>
>gcc -g -DLIBDIR=\"/usr/angband/lib\" -c /usr/angband/src/signals.c -o
>/usr/ang\band/obj/signals.o
>In file included from /usr/angband/src/signals.c:56:
>/usr/include/bsd/signal.h:7: No include path in which to find signal.h
>make: *** [/usr/angband/obj/signals.o] Error 1
>
>---------------------------------------------------------------------------
>
>Can anyone shed light on this error (seems to occur in a
>#include_next statement -- what does this do?), and suggest
>a fix for the problem ??
>
>regards
>
>Mike

#define conjecture

If you are compiling bsd sources ( particularly networking ) under Linux,
I gather you should use -Ibsd as an option to gcc.
"#include_next <file>" includes in the bsd case and not otherwise or some such.

enjoy,
JonT.

-- 
Jonathon Earnshaw Tidswell            | Telephone:  +61 2 957 3549
Hydrographic Sciences Australia P/L   | Facsimile:  +61 2 959 3594
PO Box 85 Cammeray NSW Australia 2062 | E-mail:     jont@hsa.com.au
Disclaimer: I think my thoughts are my own, and I believe my writings are too.