[Olsr-dev] src/gatewaySpeedFile.c:124: error: ‘struct stat’ has no member named ‘st_mtim’

Ferry Huberts (spam-protected)
Thu May 10 16:13:38 CEST 2012



On 10-05-12 15:40, Ferry Huberts wrote:
>
>
> On 10-05-12 15:31, Henning Rogge wrote:
>> On 05/10/2012 03:22 PM, Hans-Christoph Steiner wrote:
>>>
>>> Hey Ferry,
>>>
>>> Your recent gateway commits seem to only work on GNU/Linux, olsrd now
>>> fails to build on Mac OS X, Android, and Windows:
>>>
>>> Mac OS X:
>>> [CC] src/gatewaySpeedFile.c
>>> src/gatewaySpeedFile.c: In function ‘readGatewaySpeedFile’:
>>> src/gatewaySpeedFile.c:124: error: ‘struct stat’ has no member named
>>> ‘st_mtim’
>>> src/gatewaySpeedFile.c:134: error: ‘struct stat’ has no member named
>>> ‘st_mtim’
>>> src/gatewaySpeedFile.c:134: error: ‘struct stat’ has no member named
>>> ‘st_mtim’
>>> make: *** [src/gatewaySpeedFile.o] Error 1
>>>
>>> https://build.safermobile.org/job/olsrd-stable-android/10/console
>>>
>>> https://build.safermobile.org/job/olsrd-stable-windows/7/console
>>
>> Did I somehow missed the discussion about this new core feature? Or did
>> it just happen some time ago?
>>
>> Henning
>>
>
> Ok guys,
>
> Sorry 'bout that. I thought I checked that smart gateway was linux only
> but it appears that I missed something.
> I'll revert the commits.
>
>
> Also, no there was no discussion on this, sorry :-(
>
> Why to we want this?
> We have nodes with multiple uplinks: WLAN, UMTS, Satcom.
> We have a VPN link configured to our backbone on every node.
> We detect which uplink is active and get the bandwidth settings for that
> link.
> We now want olsrd to use the active bandwidth for the smart gateway
> announcement so that the best gateway is chosen in a cluster of nodes.
>
> The next step I want to do is to force a smart gateway election when a
> gateway announces 0 bandwidth and the receiving node uses that smart
> gateway.
>
>

 From now on I'll be submitting my patches to the mailing list before 
committing, just to be safe and to be able to discuss them.
Obviously I'll then be expecting feedback/review comments :-)


-- 
Ferry Huberts




More information about the Olsr-dev mailing list