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

make -j 4 doesn't work properly #19

Open
mikrosk opened this issue Jan 12, 2023 · 7 comments
Open

make -j 4 doesn't work properly #19

mikrosk opened this issue Jan 12, 2023 · 7 comments

Comments

@mikrosk
Copy link
Member

mikrosk commented Jan 12, 2023

I rarely use the -j switch but somehow I had the feeling that at least gemlib and mintlib are parallel-builds friendly? However that doesn't seem to be the case, only the following folders are created: .lib020, .lib16, .lib, .lib02016

@th-otto
Copy link
Contributor

th-otto commented Jan 12, 2023

Works as expected for me, and creates all 6 folders.

I recently update my system, but i use make -j8 all the time, especially with gemlib, where it makes a big difference in compilation times, and it always worked.

mintlib should work too. Only project which sometimes seem to cause trouble is the freemint kernel.

@mikrosk
Copy link
Member Author

mikrosk commented Jan 12, 2023

That's odd. I refuse to believe that it is caused by some WSL difference, most likely my build is just a bit slower due to virtualization.

Is there something I could check? I started with clean source tree.

@th-otto
Copy link
Contributor

th-otto commented Jan 12, 2023

Are you using the linux version of gcc-m68k-atari-mint-gcc on WSL? Maybe you can also try the mingw version, available on my site. Maybe you need MSYS2 for a bash.

@mikrosk
Copy link
Member Author

mikrosk commented Jan 12, 2023

Are you using the linux version of gcc-m68k-atari-mint-gcc on WSL

Indeed.

I'll test it in other environments, I vaguely remember trying -j at home and it worked.

@th-otto
Copy link
Contributor

th-otto commented Mar 14, 2023

Today i had a similar issue. make -j8 did not fail, but apparently did not rebuild anything. Running it again solved it.

Such issues are a pain. They are hard to track, because they depend on the order on how the commands are run.

@mikrosk
Copy link
Member Author

mikrosk commented Mar 14, 2023

Yeah, for that reason I rarely use the -j switch - our projects are small and usually don't require full recompilation.

@th-otto
Copy link
Contributor

th-otto commented Mar 14, 2023

But for gemlib that isn't the case. Its not large, but there are a lot of small files, and make -j makes a big difference. And any change to mt_gem.h will trigger a full recompilation.

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

2 participants