On 5/9/26 20:29, Scott Hall via TriEmbed wrote:
(a lot of "does not name a type" and related compiler errors)
This reads to me like an include path issue. Is it possible you have an
older source library installed on your system that the compiler is
finding first?
Something I sometimes do when facing these errors is perform a recursive
grep for the symbol in question through the common system include paths:
/usr/include
/usr/local/include
This should pretty quickly expose any files that declare the symbol.
I think there's also a way to make gcc output the full paths of all
#include directives it resolves, but I don't have the syntax for that
quick at hand.
Good luck!
-B
_______________________________________________
Triangle, NC Embedded Interest Group mailing list
To post message: [email protected]
List info: http://mail.triembed.org/mailman/listinfo/triembed_triembed.org
TriEmbed web site: https://TriEmbed.org
To unsubscribe, click link and send a blank message:
mailto:[email protected]?subject=unsubscribe
Searchable email archive available at
https://www.mail-archive.com/[email protected]/
