Fix makefile permissions in wsl

Question

0.00/5 (No votes)

See more:

I have a question that's two-thirds a linux question - maybe a WSL specific question - and a third embedded development toolchain question.

I really don't like dealing with the prima donnas at stackoverflow - not that everyone is that way but enough of them are, but I'm not sure codeproject is a great place to post this. It's kind of a long shot.

basically I'm running into a permissions problem running a makefile that chmod 777 -R isn't fixing. Curiously, running chmod *did* fix it earlier today on the same machine (i have a screen shot to prove to myself I'm not crazy). I stepped away from WSL for half a day and came back to the same prompt, ran the same command and it no work.

This is all using cross compilers, just to complicate everything.

I've unzipped two cross compiler toolchains to my home directory in WSL

I have a source tree called xboot whose makefile is set up to use cross compilers, so long as you point it to the appropriate compiler directory.

Earlier today, I attempted to run make ..., and even sudo make ... (arguments omitted) and ran into a Permission Denied error.
chmod 777 -R ~/arm-gcc seemed to fix this.

Later, I got the same error again.

I have a second toolchain for a slightly different ARM that I need to compile with. Again I run into permission problems.

I say this may be a WSL specific problem because I've never had this issue using a third party VM, like VMWare Player.

What I have tried:

chmod 777 -R ~/xboot
chmod 777 -R ~/arm-gnueabihf-gcc
make CROSS_COMPILE=/home/honey/arm-gnueabihf- PLATFORM=arm32-h3

Which yields

[ROMDISK] Packing romdisk
[CC] arch/arm32/lib/cpu/cmd-bootlinux.c
make[2]: /home/honey/arm-gnueabihf-gcc: Permission denied
make[2]: *** [rules.mk:33: .obj/arch/arm32/lib/cpu/cmd-bootlinux.o] Error 127
make[1]: *** [Makefile:346: arch/arm32/lib/cpu] Error 2
make: *** [Makefile:10: all] Error 2

I've also tried sudo with the same result

Putting child 0x55acbe333fe0 (.obj/arch/arm32/lib/cpu/cmd-bootlinux.o) PID 18847 on the chain.
Live child 0x55acbe333fe0 (.obj/arch/arm32/lib/cpu/cmd-bootlinux.o) PID 18847
[CC] arch/arm32/lib/cpu/cmd-bootlinux.c
Reaping winning child 0x55acbe333fe0 PID 18847
make[2]: /home/honey/arm-gnueabihf-gcc: Permission denied
make[2]: *** [rules.mk:33: .obj/arch/arm32/lib/cpu/cmd-bootlinux.o] Error 127
Reaping losing child 0x55733c1469c0 PID 18846
make[1]: *** [Makefile:346: arch/arm32/lib/cpu] Error 2
Removing child 0x55733c1469c0 PID 18846 from chain.
Reaping losing child 0x55a06f7ee8b0 PID 18831
make: *** [Makefile:10: all] Error 2
Removing child 0x55a06f7ee8b0 PID 18831 from chain.

rules.mk line 33 is this:

@$(CC) $(X_CFLAGS) $($(BASENAME)-flags) -MD -MP -MF $@.d $(X_INCDIRS) -c $< -o $@

Posted 26-Apr-23 20:08pm

honey the codewitch

Updated 4-May-23 3:58am

v5

Add a Solution

Comments

Peter_in_2780 27-Apr-23 2:59am

More likely occurring on an intermediate file, rather than toolchain component.
I'm guessing umask is set to something sane.
strace is the masochist's friend in cases like this; not sure how much trace you can crank up in make.

honey the codewitch 27-Apr-23 7:43am

I've tried strace, and I don't remember the result because it was when I first ran into this problem. I'll try again

[no name] 27-Apr-23 3:37am

Can you run ls -lR /home/honey/arm-gnueabihf-gcc, and show us the results?

honey the codewitch 27-Apr-23 7:43am

Here's a sample. It all looks like this (there's a lot of it)
-rwxr-xr-x 1 honey honey 10392 Jul 1 2021 FrameDecorator.py
-rwxr-xr-x 1 honey honey 1577 Jul 1 2021 FrameIterator.py
-rwxr-xr-x 1 honey honey 6758 Jul 1 2021 __init__.py
drwxr-xr-x 2 honey honey 4096 Jul 1 2021 command
-rwxr-xr-x 1 honey honey 8031 Jul 1 2021 frames.py
drwxr-xr-x 2 honey honey 4096 Jul 1 2021 function
drwxr-xr-x 2 honey honey 4096 Jul 1 2021 printer
-rwxr-xr-x 1 honey honey 10913 Jul 1 2021 printing.py
-rwxr-xr-x 1 honey honey 4209 Jul 1 2021 prompt.py
-rwxr-xr-x 1 honey honey 5530 Jul 1 2021 types.py
-rwxr-xr-x 1 honey honey 3137 Jul 1 2021 unwinder.py
-rwxr-xr-x 1 honey honey 11077 Jul 1 2021 xmethod.py

[no name] 27-Apr-23 8:30am

That all looks fine to me. I think you will need to use one of the debug options to make, to try and see what it is actually doing when the error occurs.

honey the codewitch 27-Apr-23 8:55am

I used strace and I can't figure out what this line means
make[2]: /home/honey/arm-gnueabihf-gcc: Permission denied

Is it trying to execute the directory?

[no name] 27-Apr-23 9:14am

Without seeing the Makefile and the debug output it's impossible to guess. Can you run it with the -d option and post the content and the debug output in the question?

honey the codewitch 27-Apr-23 10:17am

i just added the final part of the output to the question

[no name] 27-Apr-23 10:29am

As far as I can tell the issue is with the following:

make[2]: *** [rules.mk:33: .obj/arch/arm32/lib/cpu/cmd-bootlinux.o] Error 127

I have no idea what error 127 is, but the information suggests that the above path is incorrect or inaccessible. Not sure why the path begins with a full stop (period).

honey the codewitch 27-Apr-23 12:53pm

That's a good question. I assumed it was omitting something but I think you're right, that's the full path. Now I'm wondering why it worked before. I may have to unpack xboot again

[no name] 28-Apr-23 7:17am

It may be that some variable used in the Makefile to construct this path has not been set correctly.

honey the codewitch 28-Apr-23 7:20am

It's possible, but I have some difficulty assuming that because xboot is widely used for AllWinner chips (at least by Chinese folks), and I've had a heck of a time running down information on using it. Hard to search google in Chinese, at least for me. I'm going to try this on my VM again. I remember it worked there. It's less than ideal, but maybe it will give me some insight if i make with -d and compare the results. Gonna do it once I feel up to tackling it.

[no name] 28-Apr-23 7:31am

Good luck.

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

QuantumPlumber · Answer 1 · 2023-05-04T03:58:00

Solution 1

Have you tried a "make clean" before running your make command? Desperation, I know, but it might help if Peter's on the right track.

Posted 4-May-23 3:58am

QuantumPlumber

Comments

honey the codewitch 4-May-23 10:01am

Yes. I run make clean before I build. I got it working using an older version of the actual toolchain - not changing the build scripts at all. I still don't know why though, which is why I'm leaving this open.

Fix makefile permissions in wsl

1 solution

Solution 1

Add your solution here

Preview 0

Fix makefile permissions in wsl

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us