9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Raschke <rrplan9@tombob.com>
To: Christian.Kellermann@nefkom.net, 9fans@cse.psu.edu
Subject: Re: [9fans] Removal of .i files from sources?
Date: Tue,  4 Dec 2007 09:22:36 +0000	[thread overview]
Message-ID: <12e6624a424b72d880905cc938d36326@tombob.com> (raw)
In-Reply-To: <20071203222511.GA1228@hermes.my.domain>

Christian Kellermann wrote:
> I need to build a cpu kernel from sources. Therefore I have been
> following the tip of the day recipie from the wiki. Assembling the
> sd*.n files fails due to the corresponding .i files already exist.
> In my current setup I cannot delete those nor touch them or change
> permissions.
> 
> How can I get around this? Why are those precompiled files there
> in the first place? I would not expect seeing 8c object files on
> sources either... Would a removal be sensible?

I haven't looked at the Tip of the Day description recently, but I
have a few folders on my local tree, where I bind the central sources
into in such a way that I can have my own local files overshadowing
the central ones

bind -c $home/src/kernel/pc $home/src/kernel/pc
bind -a /sys/src/9/pc $home/src/kernel/pc

You should then be able to copy one of the central .i files into you bound location. making it read/writable for you and it overshadowing the central one.

Robby



  reply	other threads:[~2007-12-04  9:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 22:25 Christian Kellermann
2007-12-04  9:22 ` Robert Raschke [this message]
     [not found] ` <adc391e1dfd3d40c6439b19c65d02dff@tombob.com>
2007-12-04  9:43   ` Christian Kellermann
2007-12-04 17:45 ` Dave Eckhardt
2007-12-05  8:08   ` Christian Kellermann
2007-12-05 13:56     ` David Leimbach

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=12e6624a424b72d880905cc938d36326@tombob.com \
    --to=rrplan9@tombob.com \
    --cc=9fans@cse.psu.edu \
    --cc=Christian.Kellermann@nefkom.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).