From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Applying patches to local machine
Date: Fri, 2 Nov 2007 08:35:29 -0400 [thread overview]
Message-ID: <8996e9fb1d945bb1fd727f12fe64f9c2@quanstro.net> (raw)
In-Reply-To: <509071940711020452n6372fbb4h9da4b2b12f1d6701@mail.gmail.com>
> all the /bin/patch/* files are just shell scripts, so it's easy to see
> what's going on. which stage gives you permission errors? in a default
> setup, you'll have to be in group sys, as that's who owns all the
> sources.
>
> if you can't be in sys for whatever reason, you'll have a somewhat
> more manual process ahead of you. identify the files to be modified,
> create local copies (i'm assuming you can at least *read* them,
> otherwise this is probably futile), bind them over the system ones,
> and re-run the patch command.
>
> of course, i'm largely guessing without an error message.
read the source, luke.
patch/apply assumes you are at bell labs with appropriate permissions
to /n/sources. the script bails if you can't touch files in the patch's
directory.
it is also likely that you'll need to merge the source by hand as
the piemenu patch is very old.
you likely want to make a seperate copy of libdraw and link against
it selectivly by binding the archive on /386/lib/libdraw.a
- erik
next prev parent reply other threads:[~2007-11-02 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 10:11 Christian Kellermann
2007-11-02 10:21 ` Charles Forsyth
2007-11-02 10:25 ` Christian Kellermann
2007-11-02 10:39 ` Anthony Sorace
2007-11-02 10:44 ` Christian Kellermann
2007-11-02 11:35 ` Christian Kellermann
2007-11-02 11:52 ` Anthony Sorace
2007-11-02 12:35 ` erik quanstrom [this message]
2007-11-02 18:47 ` Dave Eckhardt
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=8996e9fb1d945bb1fd727f12fe64f9c2@quanstro.net \
--to=quanstro@quanstro.net \
--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).