[1.1.x] #error "You are using an old Configuration.h file, update it before building Marlin."

[bruce356]

Hi Just downloaded bugfix 1.1.x tried to compile with Arduino v1.8.6 using both the default files as down loaded and with my previous configs transfered and get the following errors on compiling.

SanityCheck.h:47: error: #error "You are using an old Configuration.h file, update it before building Marlin."
SanityCheck.h:51: error: #error "You are using an old Configuration_adv.h file, update it before building Marlin."

Its probably something very simple to fix.
regards - bruce

[iosonopersia]

#error "You are using an old Configuration.h file, update it before building Marlin."

Have you even read the error itself? I think it's enough self-explanatory...

[...] and with my previous configs transfered [...]

This is the cause of your problem. Just get the new Configuration.h and manually change the options according to the old values you used before

[bruce356]

Hi iosonopersia, thanks for the quick response, I know I am not a programmer I just downloaded the latest zip file left the default settings compliled (or tried) and received the above error. Please tell me why I am stupid.

[iosonopersia]

I never said you're stupid... Anyway, compiling with the default Configuration.h and Configuration_adv.h should not raise those errors. I quickly checked the code and everything is ok. Make sure that you downloaded the actual bugfix 1.1.x and that you didn't touch any of the files. Than, it may be a problem of Arduino IDE, I really don't know

[bruce356]

I know you did not but I thought that I missed something simple that was my fault.
I just downloaded again touched nothing, just compiled with Arduino set to Mega 2560 and same errors as above.

Just to make sure I unzipped the file to my laptop that has Arduino v1.8.5 installed and it compiled normally NO Errors? What the f I don't get it. Thanks again for spending the time and helping.
Regards - bruce

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.