<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Hi sylvain and thanks for your replies.<br>As you pointed out the resolution to the problem was to build new toolchain according to instructions in wiki,<br>which does build( in backtrack r2 )both master and testing branch without complaining about inttypes.h <br>regards erich<br><br><div><span><br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">Fra:</span></b> Sylvain Munaut <246tnt@gmail.com><br> <b><span style="font-weight: bold;">Til:</span></b> Erich Dachleger <edachleger@yahoo.com> <br><b><span style="font-weight: bold;">Kopi:</span></b>
"baseband-devel@lists.osmocom.org" <baseband-devel@lists.osmocom.org> <br> <b><span style="font-weight: bold;">Sendt:</span></b> Lørdag, 19. januar 2013 14.18<br> <b><span style="font-weight: bold;">Emne:</span></b> Re: sylvain/testing: apps/trx/trx.c: inttypes.h:No such file or directory<br> </font> </div> <br>>> I tested and removed inttypes.h in trx/trx.c. Recompiling gives an error<br>>> message about parse error before debug-message PRIu32 on line 69 in<br>>> trx/trx.c.<br>><br>> PRIu32 is AFAIK the proper way of printing a uint32_t without<br>> generating a warning and without making assumptions about the<br>> platform.<br>><br>> inttypes.h is a standard C99 header file, if you distribution doesn't<br>> have it, I would suggest reporting the bug to them.<br><br>As was pointed out to me, it's the trx.c file from the firmware and<br>not the one from the host app, so the bug should go to the
cross<br>toolchain provider I guess.<br><br>That printf is definitely not a "key-functionality" so you can just<br>remote it, however, I would expect that while fixing other GCC<br>warnings, the use of inttypes.h will rise in the future, so I'd<br>suggest you get a good toolchain. See<br><a href="http://bb.osmocom.org/trac/wiki/GnuArmToolchain" target="_blank">http://bb.osmocom.org/trac/wiki/GnuArmToolchain</a> for how to build one.<br><br><br>Cheers,<br><br> Sylvain<br><br><br><br> </div> </div> </div></body></html>