From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 12 Dec 2012 22:27:43 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] 5l Topicbox-Message-UUID: f60898c4-ead7-11e9-9d60-3106f5b1d025 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 wrote: > plock: incompatible type signatures 574ec04f(taslock.5) and 9dcf33f5(/arm= /lib/libc.a(free)) for lock > minooka=C2=B2; nm -aT taslock.5|grep free > minooka=C2=B2; > > taslock doesn't define the symbol, so why do i get this error?