On Thu, Dec 5, 2013 at 5:32 PM, John Meinel <[email protected]> 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.com closed. 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 > > 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 [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
