From: Micah Stetson <micah@cnm-vra.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9ports won't compile: undefined ref to getcallerpc
Date: Tue, 19 Oct 2004 15:35:33 -0700 [thread overview]
Message-ID: <20041019223533.GA28331@epaphras> (raw)
In-Reply-To: <a4e6962a041019141468ae46ed@mail.gmail.com>
> > reference to getcallerpc. I opened fdwait.c and it includes libc.h,
> > which defines getcallerpc, so I am not sure what is causing the error.
...
> Okay, I was able to reproduce your problem on Gentoo x86 with the same compiler.
> Simply remove lib/lib9.a and run ./INSTALL again.
>
> Not sure why this fixes it (don't have time to look into it right
> now), but it does.
I actually ran into this yesterday. It's gnu as. It
doesn't return an error status when it fails to open the
assembly source. Mkmk.sh:40 interprets this to mean that
the assembly source was there, and so it doesn't try to
build getcallerpc from the C source. Getcallerpc is
actually in the C source, so it doesn't get linked into
lib9.a.
Micah
next prev parent reply other threads:[~2004-10-19 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 20:35 Derek Davis
2004-10-19 21:14 ` Eric Van Hensbergen
2004-10-19 22:35 ` Micah Stetson [this message]
2004-10-20 2:25 ` Russ Cox
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=20041019223533.GA28331@epaphras \
--to=micah@cnm-vra.com \
--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).