juju bootstrap w/ gccgo built cli and tools

[David Cheney]

Ok, good news first.

gccgo compiled tools work fine.

statically linking libgo also makes the tools as self contained as our gc
compiled ones.

Bad news,

jujud is 40mb, -Os or -O2 effect, in fact the latter makes it a bit larger

the binaries cannot be stripped, the debug data is required for operation
of the program, i'm guessing gccgo's reflection implementation requires the
debug symbols.

Dave



On Thu, Dec 5, 2013 at 5:42 PM, Andrew Wilkins <andrew.wilkins at canonical.com
> wrote:

> On Thu, Dec 5, 2013 at 2:37 PM, David Cheney <david.cheney at canonical.com>wrote:
>
>> On Thu, Dec 5, 2013 at 5:32 PM, John Meinel <john at arbash-meinel.com>
>> wrote:
>> > It sounds like we should be bundling the libgo.so into the tar.gz that
>> we
>> > are building. Either statically (so we dont have to worry about system
>> skew)
>> > or just have it know to load it in the same dir as the executable. We
>> > *could* try to use a system lib, but then we're back into dealing with
>> cross
>> > series version skew. (What version of libgo.so would we get on precise,
>>  vs
>> > trusty,  etc)
>>
>> Yup, _not_ linking it statically will be an entire dimension of hurt. So
>>
>> lucky(~/src/launchpad.net/juju-core) % go install -v -compiler gccgo
>> -gccgoflags=-static-libgo ./...
>>
>> did the business, and I could bootstrap, however ...
>>
>> Installing add-apt-repository
>>
>> Adding apt repository: deb
>> http://ubuntu-cloud.archive.canonical.com/ubuntu
>> precise-updates/cloud-tools main
>>
>> Running apt-get update
>>
>> Running apt-get upgrade
>>
>> Installing package: git
>>
>> Installing package: cpu-checker
>>
>> Installing package: mongodb-server
>>
>> Fetching tools: wget --no-verbose -O $bin/tools.tar.gz
>> '
>> https://s3-ap-southeast-2.amazonaws.com/juju-syd-en-ee-ii/tools/releases/juju-1.17.0.1-precise-amd64.tgz?AWSAccessKeyId=AKIAJ4SOKUWG25EDMAOA&Expires=1701757655&Signature=h2ujOoLJidL%2FEKTHnmOrAZ9e0A8%3D
>> '
>>
>> Starting MongoDB server (juju-db)
>>
>> Bootstrapping Juju machine agent
>>
>> Starting Juju machine agent (jujud-machine-0)
>>
>> Connection to ec2-54-253-158-49.ap-southeast-2.compute.amazonaws.comclosed.
>>
>> 2013-12-05 06:32:52 INFO juju supercommand.go:286 command finished
>>
>> lucky(~/src/launchpad.net/juju-core) % juju ssh 0
>>
>> WARNING discarding API open error: <nil>
>>
>> ERROR environment has no access-key or secret-key
>
>
> That's a bug with API-based secrets pushing. I have a CL pending.
> In the mean time, do "juju status" first.
>
> Nice work, btw.
>
>
>>
>> >
>> > Also I was surprised that the tar.gz is significantly bigger even
>> without
>> > libgo.so in it. (Lasting time I uploaded tools it was 4.6MB, your log
>> shows
>> > it as 5.5MB, and juju-1.10 was like 2.4MB IIRC)
>>
>> It's 10.4mb when libgo is linked statically.
>>
>> --
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20131206/be3a31f3/attachment-0001.html>