[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

building 2.0.1 sunOS4.1.3

From: John W. Eaton
Subject: building 2.0.1 sunOS4.1.3
Date: Tue, 21 Jan 1997 10:23:37 -0600

On 21-Jan-1997, Djossou Coco <address@hidden> wrote:

: c++ -c  -I. -I.. -I../liboctave -I../src -I../glob -I../libcruft/misc  
-DHAVE_CONFIG_H  -fno-implicit-templates  -O
: In function `void my_friendly_exit(const char *, int)':
: passing `void (*)()' as argument 2 of 
`octave_set_signal_handler(int, void (*)(int))'
: In function `void (* octave_set_signal_handler(int, void 
: warning: ANSI C++ prohibits conversion from `(int)' to 

>From my current version of the INSTALL.OCTAVE file:

   * If you encounter errors like

          passing `void (*)()' as argument 2 of
            `octave_set_signal_handler(int, void (*)(int))'


          warning: ANSI C++ prohibits conversion from `(int)' to `(...)'

     while compiling `', you may need to edit some files
     in the gcc include subdirectory to add proper prototypes for
     functions there.  For example, Ultrix 4.2 needs proper
     declarations for the `signal()' and the `SIG_IGN' macro in the
     file `signal.h'.

     On some systems the `SIG_IGN' macro is defined to be something like

          #define  SIG_IGN  (void (*)())1

     when it should really be something like:

          #define  SIG_IGN  (void (*)(int))1

     to match the prototype declaration for `signal()'.  This change
     should also be made for the `SIG_DFL' and `SIG_ERR' symbols.  It
     may be necessary to change the definitions in `sys/signal.h' as

     The gcc fixincludes/fixproto script should probably fix these
     problems when gcc installs its modified set of header files, but I
     don't think that's been done yet.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]