View Single Post
Old 10-04-2015, 08:42 AM   #123
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
Quote:
Originally Posted by NiLuJe View Post
- - -
(The bad news is I have no idea why the hell the legacy framework craps out with a freetype lib built w/ GCC 5, so I had to roll-back to GCC 4.9 for the FT stack on legacy devices...).
The BR auto-builder has been stumbling over a lot of packages when using GCC-5 ...
The work-around so far has been:
Quote:
Add -std=gnu89 to CFLAGS to keep pre gcc5 inline function symbols visibility rules.
It is one of the reasons I didn't use __attribute__(inline) on the new translation code.
But mostly because I don't know how many gcc-isms your clang compiler will take.

None of the auto-builders have a GCC-6 toolchain installed (yet).
That may be another can of worms, later.

Last edited by knc1; 10-04-2015 at 08:48 AM.
knc1 is offline   Reply With Quote