From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] hehe bad to worse
Date: Thu, 10 May 2001 14:00:54 -0400 [thread overview]
Message-ID: <20010510180056.9B3EF19A0F@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
If you've managed to do all the wraps in order, nothing has to
be changed.
I made two mistakes in the last wrap that canceled each other out:
- port/segment.h should have been removed
- portmkfile should have been fixed to not have segment.$O depend
on it any more
I didn't put either in so following the wraps, things should
continue to compile OK, albeit with a file that doesn't need to be there.
It could confuse someone that changes segment.h and then notices that the
change doesn't make it into the resulting kernel.
[-- Attachment #2: Type: message/rfc822, Size: 2848 bytes --]
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: Re[2]: [9fans] hehe bad to worse
Date: Thu, 10 May 2001 19:47:05 +0200
Message-ID: <200105101747.TAA25135@copernicus.cs.utwente.nl>
Now I'm slightly confused. My /sys/src/9/port/portmkfile contains
segment.$O: ../port/segment.h
This is the line that is to be deleted, I assume, or???
For the record, AFAIK I succesfully applied both wraps, and succeeded
to remake everything, including kernels.
Axel.
> my fault, I should have put a new port/portmkfile in the last wrap.
> Just remove the
>
> segment.$O: segment.h
>
> line from portmkfile, segment.h is history, its contents are in segment.c.
next reply other threads:[~2001-05-10 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 18:00 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 16:27 presotto
2001-05-10 17:47 ` Axel Belinfante
2001-05-09 14:35 Russ Cox
2001-05-09 14:43 ` Re[2]: " Matt H
2001-05-09 9:48 matt
2001-05-10 15:15 ` Douglas A. Gwyn
2001-05-10 15:36 ` Re[2]: " Matt H
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=20010510180056.9B3EF19A0F@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.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).