🚀 go-pugleaf

In article <LPC7LWD@mailgzrz.tu-berlin.de> Thomas Wolfram writes:

     Hi, I'm about to create shared X11R5 (X386 1.2E/XFree86) libraries
     for SVR3 (ISC 3.0) .... 

     I want to stick with gcc 2.2.2 and not go back to 1.40. But I don't
     want to init all unitilialized (most static) data in dozens of X source
     files only to force gcc 2.2.2 to put it to .data section.
    ...

     Does anybody know a better solution? Perhaps changing the init code
     for the target shared library? But how? 
     Or can I hope for a gcc 2.2.3 with a option "-fput-uninitialized-to-data"?

For the 386, Gcc 2.2 seems to have a "-msvr3-shlib" option.

I don't seem to have the docs describing it handly, but the code looks
as though it should do what you want.

This should probably really be a "-f" option (-fsvr3-shlib), since it
works around a generic sys5r3 problem in mkshlib that is not unique
to the 386, but also occurs on 3b2, 68k and other architectures
(unless the specific vendor has reworked mkshlib so that it's not a
problem - and nearly all have not done so).