[Top][All Lists]

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

problems with c89 and c++ on z/OS

From: Werner LEMBERG
Subject: problems with c89 and c++ on z/OS
Date: Tue, 02 Jul 2002 09:06:55 +0200 (CEST)

Here a list of problems with autoconf on z/OS, using native C and C++
compilers.  AFAIK, g++ hasn't been ported (yet).

  . Perhaps a cosmetic thing only: The value `13' in the signal list
    for `trap' causes a warning message about an `unusual trap signal'
    or something similar.  I've checked the list for signals for z/OS
    against my Linux box; the used values in autoconf are the same.
    Perhaps it is a good idea to redirect the output to /dev/null to
    suppress this warning message.

    Mike, James, why does SIGPIPE (which is value 13) cause this

  . The ANSI C compiler on z/OS is called c89; cc is a K&R compiler.
    Is there a way to make autoconf automatically prefer c89 over cc
    on this platform to avoid a `CC=c89'?

  . c89, cc, and c++ (those three forms are only different front ends
    to a single compiler, AFAIK) need an argument (a valid source
    file) to make the switches -v and -V work.  The first line of the
    data returned by -V gives the compiler version.  -v is rather
    useless; the rest of the -V data isn't useful either for autoconf.

    Akim already answered to me that calling both -v and -V with an
    argument will be soon in autoconf.

  . c++ doesn't accept the suffix `.cc' for C++ files by default.  It
    needs the option `-+' to do that.  I would like to have autoconf
    add that automatically.

  . The major problem with c89 and cc (but not with c++) on z/OS is
    that a missing header file doesn't produce a fatal return code.
    This is weird, and I don't know whether this is the correct
    behaviour regarding to the C standard... Anyway, it makes a lot of
    autoconf's tests returning incorrect results.

    Looking into the config.log file (which I've already sent to Akim)
    I can see that the test for sys/dir.h correctly finds out that
    this file doesn't exist.  My question now: Is it possible to use
    this double test (preprocessor/compiler) for checking all header
    files?  Alternatively, can autoconf be forced to do that?
    Ideally, autoconf should do that automatically if running on the
    z/OS platform.

    BTW, the missing header file in question is `stdint.h'.


reply via email to

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