I manually built a juju-core_1.19.0-0ubuntu1~14.04.1~juju1 arm64 deb from the source package in ppa:juju/devel (ppa doesn't have arm64 support itself). I did a manual provider bootstrap w/ --upload-tools and it failed with the error:
/var/lib/juju/tools/1.19.0.1-trusty-arm64/jujud: error while loading shared libraries: libgo.so.5: cannot open shared object file: No such file or directory
My previous successes have been using the Ubuntu packages, which build jujud statically w/ libgo. ppa:juju/devel links against libgo dynamically. The code changes necessary to build statically - if you elect to solve the problem that way - are straightforward if you diff the ubuntu and ppa debian subdirs of the source packages.
This is a bug in packaging, the tools should have been compiled with
the -gccgo-flags -shared-libgo option
On Wed, Apr 16, 2014 at 7:57 AM, dann frazier 1.19.0- 0ubuntu1~ 14.04.1~ juju1 arm64 deb juju/tools/ 1.19.0. 1-trusty- arm64/jujud: error while loading bootstrap- 1.19.0. log" /bugs.launchpad .net/bugs/ 1308263/ +attachment/ 4084819/ +files/ juju-manual- bootstrap- 1.19.0. log /bugs.launchpad .net/bugs/ 1308263 juju/tools/ 1.19.0. 1-trusty- arm64/jujud: error while loading 1.19.0- 0ubuntu1~ 14.04.1~ juju1 arm64 deb juju/tools/ 1.19.0. 1-trusty- arm64/jujud: error while loading /bugs.launchpad .net/juju- core/+bug/ 1308263/ +subscriptions
<email address hidden> wrote:
> Public bug reported:
>
> I manually built a juju-core_
> from the source package in ppa:juju/devel (ppa doesn't have arm64
> support itself). I did a manual provider bootstrap w/ --upload-tools and
> it failed with the error:
>
> /var/lib/
> shared libraries: libgo.so.5: cannot open shared object file: No such
> file or directory
>
> My previous successes have been using the Ubuntu packages, which build
> jujud statically w/ libgo. ppa:juju/devel links against libgo
> dynamically. The code changes necessary to build statically - if you
> elect to solve the problem that way - are straightforward if you diff
> the ubuntu and ppa debian subdirs of the source packages.
>
> ** Affects: juju-core
> Importance: Undecided
> Status: New
>
>
> ** Tags: hs-arm64
>
> ** Attachment added: "juju-manual-
> https:/
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https:/
>
> Title:
> /var/lib/
> shared libraries: libgo.so.5: cannot open shared object file: No such
> file or directory
>
> Status in juju-core:
> New
>
> Bug description:
> I manually built a juju-core_
> from the source package in ppa:juju/devel (ppa doesn't have arm64
> support itself). I did a manual provider bootstrap w/ --upload-tools
> and it failed with the error:
>
> /var/lib/
> shared libraries: libgo.so.5: cannot open shared object file: No such
> file or directory
>
> My previous successes have been using the Ubuntu packages, which build
> jujud statically w/ libgo. ppa:juju/devel links against libgo
> dynamically. The code changes necessary to build statically - if you
> elect to solve the problem that way - are straightforward if you diff
> the ubuntu and ppa debian subdirs of the source packages.
>
> To manage notifications about this bug go to:
> https:/