From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 5l
Date: Wed, 12 Dec 2012 22:27:43 +0000 [thread overview]
Message-ID: <CAOw7k5jcm=LXJCWBRVw6WsgoOQiUYHbm30PoYMw0kQPemePj_w@mail.gmail.com> (raw)
In-Reply-To: <cecf9e6689b267eb4f8910a5fb05b209@ladd.quanstro.net>
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 <quanstro@quanstro.net> 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?
next prev parent reply other threads:[~2012-12-12 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 21:47 erik quanstrom
2012-12-12 22:27 ` Charles Forsyth [this message]
2012-12-12 22:53 ` Richard Miller
2012-12-12 22:56 ` Charles Forsyth
2012-12-12 22:59 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOw7k5jcm=LXJCWBRVw6WsgoOQiUYHbm30PoYMw0kQPemePj_w@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).