-
Notifications
You must be signed in to change notification settings - Fork 76
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
Makefile does not account for older toolchains #6
Comments
Additional information:
|
independently first calling make for libopencm3 solved the issue in combination with making Frodo c89/gnu89 compliant. |
technotive
changed the title
Makefile does not accoutn for older toolchains
Makefile does not account for older toolchains
Apr 26, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Edits; Markdown fix.
In the process of trying to get the standard benchmarks to work according to the readme. At this point I am at the "Running tests and benchmarks" part of the readme.
Linuxmint 17.3 (Rosa) with GCC/G++ 5.5 has the following output when calling make:
Which is supposedly remedied by:
make CFLAGS="-std=gnu99"
Which results in:
On the first run.
Then we run
make
again, and thenmake CFLAGS="-std=gnu99"
again to getAfter which a regular make results in:
At which point alternating both method does not change anything anymore.
Calling
make clean
will revert the situation to the way it was at the beginning of this message.Note that I originally updated from GCC 4.8 (Which showed similar behaviour) to GCC 5.5 because I read that gnu11 is the new default for GCC 5.5, which would make messing with the CFLAG unessecary. Sadly, GCC 5.5 did not deliver what I thought it would.
It looks like some libraries need the "-std=gnu99" flag but somehow either something else gets misconfigured because of it, or it was misconfigured from the start. Can someone help me debug this? I am not an expert when it comes to Makefiles, so it might as well be I just forgot something.
The text was updated successfully, but these errors were encountered: