[Olsr-dev] os x issue help

[L. Aaron Kaplan]

ah, yes... ok..

in OS X just for the time being in tip please just set
LDFLAGS_EXE += ""
instead of
LDFLAGS_EXE +=  -Wl,-export-dynamic

then it will compile.



On Jan 9, 2009, at 9:18 PM, Mark K. wrote:

> I thought export-dynamic might have been the problem, so I modified  
> the makefile and forced it to use the dynamic list you setup.   
> Unfortunately, I still couldn't compile.
>
> here's the error:
>
> ld: unknown option: --dynamic-list=olsrd.exports
> collect2: ld returned 1 exit status
> make: *** [olsrd] Error 1
>
> I'm still trying to figure out why this compile process is failing,  
> I'll keep looking.  I'm using the built-in gcc 4.0.1 on os x 10.5.6.
>
>
> On Jan 9, 2009, at 12:36 PM, L. Aaron Kaplan wrote:
>
>>
>> Mark,
>>
>> First question: we recently fixed a severe bug in OS X where no  
>> packets where sent out.
>> Was your version before or after this fix? (if unsure - try again  
>> with http://gredler.at/hg/olsrd/archive/tip.tar.gz)
>>
>> Second: can you tell me how you configured the tapX devices? Is  
>> that part of an openVPN setup?
>> How are these tap devices connected to each other? Are they?
>>
>> a.
>>
>>
>> On Jan 9, 2009, at 7:30 PM, Mark K. wrote:
>>
>>> i have two olsr nodes communicating through tap0 and tap1 virtual
>>> devices.  But, I have two problems.  First, the nodes do not add  
>>> each
>>> other to their tables -- why is that?  And, I am getting this  
>>> strange
>>> error about socket associations (see below).
>>>
>>> 20 bytes from 192.168.2.21, socket associated tap0 really received  
>>> on
>>> tap0
>>> 20 bytes from 192.168.2.21, socket associated tap0 really received  
>>> on
>>> tap0
>>> 20 bytes from 192.168.2.21, socket associated tap0 really received  
>>> on
>>> tap0
>>> 20 bytes from 192.168.3.22, socket associated tap0 really received  
>>> on
>>> tap1
>>> 20 bytes from 192.168.3.22, socket associated tap0 really received  
>>> on
>>> tap1
>>>
>>>
>>> Does anyone have any idea on how to fix this?  The messages are at
>>> least being received but the table update does not seem to occur.
>>>
>>> Per previous discussions, I am starting olsrd with the -f option and
>>> directing each olsrd agent to a separate olsrd.conf file.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> -- 
>>> Olsr-dev mailing list
>>> (spam-protected)
>>> http://lists.olsr.org/mailman/listinfo/olsr-dev
>>
>