Minor but annoying qcc bug

74 views
Skip to first unread message

Conor Olive

unread,
Jun 3, 2026, 8:00:58 AMJun 3
to basilisk-fr
Hi all, 

Not sure if bugs in qcc should still be reported on sandbox/bugs since this one is primarily triggered through specific types of include paths (i.e. environment dependent rather than code dependent). Specifically the way that I triggered this was by compiling qcc inside of ~/mydomain.com, where the default include path (-DBASILISK=...) is baked into the binary, then trying to use qcc to compile any of the examples (e.g. karman.c). Seemingly this can also be reproduced by any of the parent folders in -DBASILISK=... containing *.c* or *.h* in the folder name. 

The offending LoC found is 481 in src/include.lex (is_code) which searches for .c/.h anywhere in the path string rather than just at the end. The obvious fix here is to simply look only at the end (or otherwise be very careful about the parent folders' naming).

The attached patch fixes this edge case. I would be happy to write a bug report in the sandbox if this is helpful.

Best regards,
Conor


qcc-path-extension-fix.patch

Stephane Popinet

unread,
Jun 4, 2026, 9:42:58 AMJun 4
to basil...@googlegroups.com
Hi Conor,

Thanks for the bug report and patch. I have just pushed a patch (which I
had made earlier than your report) which should fix the problem.

cheers,

Stephane

https://basilisk.fr/src/?changes=20260527160025


Reply all
Reply to author
Forward
0 new messages