View Single Post
Old 09-01-2012, 07:00 PM   #10
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Quote:
Originally Posted by NiLuJe View Post
@twobob: Usually, a quick round of checking the system's headers + google will get you the answer.

If it's a project using autotool, there's generally a configure-time check responsible for checking the system's libc that may be overridden manually. But you may also need/want to hack around the sources/headers of the project directly (see what I did for coreutils for exeample) to dumb it down.

grep -r & readelf are your friends .

The scanf case might be one of the trickier, if I remember correctly, you'll have to either build with gcc set to a particular -std that doesn't handle C99, or build with _GNU_SOURCE defined. That might not be viable workarounds for every projects out there...

This is great info. I am honestly just beginning to understand even a tiny part of the construct but every little helps me provide better output.

Much appreciated. These little tricks and touches make all the difference for a finicky target like the kindles.
twobob is offline   Reply With Quote