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

Add a fallback way to determine the home path. #3

Closed
wants to merge 1 commit into from
Closed

Add a fallback way to determine the home path. #3

wants to merge 1 commit into from

Conversation

s-l-teichmann
Copy link

On linux/386 systems Parse (in wego) fails with something like:
"[...]
2016/04/15 12:13:04 Error parsing config: user: Current not implemented on linux/386
You can set the environment variable WEGORC to point to your config file as a workaround
[...]"

Before restorting to WEGORC we should try the HOME env variable first.

On linux/386 systems Parse (in wego) fails with something like:
"[...]
2016/04/15 12:13:04 Error parsing config: user: Current not implemented on linux/386
You can set the environment variable WEGORC to point to your config file as a workaround
[...]"

Before restorting to WEGORC we should try the HOME env variable first.
@schachmat
Copy link
Owner

The Problem is probably that you are using the gccgo package instead of the golang-go package of your distribution. I don't know why, but gccgo doesn't seem to be able to implement that functionality, while it works perfectly from the golang sources.

I don't want to introduce codepaths which might not work on all architectures (It is not defined for all of them what $HOME and $UserProfile should link to) when we have a whole programming language team dedicated to unify the interface for all supported platforms.

@s-l-teichmann
Copy link
Author

Actually it was cross compile with gc Go 1.6.1. When compiling it natively it works.
os.user depends on cgo.

See golang/go#6376

@schachmat
Copy link
Owner

Ah, thanks for the reference.

@schachmat schachmat closed this Apr 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants