9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Xen and new venti
Date: Sat,  8 Mar 2008 20:11:28 +0000	[thread overview]
Message-ID: <19aa40d0d968992bace1770aaf2c775e@hamnavoe.com> (raw)

OK, I've found the real cause of the errors which stella@plan9.jp
was seeing when linking 9xen kernels:

> v4parsecidr: undefined: memcpy in v4parsecidr
> _strayintrx: _ctype: not defined

In the definition of LIB= in the mkfile, if libc.a is listed before
libip.a, you get the above errors (for any kernel, not just xen ones).
This is because there are no direct references to libc.a functions
from the kernel itself, only from something in libip.a which was
added recently.  So the linker needs to see libip.a before libc.a
in order to know what references to resolve.

If you simply move libc.a after libip.a, it works fine without having
to change any source code.

I've now rebuilt all the 9xen*.gz kernels in /n/sources/xen/xen3
using the current Plan 9 kernel and nventi.  They work with Xen
3.0.x; no guarantees about 3.2.x but it's worth trying.

-- Richard



             reply	other threads:[~2008-03-08 20:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-08 20:11 Richard Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-05  0:18 stella
2008-03-05  0:37 ` erik quanstrom
2008-03-05  8:10   ` stella
2008-03-03 23:15 stella
2008-03-04  0:52 ` erik quanstrom
2008-03-04 21:38   ` stella
2008-03-04 22:18     ` Richard Miller
2008-03-04 22:26       ` 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=19aa40d0d968992bace1770aaf2c775e@hamnavoe.com \
    --to=9fans@hamnavoe.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).