Timeline for answer to compiling gpsim on macOS causes "error: 'long long type-name' is invalid" by Jesper Juhl
Current License: CC BY-SA 4.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2020 at 15:59 | comment | added | Foad S. Farimani | @Scheff yeah, I committed but the line is still there commented out. I was waiting for your feedback to see why Qt doesn't work as it is expected. | |
| Apr 25, 2020 at 15:47 | comment | added | Scheff's Cat | @Foad Too funny that I noticed two last commits in the linked github repo with something like "long long fixed" which appeared just 13 minutes (!) before you sent your question... ;-) | |
| Apr 25, 2020 at 14:53 | comment | added | Foad S. Farimani |
On gpsim source code, it is also unsigned long long. Wonder why the software I have forked has changed it. 🤔
|
|
| Apr 25, 2020 at 14:43 | comment | added | Foad S. Farimani | it worked, but I will be waiting for @JesperJuhl to see why Qt doesn't work properly here. | |
| Apr 25, 2020 at 14:37 | history | edited | Jesper Juhl | CC BY-SA 4.0 |
added 33 characters in body
|
| Apr 25, 2020 at 14:35 | comment | added | Jesper Juhl | @Foad As far as I know, yes. | |
| Apr 25, 2020 at 14:34 | comment | added | Scheff's Cat |
OP mentioned Qt. Qt does in fact provide uint. Hence, I'm a bit puzzled why uint long long shouldn't work. Of course, I didn't dig deeper. A missing Qt header might explain...
|
|
| Apr 25, 2020 at 14:34 | comment | added | Foad S. Farimani | so this is a bug, with any other compiler as well? and has nothing to do with macOS or clang for that matter? | |
| Apr 25, 2020 at 14:30 | history | answered | Jesper Juhl | CC BY-SA 4.0 |