GNU C++ error
-
Just to be sure, you run a 32bit distribution to build your application in 32bit and that fails ?
@SGaist Yes, that's correct.
Previously I was running 64-bit Raspberry pi OS to build a 64-bit executable and that built just fine.
Update: The 64-bit OS is really Debian whereas the 32-bit Rpi OS is their own creation. -
Since it's your code, where exactly does it fail ?
-
@SGaist It fails in the MOC code, which is not my code.
But it gives very little by way of clues, just the one line:usr/include/c++/8/bits/functexcept.:42: Parse error at "std"That is in a .h file and here is the line:
namespace std _GLIBCXX_VISIBILITY(default)Update: If you look closely, it is actually /usr/lib/qt5/bin/moc that produces the error.
-
That part is clear, but moc is running on one of your class so it would be good to know what you are using for it.
-
That part is clear, but moc is running on one of your class so it would be good to know what you are using for it.
@SGaist I'm doing threading (main GUI thread and worker thread) and signals and slots.
Update: I think see the issue. Even though I ran qmake, the Makefile still has references to aarch64.
I type:
rm Makefile qmake grep aarch64 Makefile... and it still makes reference to aarch64.
-
@Publicnamer said in GNU C++ error:
usr/include/c++/8/bits/functexcept.:42: Parse error at "std"
-
@Publicnamer said in GNU C++ error:
usr/include/c++/8/bits/functexcept.:42: Parse error at "std"
@JoeCFD So glad they fixed it back in 2013. Too bad I'm still encountering it in 2021 ;)
-
You should completely nuke the build folder to ensure you do a clean build.
-
@SGaist
I seem to have fixed it. I deleted the file .qmake.stash, which I hadn't noticed before, and now I'm able to build. Thanks. -
That's why nuking the build folder and not just deleting its content is usually a good idea :-)
Glad you have it working and thanks for the feedback.
Please mark the thread as solved using the "Topic Tools" button or the three doted menu beside the answer you deem correct so that other forum members may know a solution has been found :-)
