public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/65570] New: cannot find package "runtime/cgo" Date: Wed, 25 Mar 2015 20:09:00 -0000 [thread overview] Message-ID: <bug-65570-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65570 Bug ID: 65570 Summary: cannot find package "runtime/cgo" Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: doko at gcc dot gnu.org CC: cmang at google dot com the powerpc build now goes further, either the fix for PR go/65417 or PR go/65462 broke something on aarch64 and ppc64le, at least all lxd builds of ppc, ppc64le and aarch64 fail with: $ cat test.go package main /* #include <stdio.h> void hello() { printf("Hello world!\n"); } */ import "C" func main() { C.hello() } $ go build -v -x test.go WORK=/tmp/go-build985134900 package runtime/cgo: cannot find package "runtime/cgo" in any of: /usr/src/runtime/cgo (from $GOROOT) ($GOPATH not set) go install -v -x github.com/lxc/lxd/lxc package github.com/lxc/lxd/lxc imports github.com/gosexy/gettext imports runtime/cgo: cannot find package "runtime/cgo" in any of: /usr/src/runtime/cgo (from $GOROOT) /build/buildd/lxd-0.5/dist/src/runtime/cgo (from $GOPATH) debian/rules:19: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 1 Stephane posted a pointer to the complete build logs in https://launchpad.net/bugs/1436530
next reply other threads:[~2015-03-25 20:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 20:09 doko at gcc dot gnu.org [this message] 2015-03-25 21:45 ` [Bug go/65570] " ian at gcc dot gnu.org 2015-03-25 21:47 ` ian at airs dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-65570-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).