Debian bug report logs - #1279, boring messages

Subject: Bug#1279: Strangeness involving <bsd/signal.h>
Reply-To: rdm@tad.micro.umn.edu, debian-bugs@pixar.com
Resent-From: rdm@tad.micro.umn.edu
Resent-To: debian-devel@pixar.com
Resent-Date: Thu, 24 Aug 1995 15:03:05 GMT
Resent-Message-ID: <debian-bugs-handler.1279.08241459080@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: libc
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Thu, 24 Aug 1995 15:03:05 GMT
Received: with rfc822 via encapsulated-mail; Thu, 24 Aug 1995 14:59:06 GMT
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

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

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: rdm@tad.micro.umn.edu
Subject: Bug#1279: Acknowledgement (was: Strangeness involving <bsd/signal.h>)
In-Reply-To: <m0sldiu-00071WC@rdm.legislate.com>
References: <m0sldiu-00071WC@rdm.legislate.com>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1279" or "Re: Bug#1279" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Subject: Bug#1279: Strangeness involving <bsd/signal.h>
Reply-To: rdm@tad.micro.umn.edu, debian-bugs@pixar.com
Resent-From: rdm@tad.micro.umn.edu
Resent-To: debian-devel@pixar.com
Resent-Date: Thu, 24 Aug 1995 15:18:03 GMT
Resent-Message-ID: <debian-bugs-handler.1279.08241514020@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: libc
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Thu, 24 Aug 1995 15:18:03 GMT
Received: with rfc822 via encapsulated-mail; Thu, 24 Aug 1995 15:14:00 GMT
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
To: debian-bugs@Pixar.com
In-Reply-To: <m0sldiu-00071WC@rdm.legislate.com>

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

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: rdm@tad.micro.umn.edu
Subject: Bug#1279: Info received (was Bug#1279: Strangeness involving <bsd/signal.h>)
In-Reply-To: <199508241507.LAA17733@magenta.com>
References: <199508241507.LAA17733@magenta.com>

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developers to
accompany the original report.

If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1279" or "Re: Bug#1279" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)