-
Notifications
You must be signed in to change notification settings - Fork 257
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
Build-error "use of internal package not allowed" when using Go 1.6 on ArchLinux #21
Comments
Looks like I missed a detail when I converted the packages to "internal",
and Go 1.6 is not happy about. I will take a look tomorrow!
|
Hmm. I cannot reproduce this, it builds just fine on my machine with Go 1.6. I have added Go 1.6 to the Travis build options, and it seems to work there as well: https://travis-ci.org/rfjakob/gocryptfs/jobs/120486918 |
Same issue here on ArchLinux. According to one member from the ArchLinux forum:
For information ArchLinux currently ships with openssl 1.0.2.g-3. |
I see. Maybe i can drop the dependency to spacemonkey and call openssl
directly.
|
Ok I have begun working on this, seems to be doable. Stay tuned, I think I can finish it next week. |
This will allow us to get rid of the dependency to spacemonkeygo/openssl that causes problems on Arch Linux ( #21 )
...complete with tests and benchmark. This will allow us to get rid of the dependency to spacemonkeygo/openssl that causes problems on Arch Linux ( #21 )
I have just released gocryptfs v0.10-rc1 that has dropped the dependency to spacemonkeygo. Please give it a try! |
Thanks. It compiles just fine now under ArchLinux. |
FYI, gocryptfs can now easily be compiled & installed on ArchLinux via AUR. |
Hi,
im currently trying to compile gocryptfs by using the bash script which ends in the following build error:
go build
produces the same result.Any hints or advice to overcome this build error. I am using Go 1.6.
BTW: Building with gcc-go results in
I installed openssl (there is no extra dev-Packge for ArchLinux) before.
The text was updated successfully, but these errors were encountered: