cc1plus.exe fatal error

Hello.
I have this error compiling one proyect in windows 10.:

My platformio.ini has this flag that complile ok under linux :
build_flags =
${common.build_flags}
-D USER_SETUP_LOADED=1
-include /$PROJECT_LIBDEPS_DIR/$PIOENV/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h

If I changue this line:
-include /$PROJECT_LIBDEPS_DIR/$PIOENV/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h

by this other:
-include $PROJECT_LIBDEPS_DIR/$PIOENV/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h

The proyect compile under windows 10 + vscode +platformio.
But not compile under linux. It is neccesary to put " / " to compile it.

There is an issue with platformio that cause this fault?

I asked here for this bug: https://community.platformio.org/t/cc1plus-exe-fatal-error/34551

Thanks.
Robert.

- Sorry, the same error occurs El lun, 3 jul 2023 a las 14:58, Ivan Kravets ***@***.***>) escribió:

…

Could you try a direct declaration using interpolation? See docs and examples here https://docs.platformio.org/en/latest/projectconf/interpolation.html Try the next: [env:myenv]build_flags = -D USER_SETUP_LOADED=1 -include ${platformio.libdeps_dir}/${this.__env__}/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h — Reply to this email directly, view it on GitHub <#4682 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE7JITD4WNXQUOBE5TCDEJDXOK6WLANCNFSM6AAAAAAZ3AV74A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

This works under linux and windows:

-include .pio/libdeps/${PIOENV}/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h

only this works under linux and windows:

…

-include .pio/libdeps/${PIOENV}/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h El lun, 3 jul 2023 a las 16:25, Roberto Fernandez ***@***.***>) escribió:

- Sorry, the same error occurs El lun, 3 jul 2023 a las 14:58, Ivan Kravets ***@***.***>) escribió: > Could you try a direct declaration using interpolation? See docs and > examples here > https://docs.platformio.org/en/latest/projectconf/interpolation.html > > Try the next: > > [env:myenv]build_flags = > -D USER_SETUP_LOADED=1 > -include ${platformio.libdeps_dir}/${this.__env__}/TFT_eSPI/User_Setups/Setup25_TTGO_T_Display.h > > — > Reply to this email directly, view it on GitHub > <#4682 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AE7JITD4WNXQUOBE5TCDEJDXOK6WLANCNFSM6AAAAAAZ3AV74A> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

Sorry, I deleted my previous comment. This is actually a bug and we will fix it ASAP.

Thanks for the report. Please re-test with pio upgrade --dev.

I've tested with PlatformIO Core, version 6.1.9a1 as 6.1.8 has broken our build system entirely and I still have an include error issue. Our build flags have a relative path in them as the PlatformIO docs say

Process file as if #include "file" appeared as the first line of the primary source file.

However, the build system prepends the builder path directory as an absolute path to the include file, when it is actually in our PROJECT_DIR/include, which is already in -Iinclude

build_flags =
	${env_common_stm32.build_flags}
	${radio_2400.build_flags}
	${common_env_data.build_flags_tx}
	-flto
	-include target/FM30_TX.h

Build output

arm-none-eabi-gcc -o .pio\build\FM30_TX_via_DFU\FrameworkArduinoVariant\PeripheralPins.c.o -c -std=gnu11 -O2 -Wno-builtin-macro-redefined -Wall -flto -include C:\Users\bmayland\.platformio\platforms\ststm32\builder\target\FM30_TX.h ...

Should I open a new issue for this or keep it here?

Could you provide a simple project (zip archive attached here) to reproduce this issue?

I apologize for my error, but I have misspoken in my previous message. The builder does properly support it if I supply an absolute path for the include file via a variable, but does not leave relative paths alone. It expands the relative path into the builder directory.

I do not have a simple project to supply. I can work around this in our project by supplying the full path the -include file but that's a real problem because we'd now have to go back and cut new version of all our supported older versions so the build works again.

The builder code here does not fire because the relative path does not exist (platformio/builder/tools/piobuild.py)

 if os.path.exists(p):
                result["CCFLAGS"][i] = (f[0], os.path.abspath(p))

Please provide the 1 line from platformio.ini which works and another one that does not.

working

build_flags =
	${env_common_stm32.build_flags}
	${radio_2400.build_flags}
	${common_env_data.build_flags_tx}
	-flto
	-include ${PROJECT_DIR}/include/target/FM30_TX.h
	-DUSBCON
	-DPIO_FRAMEWORK_ARDUINO_ENABLE_CDC
	-DHSE_VALUE=16000000U
	-DVECT_TAB_OFFSET=0x1000U
	-Wl,--defsym=FLASH_APP_OFFSET=0x1000

not working (what we had before

build_flags =
	${env_common_stm32.build_flags}
	${radio_2400.build_flags}
	${common_env_data.build_flags_tx}
	-flto
	-include target/FM30_TX.h
	-DUSBCON
	-DPIO_FRAMEWORK_ARDUINO_ENABLE_CDC
	-DHSE_VALUE=16000000U
	-DVECT_TAB_OFFSET=0x1000U
	-Wl,--defsym=FLASH_APP_OFFSET=0x1000

You need

-include include/target/FM30_TX.h

The cwd is the project root dir.

Oh I see! I appreciate that.

In 6.1.8 it worked though, and for years it has worked. Not to be too snarky because I appreciate your help, but

Process file as if #include "file" appeared as the first line of the primary source file.

This file is in the include path and therefore should have no issue being included, so long as an absolute path was not added to it. Is there any way this can not be processed and have a bogus path added to it?

I think we can improve this behavior. I reopen this issue.

Or, could I ask you to create a new issue and refer to this one? It's better for history.

Can do, will tag this issue in it too.

Resolved a critical issue related to the usage of the ``-include`` fl…

Navigation Menu

Repository navigation

cc1plus.exe fatal error #4682

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

cc1plus.exe fatal error #4682

Description

Activity

roberbike commented on Jul 3, 2023

roberbike commented on Jul 3, 2023

roberbike commented on Jul 3, 2023

ivankravets commented on Jul 3, 2023

ivankravets commented on Jul 3, 2023

CapnBry commented on Jul 5, 2023

ivankravets commented on Jul 5, 2023

CapnBry commented on Jul 5, 2023

ivankravets commented on Jul 5, 2023

CapnBry commented on Jul 5, 2023

ivankravets commented on Jul 5, 2023

CapnBry commented on Jul 5, 2023

ivankravets commented on Jul 5, 2023

ivankravets commented on Jul 5, 2023

CapnBry commented on Jul 5, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions