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

Added some missing dependencies for linux x-compile #438

Merged
merged 1 commit into from
Nov 18, 2015
Merged

Conversation

cbednarski
Copy link
Contributor

No description provided.

@cbednarski
Copy link
Contributor Author

This is still broken for me:

==> Getting dependencies...
==> Removing old directory...
==> Building...
Number of parallel builds: 7

-->   windows/amd64: github.com/hashicorp/nomad
-->       linux/386: github.com/hashicorp/nomad
-->    darwin/amd64: github.com/hashicorp/nomad
-->     windows/386: github.com/hashicorp/nomad
-->     linux/amd64: github.com/hashicorp/nomad

2 errors occurred:
--> linux/amd64 error: exit status 2
Stderr: # runtime/cgo
ld: unknown option: --build-id=none
clang: error: linker command failed with exit code 1 (use -v to see invocation)

--> linux/386 error: exit status 2
Stderr: # runtime/cgo
ld: unknown option: --build-id=none
clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [bin] Error 1

@cbednarski
Copy link
Contributor Author

Possibly related to #421

@carlosdp
Copy link
Contributor

@cbednarski I don't think so, I still get the ld error with #421, and os/user is still imported (just for the User struct)

Edit: though I guess removing os/user entirely could be worth a try?

@cbednarski
Copy link
Contributor Author

@carlosdp yeah I'm still not sure why the --build-id=none thing is happening but this fixes part of the problem.

cbednarski added a commit that referenced this pull request Nov 18, 2015
Added some missing dependencies for linux x-compile
@cbednarski cbednarski merged commit c56bb46 into master Nov 18, 2015
@cbednarski cbednarski deleted the b-makefile branch November 18, 2015 21:46
@carlosdp
Copy link
Contributor

I searched around but it's one of those errors that's too generic to be useful =(

@carlosdp
Copy link
Contributor

@cbednarski @mitchellh is there a reason you guys are still using goxc? Go 1.5 has really good cross-compiling out of the box now, did you guys evaluate it and find it to be insufficient?

I've just been compiling with GOOS=linux GOARCH=amd64 go build (etc.) for my builld.

@legal90
Copy link
Contributor

legal90 commented Nov 25, 2015

@cbednarski Have you already fixed that issue for you? Could you please share the solution? :)
Otherwise, it might be reasonable to open a new issue here...

2 errors occurred:
--> linux/386 error: exit status 2
Stderr: # runtime/cgo
ld: unknown option: --build-id=none
clang: error: linker command failed with exit code 1 (use -v to see invocation)

--> linux/amd64 error: exit status 2
Stderr: # runtime/cgo
ld: unknown option: --build-id=none
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@dadgar
Copy link
Contributor

dadgar commented Nov 25, 2015

I believe that issue is when compiling 386 on an amd64 version of linux without the correct headers.

@legal90
Copy link
Contributor

legal90 commented Nov 26, 2015

@dadgar In my case above this error occurred while building on OS X 10.11.

@dadgar
Copy link
Contributor

dadgar commented Nov 26, 2015

@legal90 yeah Nomad has cgo dependencies so you can't easily cross compile. Specifically user.Lookup

@github-actions
Copy link

github-actions bot commented May 2, 2023

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants