From: Tim Rice <tim@multitalents.net>
To: Benji Wiebe <benjiwiebe14@gmail.com>
Cc: bug-gnulib@gnu.org
Subject: Re: Port getprogname module to SCO OpenServer
Date: Thu, 1 Oct 2020 11:59:47 -0700 (PDT) [thread overview]
Message-ID: <alpine.UW2.2.11.2010011138270.23837@server01.int.multitalents.net> (raw)
In-Reply-To: <f128e8bf-cb13-fbf7-ca0a-00ffedcb6374@gmail.com>
Hi Benji,
On Wed, 30 Sep 2020, Benji Wiebe wrote:
> I ported the getprogname module to SCO OpenServer 6 (should also work on OSR5
> and UnixWare). It prevents several OSS packages from building.
No proc filesystem on Openserver 5 so it will not work there. Would
need a different "#ifdef" for 5 anyway.
> I just made it read from /proc/<pid>/cmdline to get the command name. The
> patch is below. Comments are welcome. Thanks!
Note reading /proc/<pid>/cmdline will limit you to a 79 char pathname.
And your program limits to 49.
>
> +# 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__
--
Tim Rice Multitalents
tim@multitalents.net
next prev parent reply other threads:[~2020-10-01 19:00 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 [this message]
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
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=alpine.UW2.2.11.2010011138270.23837@server01.int.multitalents.net \
--to=tim@multitalents.net \
--cc=benjiwiebe14@gmail.com \
--cc=bug-gnulib@gnu.org \
/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).