Skip to main content


when using a C compiler last patched nineteen years ago, on Solaris, there is this issue...

Today's episode in "ancient machines that never die" and they all (try to) run #curl.

#curl
This entry was edited (1 month ago)
in reply to daniel:// stenberg://

There is a lot more load-bearing antiquity out there than anyone realizes.
in reply to daniel:// stenberg://

do you still try to accommodate those users or is it impossible?
in reply to kaia

@kaia curl is written in ancient and very conservative C so it *usually* still works just fine. Sometimes with a little hands-on. But there are also the times when the machine is so special and ancient that it's hard to help much...
@kaia
in reply to daniel:// stenberg://

Aah, c'mon mate, don't tease. As someone with some love for ancient Solaris, I want to hear the story!
in reply to Andre

@PCOWandre https://github.com/curl/curl/issues/13317
in reply to daniel:// stenberg://

That's quite insane! I've never heard of anyone running such a vintage compiler on Solaris 11. I wouldn't have even expected it to work except for the seemingly timeless compatibility of SunOS.

I was doing plenty of active Solaris work on 8/9 in 2005 and I was almost exclusively building packages on Studio 8.

Hang on, hang on.

5.11. "SUNW,Ultra-60". Hang on. "snv_34".

So this is an alpha release of Solaris 11 that never made it to production release for any pre sun4v machines running a compiler from the vintage of the hardware rather than the operating system.

Cool, cool. A genuine basketcase build!

Thanks for the entertaining read.

in reply to daniel:// stenberg://

isn’t this the classic linker which expects ld.so to have all the link and compile time paths, lest you have to explicitly set -R and -L? I recall having a less than fond of opinion about libtool back in the day. Suffice to say it isn’t really a compiler issue per se?