"Peter J. Holzer" <hjp-pgsql@xxxxxx> writes: > On 2023-12-22 10:31:14 -0500, Tom Lane wrote: >> Binaek Sarkar <binaek@xxxxxxxxxx> writes: >>> Interestingly, the *build completes successfully when the .a file is >>> smaller* (around 100 MB). >> Pure luck I suspect. > I seem to remember a 256MB limit for position independent code on x86. > The current man-page for GCC doesn't mention such a limit, though, so I > may be mistaken. At least on x86, there is/was a shlib size boundary beyond which you needed to generate different instructions with wider offset fields in order to have position-independent code. Thus the difference between -fpic and -fPIC. It's at least possible that the OP's Go toolchain automatically uses -fpic, but I'm suspicious of that theory. Usually you don't use either switch when building .a libraries. regards, tom lane
