[Olsr-dev] openwrt issues

Ferry Huberts (spam-protected)
Sun Jun 3 22:39:49 CEST 2012


On 03-06-12 21:12, Jo-Philipp Wich wrote:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 >
 > Hi.
 >
 >> How do we want to handle the openwrt compilation issues?
 >> It seems to me that the openwrt toolchain and libraries are quite
 >> outdated and I really need your input on how to proceed.
 >
 > Not having nanosecond resolution in stat.h does not mean that it is
 > outdated, just that it is not implemented. Any code using non-standard
 > struct stat fields should protect the usage with appropriate defines.
 >

that why I said 'seems' ;-)

I will look into adding the defines that are needed

 > As for the nmea lib, there it should enough to advise the compiler to
 > use the appropriate standards level.
 >
 > ~ Jow
 > -----BEGIN PGP SIGNATURE-----
 > Version: GnuPG v1.4.10 (GNU/Linux)
 > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 >
 > iEYEARECAAYFAk/LtykACgkQdputYINPTPOvzQCdGdB4085O57IpHMrr4o6vlOZh
 > zvsAoIvTLrXsMd0oy+eZPBoYhw8BA99k
 > =99nx
 > -----END PGP SIGNATURE-----
 >


On 03-06-12 21:13, Jo-Philipp Wich wrote:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 >
 > [again to the list, sorry Saverio]
 >
 > Hi,
 >
 > isnan() on uClibc is protected by __USE_ISOC99 or __USE_BSD so appending
 > either -D_GNU_SOURCE or -std=c99 / -std=gnu99 to TARGET_CFLAGS in
 > OpenWrt should work.
 >

would be aewsome if this could be added to the openwrt build, thanks for 
the advise!

 > ~ Jow
 > -----BEGIN PGP SIGNATURE-----
 > Version: GnuPG v1.4.10 (GNU/Linux)
 > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 >
 > iEYEARECAAYFAk/Lt2MACgkQdputYINPTPPOhgCffM2yAoG8JbYiSHrbNfxUNxh7
 > F14Anj6S9KVEeOUDCpA2fOMIO016xkNY
 > =ik5e
 > -----END PGP SIGNATURE-----
 >



On 03-06-12 21:50, Markus Kittenberger wrote:
>
>
> On Sun, Jun 3, 2012 at 9:03 PM, Ferry Huberts <(spam-protected)
> <mailto:(spam-protected)>> wrote:
>
>     Ok guys,
>
>     How do we want to handle the openwrt compilation issues?
>     It seems to me that the openwrt toolchain and libraries are quite
>     outdated and I really need your input on how to proceed.
>
>
> but they (openwrt libraries and especially of legacy targets) will
> mostly not change,.
>
> hmm, olsrd worked fine on openwrt (including old versions of it) till
> now,..
> and i would vote for keeping it like this,.
>

me too, that's why I asked for advise, since I'm not really familiar 
with that target

> especially for the olsrd-core and plugins like txtinfo
>
> and imho other/new plugins that do not want to be compiled for ancient
> devices/target should get at least some #ifdefs
>
> Markus

-- 
Ferry Huberts




More information about the Olsr-dev mailing list