From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Plan 9 Port error in mpvecadd-Darwin.s on Leopard
Date: Wed, 31 Oct 2007 09:42:32 -0700 [thread overview]
Message-ID: <3e1162e60710310942r2055b518ga0cd07b4e4c30d82@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180710310924p1022cc47w8f4fec460b05061@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
On 10/31/07, andrey mirtchovski <mirtchovski@gmail.com> wrote:
>
> I haven't gotten to the point where David is, but i'm trying (leopard
> isn't "approved for use" in our organization yet, they expect it to be
> in a few months, but i can still use it at home :).
>
> something to add to the knowledge base (although pretty obvious, it
> stunned me this morning): if you are upgrading a Tiger machine that
> had xcode installed on it you must upgrade the xcode tools too, or you
> won't be able to link any binary from p9p.
>
> xcode is available on developer.apple.com or on the upgrade dvd that
> has leopard.
I'm not sure I'd trust Apple's upgrading at all :-).
I just backup to another disk, then clean/install.
Then I may have some programs to fetch, and my preferences might be a little
out of whack, but I find less "surprises".
Dave
[-- Attachment #2: Type: text/html, Size: 1479 bytes --]
next prev parent reply other threads:[~2007-10-31 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3e1162e60710301650r35bd83ectbc2d8fbf8e708ba1@mail.gmail.com>
2007-10-30 23:59 ` Bakul Shah
2007-10-31 15:10 ` David Leimbach
2007-10-31 16:24 ` andrey mirtchovski
2007-10-31 16:42 ` David Leimbach [this message]
2007-10-31 19:05 ` andrey mirtchovski
2007-10-31 20:18 ` Russ Cox
2007-10-31 20:33 ` David Leimbach
2007-10-31 20:56 ` Michaelian Ennis
2007-11-03 6:02 ` Michaelian Ennis
2007-10-31 20:32 ` David Leimbach
2007-11-03 7:35 ` underspecified
2007-11-03 9:22 ` underspecified
2007-10-31 20:53 ` Michaelian Ennis
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=3e1162e60710310942r2055b518ga0cd07b4e4c30d82@mail.gmail.com \
--to=leimy2k@gmail.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).