[libgo, build] Use convenience libraries to create .gox files

[Rainer Orth]

Ian Lance Taylor <iant@google.com> writes:

> Thanks for doing this.  However, there is a simpler way, which I've
> implemented below.  There is really no need for the .a file at all.  It
> was needed when Go packages were built differently.  Now building a Go
> package requires passing all the input files at once, so we can know
> just build a .o file, rather than building a .o file and then putting it
> into a .a file.
>
> The patch below implements this scheme.  Bootstrapped and ran Go
> testsuite on x86_64-unknown-linux-gnu.  Committed to mainline.

Excellent, thanks.

>> It would be nice if the second step could be implemented using
>> e.g. simple-object to avoid the external dependency.  Any suggestions on
>> how to handle .go_object on non-ELF platforms without named sections
>> (Tru64 UNIX with ECOFF in my case)?  I suppose I should have a look at
>> LTO on PE-COFF for ideas.
>
> Hmmm, ECOFF is going to be tricky.  Unlike COFF, ECOFF does not support
> arbitrary section names.  Offhand I don't know how it could be made to
> work.

I just had a look at the Tru64 UNIX Object File and Symbol Table Format
Specification: it seems that the .comment section could be used for this
purpose:

http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/SUPPDOCS/OBJSPEC/NV150XXX.HTM

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University