cc1 Fatal Error: No such file or directory, generated files visible in file explorer #1499
Labels
bug
Something isn't working
Comments
|
Hi @Rchanjobe I'm seeing what I can do to reproduce the issues you're seeing, from what you describe it sounds like it's writing the files correctly but then failing to find them again during compilation. Out of interest does your username contain any non-ascii characters (anything that isn't A-Z a-z 0-9 etc)? You mentioned you've tried using other temp directory locations but could you try setting it to just Has GB Studio ever worked for you or is this your first time trying it? |
|
Hi Chris, thanks for the quick response. Yes that seems to describe whats happening. My username is just alphabetical characters so that shouldn't be an issue. I tried C:J\Tmp, it returned the same error messages. Out of curiosity, I tried exporting project source and exporting project data and those seemed to finish without error. This is my first time trying GB Studio. |
|
Thanks @Rchanjobe , I'll assume the |
|
Haha yes the J is a typo. I'd be happy to test it for you, just let me know what I can do once you are back next week. |
|
Hi @Rchanjobe I've created a debug build with a few changes
None of these changes should help fix the issue but the extra information might help narrow down what's happening on your system. You can download this build here: If you could share what output is given when trying to build at least for the first few files until it fails that would be really useful. For comparison this is what I get on Windows with this build |
|
Thank you for the debug build. After opening the sample gameboy color project and hitting run the debugger returned the following: Preparing variables... Warnings:
Please let me know if there is anything else I can do and report back with to be of assistance! Thanks |
|
Hi @Rchanjobe Thanks providing this information, could you confirm if the file It should contain the same data as this https://github.com/chrismaltby/gb-studio/blob/develop/appData/src/gb/src/core/absolute.c My current theory is either something is wrong with copying the default engine source files into the build directory or that the permissions on the engine files are getting permissions that are prevent the compiler from being able to read them correctly. I've made a new build with additional logging at: If you can provide the response for this wrapped with three backticks ( ```) on the line above and below like this: ``` it just prevents github from treating the logs as markdown and modifying some of the lines. Thanks |
|
Hello @chrismaltby, that data is present in Here is the output from the new build: |
|
So strange, I can set my settings to be the same as yours and it works perfectly... I'm running Windows Server 2016, not Windows 10 but that shouldn't really make a difference in this case. One thing you could try if you're comfortable with the Windows command line is opening and from there trying to run the commands that were failing from that log In theory it should fail with the exact same error, but if it works then that would be very confusing. You could also try running: which is being called by LCC (basically You can even get some more debug information by passing "--verbose" argument to the command: If it's possible to try that last one and paste the result you get, MAYBE that will help. If not I'm really running out of ideas sorry. You don't happen to have any other Windows devices to try for comparison do you? |
|
Hi @chrismaltby, I tried going to the C:\tmp_gbsbuild directory and running that first command you listed, it produced the same error. I also ran the last command you shared, here is the verbose output: If there isn't a solution that comes to mind that's okay, from the lack of anyone reporting this bug or talking about it on the discord this problem is almost exclusive to my device. The only other thing I could think of is if the issue comes from cc1.exe on my device, but I'm not sure how I would go about update/reinstalling that. |
|
This thread is a lot to scroll through, so not sure I'm following it all. One thing to check:
Is your cc1 file named
In case it's useful here is some discussion about path issues around cc1 (which can manifest as this error: https://sourceforge.net/p/sdcc/bugs/3571/#1954 The way that was used to determine the effective path behavior was to run the Sysinternals Process Monitor tool and capture all the file activity from sdcpp.exe. Below is a screenshot showing it searching for cc1. So that's an option for getting more info. Edit: I guess if the relative path doesn't working for some reason, it's possible that one of the absolute paths shown in the screenshot ( |
|
Hello @bbbbbr, I checked in the I tried copying cc1 to |
|
If you run cc1 in a command prompt from the Yes, you could try copying it with the extension so it's |
|
@bbbbbr I opened the directory in command prompt and it didn't recognize cc1 as a program: `C:\tmp_gbstools\gbdk\libexec\sdcc>dir Directory of C:\tmp_gbstools\gbdk\libexec\sdcc 08/21/2024 10:41 PM .08/21/2024 10:41 PM .. 08/21/2024 10:41 PM 1,112,064 cc1 1 File(s) 1,112,064 bytes 2 Dir(s) 172,381,523,968 bytes free C:\tmp_gbstools\gbdk\libexec\sdcc>cc1 --help I'm not sure if this indicates an issue with the program file itself, or if there are issues with permissions. |
|
I wonder if you download the SDCC compiler release from their homepage if their build of cc1 works. sdcc.sourceforge.net -> Left menu -> Home -> Download -> Win64 -> 4.4.0 release -> https://sourceforge.net/projects/sdcc/files/sdcc-win64/4.4.0/ They make the compiler used by GBDK and GBStudio. |
|
Hi @bbbbbr , I made a copy of cc1 in the _gbstools\gbdk\sdcc\ directory and renamed it cc1.exe. Running cc1.exe --help does return a long output of options, attached as a .txt to this message given its length. This doesn't resolve issues running GB Studios but shows that the file's contents can be properly run from the cc1 bundled in the GB Studio download. I also downloaded the 4.4.0 release of sdcc and had the same results: cc1 couldn't be ran but a copy renamed cc1.exe did. I think cc1 might be clear of suspicion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After opening any project including the sample projects, pressing run returns cc1 fatal errors in debugger when compiling .c files due to no such file or directory. The temp folder defaults to C:\Users[username]\AppData\Local\Temp and when going to directory in file explorer and looking in _gbsbuild/src/core/ the .c files are all present and file modified shows the time run was pressed. Changing the temp folder location to document, desktop, and program files doesn't change the results except for where the _gbsbuild folder gets generated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Finished compiling, or at least an error not involving no such file or directory
Screenshots
Platform (please complete the following information):
Additional context
I've tried running as admin, restarting computer, uninstalling and reinstalling, downloading older versions of GB Studio, changing temp file location, and giving permissions to program.
The text was updated successfully, but these errors were encountered: