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

No longer builds after scons -c #330

Closed
x-qq opened this issue Jan 28, 2023 · 2 comments
Closed

No longer builds after scons -c #330

x-qq opened this issue Jan 28, 2023 · 2 comments
Labels
bug meta Related to the build system or other things other than the code

Comments

@x-qq
Copy link
Contributor

x-qq commented Jan 28, 2023

Running scons -c inside the git checkout directory where build worked before somehow leads to this:

% scons
scons: Reading SConscript files ...                                           
Building for: posix
Using toolchain: default
C++ compiler: g++
Checking whether the C compiler works... no
There's a problem with your compiler!

Removing .sconsign.dblite seems to fix it.

@x-qq x-qq changed the title Does not build on debian with g++ 12 No longer builds after scons -c Jan 28, 2023
@NQNStudios
Copy link
Collaborator

I'm able to reproduce this.

Here's what I dug up about .sconsign.dblite:

The .sconsign.dblite file is a temporary database used by SCons to keep file signatures to speed up future builds. If you delete it, SCons will recreate it (and your next build might take slightly longer because of that). It should not be put under version control.

(from https://stackoverflow.com/a/12867804)

So, SConstruct is marking that file for deletion, and it's getting recreated after scons -c is called.

Weirdly, scons -c still creates this bug, even after I tried changing SConstruct to not mark the dblite file for deletion.

@NQNStudios
Copy link
Collaborator

NQNStudios commented May 25, 2024

The conversation here indicates that you're not supposed to delete .sconsign.dblite from your SConstruct file, but scons -c breaks the next build even if we don't do that, so it seems like we do need to delete it. I tried the weird atexit workaround shown in that issue, and then it worked.

@CelticMinstrel CelticMinstrel added bug meta Related to the build system or other things other than the code labels Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug meta Related to the build system or other things other than the code
Projects
None yet
Development

No branches or pull requests

3 participants