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] Use of 'go get' with gccgo is not finding dependencies correctly Date: Fri, 20 Mar 2015 17:27:00 -0000 [thread overview] Message-ID: <bug-65462-4-Bf8kGI0oTG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65462-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65462 --- Comment #1 from boger at us dot ibm.com --- Created attachment 35077 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35077&action=edit Fix dependencies in go tool for gccgo The code to determine when to import packages was not quite catching the cases it should. It really needs to know what packages are part of the GO standard packages and not try to load those -- if they aren't then they should be loaded. This makes a few changes to the previous: - change the name of reqPkgSrc to reqStdPkgSrc to indicate when we should require the source for GO standard packages when loading packages. - generate the list of standard packages found in libgo and make that available to build into the go tool - set the flag Standard in the Package structure correctly for gccgo, based on the list of expected libgo standard packages - use the reqStdPkgSrc flag and the package.Standard flag to determine if the load of the package should be attempted
next prev parent reply other threads:[~2015-03-20 16:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-18 19:38 [Bug go/65462] New: " boger at us dot ibm.com 2015-03-20 17:27 ` boger at us dot ibm.com [this message] 2015-03-20 20:42 ` [Bug go/65462] " 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-Bf8kGI0oTG@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).