From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem with building from source on vx32 solved
Date: Wed, 1 Sep 2010 23:35:44 -0700 [thread overview]
Message-ID: <AANLkTimtKtehEX9-futHHnm571-GSi1jJKOPccOShg-W@mail.gmail.com> (raw)
In-Reply-To: <5f67ead6f48c116a69a892a57931d4d2@brasstown.quanstro.net>
OK, the problem with _tos on 9vx is making some sense.
gcc and 8c disagree on the size of the Tos struct. It's declared the
same way in 9vx as in
Plan 9, but 8c thinks it is 56 bytes and gcc thinks it is 88.
The reason is that 9vx is compiled on a 64-bit machine in this case,
so we are running 32-bit binaries on a 64-bit kernel, i.e. it is
heterogeneous. Amusing :-)
Guess I'll try 9vx as a 32-bit binary and see what shakes.
ron
next prev parent reply other threads:[~2010-09-02 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 6:00 ron minnich
2010-08-31 12:54 ` erik quanstrom
2010-08-31 14:59 ` ron minnich
2010-08-31 15:25 ` erik quanstrom
2010-09-02 6:35 ` ron minnich [this message]
2010-09-02 11:57 ` erik quanstrom
2010-09-02 15:05 ` ron minnich
2010-09-03 5:59 ` ron minnich
2010-09-03 8:21 ` Charles Forsyth
2010-09-03 14:56 ` ron minnich
2010-09-03 14:57 ` Philippe Anel
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=AANLkTimtKtehEX9-futHHnm571-GSi1jJKOPccOShg-W@mail.gmail.com \
--to=rminnich@gmail.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).