it doesn't say that taslock.5 defines free incompatibly: there's a disagreement about lock. free and taslock are being linked together, and both call lock, but they have incompatible definitions for lock, most likely because Lock is different in each scope. taslock.5 defines lock; free calls it.
On 12 December 2012 21:47, erik quanstrom <[email protected]> wrote: > plock: incompatible type signatures 574ec04f(taslock.5) and > 9dcf33f5(/arm/lib/libc.a(free)) for lock > minooka²; nm -aT taslock.5|grep free > minooka²; > > taslock doesn't define the symbol, so why do i get this error?
