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

Fix build issues on macOS and general build improvements #71

Merged
merged 4 commits into from
Oct 18, 2019
Merged

Fix build issues on macOS and general build improvements #71

merged 4 commits into from
Oct 18, 2019

Conversation

Robertof
Copy link
Contributor

This PR addresses the issues found in #46. In particular:

  • the configure script depends on bash 4, but gave a particularly bland message. This makes it print a special message for macOS users suggesting how to upgrade bash to version 4 (as by default macOS ships with version 3)
  • The task golangci-lint in Makefile.tools had a missing $ in a shell evaluation leading to an incorrect path being used for the linting tool
  • kubebuilder is now being installed in /usr/local/opt instead of /usr/local by default as that directory is writable by default on macOS.

\o/ Hacktoberfest!

This adds a helpful tip for macOS users which suggests to use Homebrew
to upgrade the Bash version, as macOS ships with Bash 3 by default.
A dollar sign was incorrectly missing in `Makefile.tools` which
prevented the correct execution of the `go` command to extract the
`GOPATH`.
This retrocompatible change shifts the default install directory of
`kubebuilder` to `/usr/local/opt`, which is by default writable by
non-root users on macOS. This preserves the old `$PATH` entry of
`kubebuilder` for retrocompatibility.
@pusher-ci
Copy link

Hi @Robertof. Thanks for your PR.

I'm waiting for a pusher member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link
Collaborator

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for the fixes! 😍

@JoelSpeed
Copy link
Collaborator

/ok-to-test

@Robertof
Copy link
Contributor Author

@JoelSpeed do these look legit/familiar to you? Looking at the logs it doesn't seem like they're related to the tooling

@JoelSpeed
Copy link
Collaborator

@Robertof There are (unfortunately) a few tests which flake every now and then, I've set them to rerun, definitely not related to your changes!

@JoelSpeed JoelSpeed merged commit 4d4c0ca into wave-k8s:master Oct 18, 2019
@Robertof Robertof deleted the build-tools-fixes branch October 18, 2019 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants