bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Benji Wiebe <benjiwiebe14@gmail.com>
To: Bruno Haible <bruno@clisp.org>, Tim Rice <tim@multitalents.net>
Cc: bug-gnulib@gnu.org
Subject: Re: Port getprogname module to SCO OpenServer
Date: Mon, 5 Oct 2020 21:23:28 -0500	[thread overview]
Message-ID: <64fe151c-bbe8-d2ad-8352-b112cee5e806@gmail.com> (raw)
In-Reply-To: <1640698.kv1YpayHPu@omega>

http://osr600doc.sco.com/en/man/html.CP/cc.CP.html#cc_preassertion

Is where the predefined constants for the builtin cc are listed. Do we 
need to support a possible future port of clang to SCO OpenServer when 
OpenServer is dead?

Or just make it work with the current compilers available? (SCO's cc and 
GCC)

On 10/3/20 9:48 PM, Bruno Haible wrote:
> Tim Rice wrote:
>> Hi Bruno,
>>
>> On Sat, 3 Oct 2020, Bruno Haible wrote:
>>
>>> Tim Rice wrote:
>>>>> +# elif defined __SCO_VERSION__ /* SCO OpenServer/UnixWare */
>>>> While __SCO_VERSION__ covers Openserver 6 and UnixWare 7,
>>>> what is normally used for 6 and 7 is __USLC__  for the native compiler
>>>> and __sysv5__ for gcc
>>>>
>>>> Ie.
>>>> # elif defined __USLC__ || defined __sysv5__
>>> If the code depends only on the operating system, let's use a #if for
>>> the operating system, not for the compilers (__USLC__). Because the day
>>> clang gets ported to that operating systems, the condition would not
>>> work any more.
>>>
>>> https://sourceforge.net/p/predef/wiki/OperatingSystems/ says that
>>> _SCO_DS can be used to test for SCO OpenServer. It seems that you say that
>>> __SCO_VERSION__  works as well. So let's use one of these.
>> As to __SCO_VERSION__ vs __USLC__ for native compiler, I am fine
>> with __SCO_VERSION__ in this case.
> Good.
>
>> _SCO_DS is only for Openserver 5 (which the proposed patch will not work for)
>> and __SCO_VERSION__ only works for the native compiler on OpenServer 6 and
>> UnixWare 7. Sorry I did not make that clear before.
>> __sysv5__ works for the GCC 7.3.0 on 6 and 7. If clang is ported, chances
>> are extremely high it will also include the __sysv5__ manifest define.
> OK. And what about __UNIXWARE__ and __OPENSERVER__ that I see being used [1]?
> On which versions are they defined?
>
> As it starts to get confusing, maybe you can clarify things by filling in this
> table?
>
>                  |  OpenServer 5    |  OpenServer 6   |  UnixWare 7     |
>                  |                  |                 |                 |
>                  | native  |  gcc   | native  |  gcc  | native  |  gcc  |
>                  |         |        |         |       |         |       |
> ----------------+---------+--------+---------+-------+---------+-------+
> _SCO_DS         |         |        |         |       |         |       |
>                  |         |        |         |       |         |       |
> __SCO_VERSION__ |         |        |         |       |         |       |
>                  |         |        |         |       |         |       |
> __UNIXWARE__    |         |        |         |       |         |       |
>                  |         |        |         |       |         |       |
> __OPENSERVER__  |         |        |         |       |         |       |
>                  |         |        |         |       |         |       |
> __sysv5__       |         |        |         |       |         |       |
> ----------------+---------+--------+---------+-------+---------+-------+
>
> Bruno
>
> [1] https://opensource.apple.com/source/X11misc/X11misc-10.1/makedepend/makedepend-1.0.1/imakemdep.h.auto.html
>


  parent reply	other threads:[~2020-10-06  2:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  3:30 Port getprogname module to SCO OpenServer Benji Wiebe
2020-10-01 15:59 ` Bruno Haible
     [not found]   ` <fd7272ba-fc7a-2204-ee0e-d6c8f3be35cd@gmail.com>
2020-10-03 14:08     ` Bruno Haible
2020-10-07  2:13       ` Benji Wiebe
2020-10-11 19:18         ` Bruno Haible
2020-10-01 18:59 ` Tim Rice
2020-10-02  0:52   ` Benji Wiebe
2020-10-03 13:54   ` Bruno Haible
2020-10-04  0:28     ` Tim Rice
2020-10-04  2:48       ` Bruno Haible
2020-10-06  0:10         ` Tim Rice
2020-10-06 21:21           ` Bruno Haible
2020-10-06  2:23         ` Benji Wiebe [this message]
2020-10-06  3:00           ` Tim Rice
2020-10-06 21:16           ` Bruno Haible
2020-10-06 21:47             ` Tim Rice
2020-10-06 22:01               ` Bruno Haible
2020-10-06 22:45                 ` Tim Rice

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64fe151c-bbe8-d2ad-8352-b112cee5e806@gmail.com \
    --to=benjiwiebe14@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=tim@multitalents.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).