Xref: utzoo comp.unix.xenix:3572 comp.bugs.sys5:612
Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!uflorida!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.xenix,comp.bugs.sys5
Subject: Re: globals in libraries
Message-ID: <8657@smoke.ARPA>
Date: 7 Oct 88 20:44:28 GMT
References: <167@libove.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <167@libove.UUCP> root@libove.UUCP (Jay M. Libove) writes:
>[ I know that this is a Sys5 _feature_ and not a bug, but it is of concern
>  to the Sys5 audience in general as well as the Xenix audience... ]
>It seems that Xenix, and indeed Sys5 in general, are unwilling (in their
>default "ar"chiver/library-manager) to store globals in a library as such:

To the contrary, UNIX System V does NOT have the bug you report.
Your problem stems from some port of what is apparently an old
(pre-System V) version of PCC and the Berkeley linker suite.
The "int argle;" is supposed to generate a .data, not a .lcomm,
and System V doesn't even have "ranlib".

Complain to your compiler vendor.