Doesn't build with gccgo about go-python HOT 2 OPEN

hi Russel,

I haven't tested building go-python with gccgo in a long time (obviously)
but it seems something's broken with gccgo.

with the following little project, I could reproduce your issue:

$ cd /tmp/go-tmp
$ export GOPATH=`pwd`
$ mkdir -p src/foo
$ cd src/foo
$ cat > foo.go << EOF
package foo
import "fmt"
func Foo() {
 fmt.Printf("hello foo\n")
}
EOF

$ mkdir bar && cd bar
$ cat > bar.go << EOF
package main
import "foo"
func main() {
 foo.Foo()
}
EOF

$ go get -compiler=gccgo -v .
foo
foo/bar
# foo/bar
./bar.go:3:11: error: import file ‘foo’ not found
 import "foo"
           ^
./bar.go:6:2: error: reference to undefined name ‘foo’
  foo.Foo()
  ^
zsh: exit 2     go get -compiler=gccgo -v .

do you have the same gccgo version than I do ?

$ gccgo --version
gccgo (GCC) 4.8.1 20130725 (prerelease)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

wrt Python-3: I don't plan to migrate just yet as my workplace has yet to move away from py-2... but I'd be happy to open a python-3 branch and pull requests there :}

-s

from go-python.

My gccgo reports:

|> gccgo --version
gccgo (Debian 4.8.1-8) 4.8.1
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

wrt Python version, I would have thought your work would be champing at the bit to get to Python 3.3. What is the reason for staying with Python 2.7? I may well try and take a fork and feature branch for the C Python 3.3 API. I guess there is also PyPy to think about.

from go-python.