Comment 2 for bug 1292353

I can try, that will be burried somewhere in the Go tool

On Fri, Mar 14, 2014 at 7:05 PM, James Page <email address hidden> wrote:
> how about statically linking it - that's what the packaging in trusty
> currently does for ppc64el and arm64
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1292353
>
> Title:
> juju must install the libgo.so.5 library when required
>
> Status in juju-core:
> Triaged
>
> Bug description:
> Unlike golang-go compiled tools, gccgo compiled tools are not self
> contained.
>
> $ /var/lib/juju/tools/machine-1/jujud
> /var/lib/juju/tools/machine-1/jujud: error while loading shared libraries: libgo.so.5: cannot open shared object file: No such file or directory
>
> ubuntu@ubuntu-local-machine-1:~$ ldd /var/lib/juju/tools/machine-1/jujud
> linux-vdso64.so.1 => (0x00003fff86b70000)
> libgo.so.5 => not found
> libgcc_s.so.1 => /lib/powerpc64le-linux-gnu/libgcc_s.so.1 (0x00003fff86b48000)
> libc.so.6 => /lib/powerpc64le-linux-gnu/libc.so.6 (0x00003fff86988000)
> /lib64/ld64.so.2 (0x000000005b6b5000)
>
> For environments where gccgo compiled tools are going to be deployed
> we need to ensure that _all_ machines in the environment have this
> library installed by cloud init.
>
> This needs to happen before we try to setup the upstart jobs, because
> the daemons will not be able to start.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1292353/+subscriptions