> Without much longer belabouring the point, in my case gcc did not check > my .h file; instead of checking it
for syntax (a semicolon missing in a function definition) it accepted it and reported what the effect was of trusting it - totally incomprehensible errors. However, I have learned from this that before I compile the .c files I will compile the .h's separately first - that would have prevented the issue. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b27b924a-9ca3-44cf-bceb-a355d002da2f%40googlegroups.com.
