9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] plan 9ports on suse 9.1
Date: Tue, 14 Dec 2004 14:29:34 -0700	[thread overview]
Message-ID: <Pine.LNX.4.58.0412141422110.23019@linux.site> (raw)

Sorry if this was asked before. 

I am getting this:
l -o o.9p 9p.o /usr/local/plan9/lib/libsec.a /usr/local/plan9/lib/libfs.a 
/usr/local/plan9/lib/libmux.a /usr/local/plan9/lib/libregexp9.a 
/usr/local/plan9/lib/libthread.a /usr/local/plan9/lib/libbio.a 
/usr/local/plan9/lib/lib9.a
/usr/local/plan9/lib/libthread.a(fdwait.o)(.text+0x212): In function 
`threadlisten':
/usr/local/plan9/src/libthread/fdwait.c:365: undefined reference to 
`getcallerpc'
/usr/local/plan9/lib/libthread.a(fdwait.o)(.text+0x299): In function 
`_threadwrite':
/usr/local/plan9/src/libthread/fdwait.c:323: undefined reference to 
`getcallerpc'
/usr/local/plan9/lib/libthread.a(fdwait.o)(.text+0x34f): In function 
`threadsendfd':
/usr/local/plan9/src/libthread/fdwait.c:288: undefined reference to 
`getcallerpc'
/usr/local/plan9/lib/libthread.a(fdwait.o)(.text+0x3bb): In function 
`threadrecvfd':
/usr/local/plan9/src/libthread/fdwait.c:269: undefined reference to 
`getcallerpc'
/usr/local/plan9/lib/libthread.a(fdwait.o)(.text+0x424): In function 
`threadread':
/usr/local/plan9/src/libthread/fdwait.c:250: undefined reference to 
`getcallerpc'
/usr/local/plan9/lib/libthread.a(fdwait.o)(.text+0x4cb):/usr/local/plan9/src/libthread/fdwait.c:208: 
more undefined references to `getcallerpc' follow

but am not sure why. mk clean doesn't seem to clean. What does it make 
sense to look for?

I have a suse 9.0 laptop that works fine with this, which is weird. 
thanks

ron


             reply	other threads:[~2004-12-14 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 21:29 Ronald G. Minnich [this message]
2004-12-14 21:35 ` andrey mirtchovski
2005-01-17 23:04   ` Adrian Tritschler

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=Pine.LNX.4.58.0412141422110.23019@linux.site \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    /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).