Doesn't compile

Question

Doesn't compile

jbrukh opened this issue 13 years ago · 12 comments

I get

6g -o _go_.6 build.go deps.go gb.go goinstall.go make.go pkg.go gofmt.go runext.go util.go files.go usage.go cgo.go query.go genmake.go 
gb.go:92: undefined: os.Create
gb.go:225: undefined: os.Create
pkg.go:412: not enough arguments in call to os.Open
pkg.go:760: undefined: os.Create
pkg.go:1103: undefined: os.Create
files.go:54: not enough arguments in call to os.Open
files.go:90: not enough arguments in call to os.Open
files.go:105: not enough arguments in call to os.Open
files.go:161: not enough arguments in call to os.Open
files.go:167: undefined: os.Create
files.go:167: too many errors
make: *** [_go_.6] Error 1

This is on Darwin with release.r56

Answer 1 · 2011-04-23T02:54:14.000Z

Hi,

If you take a look at https://github.com/skelterjohn/gb-release then that version should compile with the latest release. I'm not sure how to work both release and tip versions into one repository, so sorry about that.

John

Answer 2 · 2011-04-23T05:11:35.000Z

Hey John,

Thanks for the tip. If you'd like to follow both tip and release versions
of Go, why not have two separate branches instead of two separate
repositories?

Thanks,
Jake

On Fri, Apr 22, 2011 at 10:54 PM, skelterjohn <
reply@reply.github.com>wrote:

Hi,

If you take a look at https://github.com/skelterjohn/gb-release then that
version should compile with the latest release. I'm not sure how to work
both release and tip versions into one repository, so sorry about that.

John

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 3 · 2011-04-23T13:34:34.000Z

hmm. What happens if you clone go-gb and then checkout release? I do have two branches on my local git, I just wasn't sure how to push both of them to github...

Answer 4 · 2011-04-23T16:41:41.000Z

You'll need to push your local branches explicitly to github for them to
appear:

$ git push origin mylocalbranch

You can also do the following: keep two local branches such as "tip" and
"release", then tag them appropriately and push them to github. Then users
can just checkout by tag. You do:

  $ git checkout release

$ git commit -a -m "Up to date with release.r56." $ git tag gb-release.r56 $ git push origin release --tags

User does:

  $ git clone <your repo>

$ git checkout gb-release.r56

--Jake

On Sat, Apr 23, 2011 at 9:34 AM, skelterjohn <
reply@reply.github.com>wrote:

hmm. What happens if you clone go-gb and then checkout release? I do have
two branches on my local git, I just wasn't sure how to push both of them to
github...

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 5 · 2011-04-23T17:07:00.000Z

Thanks!

"git checkout gb-release.r56" does it, now.

Answer 6 · 2011-04-23T18:53:29.000Z

Looks great, thanks!

On Sat, Apr 23, 2011 at 1:07 PM, skelterjohn <
reply@reply.github.com>wrote:

Thanks!

"git checkout gb-release.r56" does it, now.

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 7 · 2011-04-23T19:29:11.000Z

By the way, great job on the tool, definitely very useful. I'm writing a
data structures library in multiple packages and I thought I was going to
kill myself with makefiles. :)

Thanks again,
Jake

On Sat, Apr 23, 2011 at 2:53 PM, Jake Brukhman jbrukh@gmail.com wrote:

Looks great, thanks!

On Sat, Apr 23, 2011 at 1:07 PM, skelterjohn <
reply@reply.github.com>wrote:

Thanks!

"git checkout gb-release.r56" does it, now.

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 8 · 2011-04-26T01:26:20.000Z

Hey John,

I noticed that gb -t from gb-release.r56 doesn't work; this seems to be due
to the fact that testing.RunTests is no longer an exported function of that
package:

_test/_testmain.go:16: undefined: testing.RunTests

Any thoughts on this? Maybe just running gotest in each target dir would be
enough...

Thanks,
Jake.

On Sat, Apr 23, 2011 at 3:28 PM, Jake Brukhman jbrukh@gmail.com wrote:

By the way, great job on the tool, definitely very useful. I'm writing a
data structures library in multiple packages and I thought I was going to
kill myself with makefiles. :)

Thanks again,
Jake

On Sat, Apr 23, 2011 at 2:53 PM, Jake Brukhman jbrukh@gmail.com wrote:

Looks great, thanks!

On Sat, Apr 23, 2011 at 1:07 PM, skelterjohn <
reply@reply.github.com>wrote:

Thanks!

"git checkout gb-release.r56" does it, now.

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 9 · 2011-04-26T02:42:16.000Z

Ah, the problem is that I made the r56 version by rolling back some code
rather than tagging when r56 came out... and I tested building but not
testing. The code generated for testing works with tip :)

I'll take a look at this tomorrow.

On Mon, Apr 25, 2011 at 9:26 PM, jbrukh <
reply@reply.github.com>wrote:

Hey John,

I noticed that gb -t from gb-release.r56 doesn't work; this seems to be due
to the fact that testing.RunTests is no longer an exported function of that
package:

_test/_testmain.go:16: undefined: testing.RunTests

Any thoughts on this? Maybe just running gotest in each target dir would be
enough...

Thanks,
Jake.

On Sat, Apr 23, 2011 at 3:28 PM, Jake Brukhman jbrukh@gmail.com wrote:

By the way, great job on the tool, definitely very useful. I'm writing a
data structures library in multiple packages and I thought I was going to
kill myself with makefiles. :)

Thanks again,
Jake

On Sat, Apr 23, 2011 at 2:53 PM, Jake Brukhman jbrukh@gmail.com wrote:

Looks great, thanks!

On Sat, Apr 23, 2011 at 1:07 PM, skelterjohn <
reply@reply.github.com>wrote:

Thanks!

"git checkout gb-release.r56" does it, now.

Reply to this email directly or view it on GitHub:
#11 (comment)

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 10 · 2011-04-26T02:43:49.000Z

No worries, thanks for taking a look.

On Mon, Apr 25, 2011 at 10:42 PM, skelterjohn <
reply@reply.github.com>wrote:

Ah, the problem is that I made the r56 version by rolling back some code
rather than tagging when r56 came out... and I tested building but not
testing. The code generated for testing works with tip :)

I'll take a look at this tomorrow.

On Mon, Apr 25, 2011 at 9:26 PM, jbrukh <
reply@reply.github.com>wrote:

Hey John,

I noticed that gb -t from gb-release.r56 doesn't work; this seems to be
due
to the fact that testing.RunTests is no longer an exported function of
that
package:

_test/_testmain.go:16: undefined: testing.RunTests

Any thoughts on this? Maybe just running gotest in each target dir would
be
enough...

Thanks,
Jake.

On Sat, Apr 23, 2011 at 3:28 PM, Jake Brukhman jbrukh@gmail.com wrote:

By the way, great job on the tool, definitely very useful. I'm writing
a
data structures library in multiple packages and I thought I was going
to
kill myself with makefiles. :)

Thanks again,
Jake

On Sat, Apr 23, 2011 at 2:53 PM, Jake Brukhman jbrukh@gmail.com
wrote:

Looks great, thanks!

On Sat, Apr 23, 2011 at 1:07 PM, skelterjohn <
reply@reply.github.com>wrote:

Thanks!

"git checkout gb-release.r56" does it, now.

Reply to this email directly or view it on GitHub:
#11 (comment)

Reply to this email directly or view it on GitHub:
#11 (comment)

Reply to this email directly or view it on GitHub:
#11 (comment)

Answer 11 · 2011-05-04T18:43:36.000Z

I feel a bit bad, but I solved your issue by waiting for release 57 to come out. You can get it with either the release or gb-release.r57 tag (both are the same as tip when I write this comment).

Answer 12 · 2011-05-04T18:45:07.000Z

Don't feel bad! Thanks for the heads up.

--Jake

On Wed, May 4, 2011 at 2:43 PM, skelterjohn <
reply@reply.github.com>wrote:

I feel a bit bad, but I solved your issue by waiting for release 57 to come
out. You can get it with either the release or gb-release.r57 tag (both are
the same as tip when I write this comment).

Reply to this email directly or view it on GitHub:
#11 (comment)