Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

user.Current panic in darwin-amd64 when crosscompiled from linux-amd64 #6376

Closed
calmh opened this issue Sep 12, 2013 · 2 comments
Closed

user.Current panic in darwin-amd64 when crosscompiled from linux-amd64 #6376

calmh opened this issue Sep 12, 2013 · 2 comments
Labels
FrozenDueToAge

Comments

@calmh
Copy link
Contributor

calmh commented Sep 12, 2013 

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What steps will reproduce the problem?

Compile and run http://play.golang.org/p/fI0-SKcrXR

This works as expected (i.e. prints current user details) on both linux-amd64 and
darwin-amd64. However, when using the cross compilation instructions at
http://dave.cheney.net/2012/09/08/an-introduction-to-cross-compilation-with-go to build
a darwin-amd64 binary from linux-amd64 it does not. Both environments running go 1.1.2
built from source.

What is the expected output?

jb@jborg-mbp:~ $ ./homedir-built-locally
&{502 20 jb Jakob Borg /Users/jb} <nil>

What do you see instead?

jb@jborg-mbp:~ $ ./homedir-crosscompiled-in-linux
<nil> user: Current not implemented on darwin/amd64

Which compiler are you using (5g, 6g, 8g, gccgo)?

8g

Which operating system are you using?

Linux, Mac OS X

Which version are you using?  (run 'go version')

b@ps-build1:~ % go version
go version go1.1.2 linux/amd64
@calmh
Copy link
Contributor Author

calmh commented Sep 12, 2013

Comment 1:

Eh. "panic" should of course be "returns error". There is no panic.

@minux
Copy link
Member

minux commented Sep 12, 2013

Comment 2:

os/user relies on cgo, and cgo is disabled for cross compiling,
thus this is expected.
if you use os/user, you must compile natively on OS X.
even if we enable cross compilation cgo support, I doubt everybody have
a working OS X cross toolchain on their linux machine.

Status changed to WorkingAsIntended.

@insasho insasho mentioned this issue Feb 16, 2015
Closed
@copumpkin copumpkin mentioned this issue Mar 27, 2015
Closed
@techtonik techtonik mentioned this issue Aug 22, 2015
Closed
yudai added a commit to yudai/gotty that referenced this issue Aug 23, 2015
@yudai
Replace user.Current() with os.Getenv("HOME")
ee45d8e 
`os/user.Current()` is not available on Darwin when a binary is cross
compiled from another platform.
See also: golang/go#6376
@wkentaro wkentaro mentioned this issue Aug 31, 2015
Closed
@tsenart tsenart mentioned this issue Sep 23, 2015
Closed
tsenart pushed a commit to mesosphere/mesos-dns that referenced this issue Sep 23, 2015
records: Find user's home directory through env
4b99d6c 
As reported in golang/go#6376,
`os/user.Current` doesn't work with cross-compilation.
This commit replaces its use with `os.Getenv` of the `$HOME` and
`$USERPROFILE` environment variables.

Fixes #275
@tsenart tsenart mentioned this issue Sep 23, 2015
Merged
ebartels added a commit to ebartels/hdfs that referenced this issue Oct 2, 2015
@ebartels
Use environment for determining user per golang/go#6376
2a52e9b
@ebartels ebartels mentioned this issue Oct 2, 2015
Merged
hlidotbe added a commit to epicagency/deploybot-cli that referenced this issue Oct 3, 2015
@hlidotbe
Replaced user.Current() by os.Getenv("HOME")
e0a3bb7 
user.Current() relies on cgo (well os/user does) and thus is not cross compilable
See golang/go#6376
@sudharsh sudharsh mentioned this issue Oct 12, 2015
Closed
@dmp42 dmp42 mentioned this issue Oct 15, 2015
Closed
@andrewrynhard andrewrynhard mentioned this issue Nov 6, 2015
Closed
@dreampuf dreampuf mentioned this issue Nov 10, 2015
Closed
@andreaskoch andreaskoch mentioned this issue Nov 16, 2015
Closed
andreaskoch added a commit to andreaskoch/allmark that referenced this issue Nov 17, 2015
@andreaskoch
Detect the user's home directory without user.Current()
09b235a 
user.Current() fails on Mac OS for binaries that have been
cross-compiled on another OS than Mac with the message:
"Error: user: Current not implemented on darwin/amd64"

Since this is, for some reason unclear to me, intended
behaviour by go (see: golang/go#6376)
I will use Mitchell Hachimoto's go-homedir library for
determining the current users home directory path.

I also fixed two failing unit tests that are unrelated to
this feature.

Fixes issue /issues/1
ebartels added a commit to ebartels/hdfs that referenced this issue Dec 21, 2015
@ebartels
Use environment for determining user per golang/go#6376
76080d9
colinmarc added a commit to colinmarc/hdfs that referenced this issue Jan 4, 2016
@colinmarc
Merge pull request #18 from ebartels/master
0a9180d 
Use environment for determining user per golang/go#6376
@darron darron mentioned this issue Jan 10, 2016
Closed
@avinashbot avinashbot mentioned this issue Feb 8, 2016
Closed
diwakergupta pushed a commit to dropbox/dbxcli that referenced this issue Mar 11, 2016
Don't use user.Current to get home directory.
ef12a5c 
This causes issues with cross-compilation due to
golang/go#6376

Use https://github.com/mitchellh/go-homedir instead.
@s-l-teichmann s-l-teichmann mentioned this issue Apr 15, 2016
Closed
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@calmh @minux @gopherbot