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