public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "boger at us dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/65462] New: Use of 'go get' with gccgo is not finding dependencies correctly Date: Wed, 18 Mar 2015 19:38:00 -0000 [thread overview] Message-ID: <bug-65462-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65462 Bug ID: 65462 Summary: Use of 'go get' with gccgo is not finding dependencies correctly Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: boger at us dot ibm.com CC: cmang at google dot com When using the go tool provided with gccgo in gcc 5.0, the use of 'go get' doesn't always find and build the dependent packages correctly. Here is an example: go get -u github.com/mitchellh/gox There is a dependent package github.com/mitchellh/iochan but that never gets downloaded or built and as a result neither does github.com/mitchellh/gox. I can make it work by downloading them in separate steps this way: go get -u github.com/mitchellh/uchan go get -u github.com/mitchellh/gox After further debugging I found the problem has to do with the code in libgo/go/cmd/go/pkg.go in the load function where it does this check: .... p1 := loadImport(path, p.Dir, stk, p.build.ImportPos[path]) if !reqPkgSrc && p1.Root == "" { continue } .... When it tries to load the github.com/mitchellh/uchan package, p1.Root == "" so it skips the rest of the code in the loop that loads the package. Isn't this a case where p1.Root should have a non-null string and therefore not continue/skip the rest of the body of the loop and get it loaded?
next reply other threads:[~2015-03-18 19:38 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-18 19:38 boger at us dot ibm.com [this message] 2015-03-20 17:27 ` [Bug go/65462] " boger at us dot ibm.com 2015-03-20 20:42 ` boger at us dot ibm.com 2015-03-20 20:43 ` ian at airs dot com 2015-03-20 20:45 ` boger at us dot ibm.com 2015-03-20 21:34 ` ian at airs dot com 2015-03-20 21:55 ` boger at us dot ibm.com 2015-03-24 22:13 ` 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-65462-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).