🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

1 total messages Started by Dieter Faulbaum Mon, 05 Oct 1992 14:09
g++
#1256
Author: Dieter Faulbaum
Date: Mon, 05 Oct 1992 14:09
108 lines
4224 bytes
I am not sure if this is really a bug:

I made the gcc 2.2.2 under SCO 3.2.2.
	It was a easy installation! Thank you for it.

But when I tried to compile the groff, I got errors like this:
	gcc -O -I. -I. -I../include -I./../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_CC_LIMITS_H=1 -DHAVE_CC_UNISTD_H=1 -DSTDLIB_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DLONG_FOR_TIME_T=1 -Dvfork=fork -DHAVE_RENAME=1 -DCOOKIE_BUG=1 -g  -c indxbib.cc
In file included from indxbib.cc:25:
/usr/local/lib/g++-include/signal.h:41: conflicting types for `void (* ssignal (int, auto void (*)()))()'
/usr/include/signal.h:32: previous declaration of `int (* ssignal (int, auto int (*)()))()'

In the manual of the SCO UNIX 3.2.2 there is declared:
          int (*ssignal (sig, action))( )
          int sig, (*action)( );
on a Stardent with UNIX Release 4.0 Pat1 on 3000 Series the same:
     int (*ssignal (sig, action))( )
     int sig, (*action)( );
on HP-UX on the HP 9000 Series also this manual entry:
      int (*ssignal(int sig, int (*action)(int)))(int);
on a GoldStar SPARC/OS Release 1.5
SunOS Release 4.1.1 (GENERIC) also
     int (*ssignal (sig, action))()
     int sig, (*action)();
I looked in the book "UNIX" by J"urgen Gulbins too and he also says:
	int (*ssignal (sig, action)) ();
	int sig, (*action) ();

I have no more references, so I think this a bug.

I think you need the file 'signal.h' to see if it is actual:

// This may look like C code, but it is really -*- C++ -*-
/* 
Copyright (C) 1989 Free Software Foundation
    written by Doug Lea (dl@rocky.oswego.edu)

This file is part of GNU CC.

GNU CC is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY.  No author or distributor
accepts responsibility to anyone for the consequences of using it
or for whether it serves any particular purpose or works at all,
unless he says so in writing.  Refer to the GNU CC General Public
License for full details.

Everyone is granted permission to copy, modify and redistribute
GNU CC, but only under the conditions described in the
GNU CC General Public License.   A copy of this license is
supposed to have been given to you along with GNU CC so you
can know your rights and responsibilities.  It should be in a
file named COPYING.  Among other things, the copyright notice
and this notice must be preserved on all copies.  
*/

#ifndef _signal_h
#ifdef __GNUG__
#pragma once
#pragma interface
#endif



extern "C" {

// This #define KERNEL hack gets around bad function prototypes on most
// systems. If not, you need to do some real work...

#ifndef masscomp
#define KERNEL
#endif

#include <//usr/include/sys/signal.h>

#ifndef masscomp
#undef KERNEL
#endif

#ifndef _signal_h
#define _signal_h 1
#endif

// The Interviews folks call this SignalHandler. Might as well conform.
// Beware: some systems think that SignalHandler returns int.
typedef void (*SignalHandler) (...);

extern SignalHandler signal(int sig, SignalHandler action);
extern SignalHandler sigset(int sig, SignalHandler action);
extern SignalHandler ssignal(int sig, SignalHandler action);
extern int           gsignal (int sig);
extern int           kill (int pid, int sig);

#ifndef hpux // Interviews folks claim that hpux doesn't like these
extern int           sigsetmask(int mask);
extern int           sigblock(int mask);
extern int           sigpause(int mask);
extern int           sigvec(int sig, struct sigvec* v, struct sigvec* prev);
#endif

// The Interviews version also has these ...

#define SignalBad ((SignalHandler)-1)
#define SignalDefault ((SignalHandler)0)
#define SignalIgnore ((SignalHandler)1)


}

#endif
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads