View Single Post
Old 08-03-2016, 07:00 AM   #12
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Use -I flag to add the include path in the build command(s) to wherever you put them.
You didn't see that error during the native compile because your native install has them in the native compiler's default search path.

It also reads as if you need to do something about that default output test in configure.
It isn't compatible with your gcc version.
So:
Search if it has been fixed by someone (probably just using a recent auto-reconfigure to regenerate the configure file will do);
Fix it yourself ;
Skip it by forcing the correct answer ;
Use an older compiler (for instance, the version used to build the Kindle firmware);

I would suggest diving into Buildroot see how they fixed auto-configure for the newer compiler versions.

It will be a rather old fix (2013?), because:
Code:
$ gcc -V </dev/null
gcc: error: unrecognized option ‘-V’
That is gcc-4.6 and the current gcc is 6.something.

Last edited by knc1; 08-03-2016 at 07:54 AM.
knc1 is offline   Reply With Quote