Gccgo -I $WORK -I /home/ubuntu/juju-build/juju-core-1.24-alpha1/pkg/gccgo_linux_ppc64 -c -g -fgo-pkgpath=gopkg.in/macaroon.v1 -fgo-relative-import-path=_/home/ubuntu/juju-build/juju-core-1.24-alpha1/src/gopkg.in/macaroon.v1 -o $WORK/gopkg.in/macaroon.v1/_obj/macaroon.o. Gccgo -I $WORK -I /home/ubuntu/juju-build/juju-core-1.24-alpha1/pkg/gccgo_linux_ppc64 -c -g -fgo-pkgpath=/juju/juju/tools -fgo-relative-import-path=_/home/ubuntu/juju-build/juju-core-1.24-alpha1/src//juju/juju/tools -o $WORK//juju/juju/tools/_obj/tools.o. juju-core_1.ĭpkg-source: warning: ignoring deletion of file src//juju/xml/xml.go.origĭpkg-source: warning: ignoring deletion of file src//juju/xml/read_test.go.origĭpkg-source: warning: ignoring deletion of file src//juju/xml/marshal.go.origĭpkg-source: warning: ignoring deletion of file src//juju/xml/marshal_test.go.origĭpkg-source: info: building juju-core in juju-core_1.24-alpha1-0ubuntu1~14.04.1~ĭpkg-source: info: building juju-core in juju-core_1.24-alpha1-0ubuntu1~14.04.1~juju1.dsc Instead we see calls to 'go install' each binary required by the package.ĭpkg-source: info: building juju-core using existing. We don't see a specific call to 'go build'. Reviewing we can see that the binary package can be installed. com/juju/ juju/environs/ tools/_ obj/tools. com/juju/ juju/environs/ tools -o $WORK/github. com/juju/ juju/environs/ tools -fgo-relative- import- path=_/ home/ubuntu/ juju-build/ juju-core- 1.24-alpha1/ src/github. Gccgo -I $WORK -I /home/ubuntu/ juju-build/ juju-core- 1.24-alpha1/ pkg/gccgo_ linux_ppc64 -c -g -fgo-pkgpath= github. com/juju/ juju/environs/ imagemetadata/ _obj/imagemetad ata.o. com/juju/ juju/environs/ imagemetadata -o $WORK/github. com/juju/ juju/environs/ imagemetadata -fgo-relative- import- path=_/ home/ubuntu/ juju-build/ juju-core- 1.24-alpha1/ src/github. v1 -fgo-relative- import- path=_/ home/ubuntu/ juju-build/ juju-core- 1.24-alpha1/ src/gopkg. Gccgo -I $WORK -I /home/ubuntu/ juju-build/ juju-core- 1.24-alpha1/ pkg/gccgo_ linux_ppc64 -c -g -fgo-pkgpath= gopkg.in/ macaroon. com/juju/ juju/tools -fgo-relative- import- path=_/ home/ubuntu/ juju-build/ juju-core- 1.24-alpha1/ src/github. '? The calls to install just the needed binaries may be working with a subset of the source code that is sane.Ī successful binary packages makes these calls 4 calls involving marshall tar.gzĭpkg-source: info: building juju-core in juju-core_ 1.24-alpha1- 0ubuntu1~ 14.04.1~ juju1.dscĬould gccgo be trying the compile the. origĭpkg-source: info: building juju-core in juju-core_ 1.24-alpha1- 0ubuntu1~ 14.04.1~ bian. go.origĭpkg-source: warning: ignoring deletion of file src/github. origĭpkg-source: warning: ignoring deletion of file src/github. gzĭpkg-source: warning: ignoring deletion of file src/github. Instead we see calls to 'go install' each binary required by the package.Īll builds of the packages warn about the orig files left in the tree:ĭpkg-source: info: using source format `3.0 (quilt)'ĭpkg-source: info: building juju-core using existing. ws/juju- ci/products/ version- 2524/publish- revision/ build-1677/ consoleText we can see that the binary package can be installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |