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

Cannot run make '/bin/sh: 1: : Permission denied' #13250

Closed
SiegeLord opened this issue Apr 1, 2014 · 5 comments
Closed

Cannot run make '/bin/sh: 1: : Permission denied' #13250

SiegeLord opened this issue Apr 1, 2014 · 5 comments
Assignees

Comments

@SiegeLord
Copy link
Contributor

Here's the sequence of events that lead up to the error:

  1. I updated a dirty directory to the newest master via git pull this morning to commit b8ef9fd
  2. I ran make -j8 || make -j8
  3. I ran sudo make install

At this point I was greeted with:

/bin/sh: 1: : Permission denied
cfg: build triple 
cfg: host triples 
cfg: target triples 
cfg: enabling more debugging (CFG_ENABLE_DEBUG)
cfg: using 
mk/platform.mk:131: *** please try on a system with gcc or clang.  Stop.

Invoking make again (even under sudo) produces the same set of messages.

OS: Ubuntu 13.10

@SiegeLord
Copy link
Contributor Author

cc @brson

@brson brson self-assigned this Apr 1, 2014
@brson
Copy link
Contributor

brson commented Apr 1, 2014

I'll investigate.

@brson
Copy link
Contributor

brson commented Apr 1, 2014

I haven't been able to reproduce this, but hope it's related to #13190, which I fixed yesterday.

@SiegeLord
Copy link
Contributor Author

Removing those two files didn't help.

While trying to get to the bottom of this, I accidentally deleted config.mk which required me to re-run the configure script. Doing so un-broke make, but meant that I had no chance to figure out why this happened. Either way, hopefully it won't happen again.

@pnkfelix
Copy link
Member

pnkfelix commented Apr 2, 2014

@SiegeLord if it happens again, I recommend you try debugging the result with remake, the GNU Make debugger, passing the --trace option to get readable output explaining what make is doing and why.

http://bashdb.sourceforge.net/remake/

apt-get install remake

Jarcho pushed a commit to Jarcho/rust that referenced this issue Aug 24, 2024
lintcheck: key lints on line start rather than byte start/end

Before: https://github.com/rust-lang/rust-clippy/actions/runs/10305798317
After: https://github.com/Alexendoo/rust-clippy/actions/runs/10333749860

If a single lint emits e.g. twice on the same line and the messages change for both there would still be two changed entries

Also slightly changes the output, the URL is no longer visible

r? `@xFrednet`

changelog: none
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

No branches or pull requests

3 participants