Debian bug report logs - #1279
Strangeness involving <bsd/signal.h>
Package: libc; Reported by: rdm@tad.micro.umn.edu; 68 days old.
Message received at debian-bugs:
From magenta.com!moth Thu Aug 24 08:12:55 1995
Return-Path: <moth@magenta.com>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0sldxf-0003ZmC; Thu, 24 Aug 95 08:12 PDT
Received: from magenta.com by pixar.com with SMTP id AA04069
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 24 Aug 1995 08:12:45 -0700
Received: (moth@localhost) by magenta.com (8.6.12/8.6.4) id LAA17733; Thu, 24 Aug 1995 11:07:55 -0400
Date: Thu, 24 Aug 1995 11:07:55 -0400
Message-Id: <199508241507.LAA17733@magenta.com>
From: rdm@tad.micro.umn.edu
Reply-To: rdm@tad.micro.umn.edu
To: debian-bugs@Pixar.com
In-Reply-To: <m0sldiu-00071WC@rdm.legislate.com>
Subject: Re: Bug#1279: Strangeness involving <bsd/signal.h>
I'm not completely sure if this is a bug or not.
I also had to add -lc to get this program to link properly -- maybe
this is ansi behavior?
[Also, I still don't have the program running properly -- it makes
some really silly assumptions about the underlying C implementation.]
--
Raul
Acknowledgement sent to rdm@tad.micro.umn.edu
:
Extra info received and forwarded.
Full text available.
Information forwarded to debian-devel@pixar.com
:
Bug#1279
; Package libc
.
Full text available.
Message received at debian-bugs:
From tad.micro.umn.edu!rdm Thu Aug 24 07:57:46 1995
Return-Path: <rdm@tad.micro.umn.edu>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0sldj0-0007u8C; Thu, 24 Aug 95 07:57 PDT
Received: from rdm.legislate.com ([192.77.155.13]) by pixar.com with SMTP id AA03095
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 24 Aug 1995 07:57:35 -0700
Received: by rdm.legislate.com
id <m0sldiu-00071WC@rdm.legislate.com>
(Debian /\oo/\ Smail3.1.29.1 #29.33); Thu, 24 Aug 95 10:57 EDT
Message-Id: <m0sldiu-00071WC@rdm.legislate.com>
Date: Thu, 24 Aug 95 10:57 EDT
From: rdm@tad.micro.umn.edu
To: debian-bugs@pixar.com
Subject: Strangeness involving <bsd/signal.h>
Package: libc
Version: 4.6.27
Revision: 5
I ran into a compilation problem where I had to add -I/usr/include to
some gcc options to get a program to compile correctly. This appears
to be the use of the #include_next directive in <bsd/signal.h>.
The program I was compiling was xfishtank (from an O'Reilly cdrom --
this means it's either an X contrib package, or from comp.sources.x --
I suspect the latter). Here's line that worked (the only change I
made was adding -I/usr/include):
gcc -g -ansi -I/usr/include -I. -I./fishmaps -I/usr/X11R6/include -Dlinux -D__i386__ -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DX_LOCALE -DFUNCPROTO=15 -DNARROWPROTO -c xfish.c -o xfish.o
This was after I'd put an #ifdef linux line in the xfish.c file that
used <bsd/signal.h> instead of <signal.h>. [Before that, it wouldn't
compile at all.]
--
Raul
Acknowledgement sent to rdm@tad.micro.umn.edu
:
New bug report received and forwarded.
Full text available.
Report forwarded to debian-devel@pixar.com
:
Bug#1279
; Package libc
.
Full text available.
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism