9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] p9p mk issue
Date: Tue, 20 Nov 2007 14:48:12 -0800	[thread overview]
Message-ID: <20071120224812.56E875B3E@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 20 Nov 2007 16:20:12 CST." <B426CA1D-1583-4BAC-9AD6-E3F30654AB6E@corpus-callosum.com>

> 
> On Nov 20, 2007, at 3:44 PM, Pietro Gagliardi wrote:
> 
> >
> > On Nov 20, 2007, at 4:01 PM, Bakul Shah wrote:
> >
> >> Don't laugh but I am trying to use identical mkfiles on
> >> FreeBSD & plan9 for some programs and it seems this is
> >> impossible.
> >>
> > PS - In my version of hoc(1), which is pure ANSI C, I use a makefile  
> > for UNIX systems and an mkfile for Plan 9.
> 
> you should be able to do some sort of magic like:
> 
> <!cat $PLAN9/$objtype/mkfile.$SYSNAME

For now I just changed default MKSHELL to rc in src/cmd/mk.
What I was really arguing for was for simplifying MKSHELL
semantics or getting rid of it altogether since it only
exists in p9p mk.


  reply	other threads:[~2007-11-20 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 21:01 Bakul Shah
2007-11-20 21:08 ` Pietro Gagliardi
2007-11-20 21:44 ` Pietro Gagliardi
2007-11-20 22:20   ` Jeff Sickel
2007-11-20 22:48     ` Bakul Shah [this message]
2007-11-21  7:44       ` John Stalker
2007-11-21 16:01       ` Russ Cox
2007-11-21 18:01         ` Bakul Shah
2007-11-21 19:57           ` Pietro Gagliardi
2007-11-22 15:47           ` Russ Cox
2007-11-22 17:43             ` Bakul Shah
2007-11-22 18:20               ` Martin Neubauer
2007-11-22 19:48               ` Russ Cox
2007-11-30 18:01                 ` Bakul Shah
2007-11-30 19:01                   ` 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=20071120224812.56E875B3E@mail.bitblocks.com \
    --to=bakul+plan9@bitblocks.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).