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

Makefile:1: *** missing separator. Stop. #88808

Closed
HtcOrange opened this issue Mar 4, 2020 · 10 comments
Closed

Makefile:1: *** missing separator. Stop. #88808

HtcOrange opened this issue Mar 4, 2020 · 10 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.

Comments

@HtcOrange
Copy link

I want to use kubemark to test the cluster. But when I wanna to install it by source code, in the step of compiling, the error occured as follows:

archlab@GG-135:~/gocode/src/k8s.io/kubernetes$ KUBE_BUILD_PLATFORMS=linux/amd64  make kubemark GOFLAGS=-v GOGCFLAGS="-N -l"
Makefile:1: *** missing separator.  Stop.

And the Makefile is only one line:

build/root/Makefile
# There is no "tab" or "space" in front of the line above

Could someone tell me what is the problem? I am so eager to know what was wrong with me? Thank you very much!!!

@HtcOrange HtcOrange added the kind/support Categorizes issue or PR as a support question. label Mar 4, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 4, 2020
@neolit123
Copy link
Member

/sig scalability

@k8s-ci-robot k8s-ci-robot added sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 4, 2020
@SupermanCj
Copy link

Hello, I also encountered the same problem. have you solved the problem?

@oxddr
Copy link
Contributor

oxddr commented Apr 3, 2020

I wasn't able to reproduce it at HEAD. KUBE_BUILD_PLATFORMS=linux/amd64 make kubemark GOFLAGS=-v GOGCFLAGS="-N -l" worked just fine.

Could you try to re-run make at the current HEAD?

@tlereste
Copy link
Contributor

I had the same problem.

Here is a workaround :

Remove the Makefile and Makefile.generated_files files :
rm Makefile Makefile.generated_files

Create the symlinks :
ln -s build/root/Makefile Makefile
ln -s build/root/Makefile.generated_files Makefile.generated_files

This solution worked for me !

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 25, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 24, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

@samaiyayashraj
Copy link

Hi,
I'm having the same issue on my windows machine. Is there any workaround for this.?

@wwj-2017-1117
Copy link

I'm having the same issue on arm + cenos. Is there any workaround for this.?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
Projects
None yet
Development

No branches or pull requests

9 participants