9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] 5l
@ 2012-12-12 21:47 erik quanstrom
  2012-12-12 22:27 ` Charles Forsyth
  0 siblings, 1 reply; 5+ messages in thread
From: erik quanstrom @ 2012-12-12 21:47 UTC (permalink / raw)
  To: 9fans

i don't understand these error messages from 5l.  (8l doesn't seem
to do quite the same thing)

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?

- erik



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] 5l
  2012-12-12 21:47 [9fans] 5l erik quanstrom
@ 2012-12-12 22:27 ` Charles Forsyth
  2012-12-12 22:53   ` Richard Miller
  0 siblings, 1 reply; 5+ messages in thread
From: Charles Forsyth @ 2012-12-12 22:27 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

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?



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] 5l
  2012-12-12 22:27 ` Charles Forsyth
@ 2012-12-12 22:53   ` Richard Miller
  2012-12-12 22:56     ` Charles Forsyth
  2012-12-12 22:59     ` erik quanstrom
  0 siblings, 2 replies; 5+ messages in thread
From: Richard Miller @ 2012-12-12 22:53 UTC (permalink / raw)
  To: 9fans

>  most likely because Lock
> is different in each scope.

/sys/src/*/dat.h defines Lock, /sys/include/libc.h defines it differently.
You may be trying to link a kernel with some function like lock() coming
from libc instead of its own version.




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] 5l
  2012-12-12 22:53   ` Richard Miller
@ 2012-12-12 22:56     ` Charles Forsyth
  2012-12-12 22:59     ` erik quanstrom
  1 sibling, 0 replies; 5+ messages in thread
From: Charles Forsyth @ 2012-12-12 22:56 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

the diagnostic says that free is being taken from libc, so it will
have libc's version.
normally free is defined in port.

On 12 December 2012 22:53, Richard Miller <9fans@hamnavoe.com> wrote:
> You may be trying to link a kernel with some function like lock() coming
> from libc instead of its own version.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] 5l
  2012-12-12 22:53   ` Richard Miller
  2012-12-12 22:56     ` Charles Forsyth
@ 2012-12-12 22:59     ` erik quanstrom
  1 sibling, 0 replies; 5+ messages in thread
From: erik quanstrom @ 2012-12-12 22:59 UTC (permalink / raw)
  To: 9fans

On Wed Dec 12 17:54:09 EST 2012, 9fans@hamnavoe.com wrote:
> >  most likely because Lock
> > is different in each scope.
>
> /sys/src/*/dat.h defines Lock, /sys/include/libc.h defines it differently.
> You may be trying to link a kernel with some function like lock() coming
> from libc instead of its own version.

yes, yes, all correct.  i misread the diagnostic.  sorry for the noise.

- erik



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2012-12-12 22:59 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-12 21:47 [9fans] 5l erik quanstrom
2012-12-12 22:27 ` Charles Forsyth
2012-12-12 22:53   ` Richard Miller
2012-12-12 22:56     ` Charles Forsyth
2012-12-12 22:59     ` erik quanstrom

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).