9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9ports & macos 10.4 don't like each othere.
Date: Wed,  9 Nov 2005 23:25:33 -0600	[thread overview]
Message-ID: <98C8D026-907D-4DAB-8A12-05C964625FA4@corpus-callosum.com> (raw)
In-Reply-To: <4372C2A2.1090802@lanl.gov>


On Nov 9, 2005, at 9:46 PM, Ronald G Minnich wrote:
>
> I don't know what the issue is, have not had time to look at it.

Russ posted a recent update to libthread and there are updates to bin/ 
9l and src/cmd/auxstats/mkfile that I hope make it in sometime in the  
near future (only needed for auxstats right now, and I respect Russ'  
busy schedule).

This actually leads to the question: since Apple's announced the x86  
support for Mac OS X, would it be beneficial to modify the mkfile's  
for the Darwin port to support the MachO multi-binary options by  
making 9c & 9l deal with the Darwin sources in a similar way as the  
Plan 9 compiler does?  Though MachO supports 'fat' binaries after the  
linker has handled them, I think it would be better to handle the  
object files in the same manner as the Plan 9 compiler and save them  
as .[v851ok0q2t6] only to let the linker squish them together if  
needed (still allowing for fully separate libraries and executables  
for each Darwin platform if needed).

Would anyone mind if I made the required changes to 9c, 9l and any  
supporting mkfiles?

jas



  reply	other threads:[~2005-11-10  5:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 20:19 Ronald G Minnich
2005-11-09 20:28 ` Ben Huntsman
2005-11-09 20:30 ` Russ Cox
2005-11-09 20:50   ` Matt Sottile
2005-11-09 20:52     ` Ronald G Minnich
2005-11-10  2:18       ` Jeff Sickel
2005-11-10  3:46         ` Ronald G Minnich
2005-11-10  5:25           ` Jeff Sickel [this message]
2005-11-10  5:53             ` Russ Cox
2005-11-10  7:30               ` Jeff Sickel

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=98C8D026-907D-4DAB-8A12-05C964625FA4@corpus-callosum.com \
    --to=jas@corpus-callosum.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).