Re: Building and using shared libraries using gccgo
- To: Hilko Bengen <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: Building and using shared libraries using gccgo
- From: Michael Stapelberg <email@example.com>
- Date: Tue, 05 Feb 2013 00:14:52 +0100
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
Hilko Bengen <firstname.lastname@example.org> writes:
> Sure. See the Makefile at the end of this mail. Please note that I
Thanks for the instructions. I reproduced them and got shared libraries
plus dynamically linked binaries.
Aside from details about the split stack flags, now one big question
Assuming we ship Go libraries compiled as shared libraries, where do we
get the SONAME from? There is no mechanism for Go libraries to declare
an ABI break. Inventing one and asking all upstream projects to adopt it
seems unlikely to succeed. Ignoring SONAMEs altogether could make
software break on the user’s installation. Then again, the same could
happen to every interpreted language, e.g. Perl.
What do you think?