From: Warren Toomey <wkt@tuhs.org>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Deleted lib1 and lib2 in v6, recoverable?
Date: Sat, 29 Dec 2018 14:59:13 +1000 [thread overview]
Message-ID: <20181229045913.GA21435@minnie.tuhs.org> (raw)
In-Reply-To: <82e23dba-38a4-3ee4-e35a-6293b8eef749@gmail.com>
> On 12/28/18 7:35 PM, Warren Toomey wrote:
> > I just tried it here. I had to do:
> > chdir ken; ...
> > ar r ../lib1 *.o
> > chdir ../dmr; ...
> > ar r ../lib2 *.o
On Fri, Dec 28, 2018 at 08:02:55PM -0600, Will Senn wrote:
> I wound up doing:
> chdir ken
> cc -c -O *.c
> ar r ../lib1 main.o
> ar r ../lib1 alloc.o
> ar r ../lib1 iget.o
> ar r ../lib1 prf.o
> ar r ../lib1 rdwri.o
> ar r ../lib1 slp.o
> ar r ../lib1 subr.o
> ar r ../lib1 text.o
> ar r ../lib1 trap.o
> ar r ../lib1 sig.o
> ar r ../lib1 sysent.o
> ar r ../lib1 clock.o
> ar r ../lib1 fio.o
> ar r ../lib1 malloc.o
> ar r ../lib1 nami.o
> ar r ../lib1 pipe.o
> ar r ../lib1 sys1.o
> ar r ../lib1 sys2.o
> ar r ../lib1 sys3.o
> ar r ../lib1 sys4.o
>
> rm *.o
>
> chdir ../dmr
> cc -c -O *.c
>
> ar r ../lib2 bio.o
> ar r ../lib2 tty.o
> ar r ../lib2 dc.o
> ar r ../lib2 dn.o
> ar r ../lib2 dp.o
> ar r ../lib2 kl.o
> ar r ../lib2 mem.o
> ar r ../lib2 pc.o
> ar r ../lib2 rf.o
> ar r ../lib2 rk.o
> ar r ../lib2 tc.o
> ar r ../lib2 tm.o
> ar r ../lib2 partab.o
> ar r ../lib2 rp.o
> ar r ../lib2 lp.o
> ar r ../lib2 dhdm.o
> ar r ../lib2 dh.o
> ar r ../lib2 dhfdm.o
> ar r ../lib2 sys.o
> ar r ../lib2 hp.o
> ar r ../lib2 ht.o
> ar r ../lib2 hs.o
> rm *.o
>
> Then I continued with the system build and it worked and my changes were
> there!
> Will
Yes, order will be important, I forgot. There's no ranlib in v6 :-)
Cheers, Warren
next prev parent reply other threads:[~2018-12-29 4:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 1:09 Noel Chiappa
2018-12-29 1:26 ` Will Senn
2018-12-29 1:35 ` Warren Toomey
[not found] ` <82e23dba-38a4-3ee4-e35a-6293b8eef749@gmail.com>
2018-12-29 4:59 ` Warren Toomey [this message]
2018-12-29 16:26 ` Clem Cole
2018-12-29 16:49 ` Warner Losh
2018-12-29 17:48 ` Clem cole
2018-12-30 18:34 ` Paul Winalski
2018-12-30 18:48 ` ron
2018-12-30 18:56 ` Warner Losh
2018-12-30 19:02 ` Paul Winalski
2018-12-31 0:00 ` Donald ODona
2018-12-31 17:51 ` Paul Winalski
-- strict thread matches above, loose matches on Subject: below --
2018-12-31 3:22 Rudi Blom
2018-12-31 2:28 Doug McIlroy
2018-12-31 3:34 ` Will Senn
2018-12-31 6:52 ` ron
2018-12-30 19:07 Norman Wilson
2018-12-30 19:24 ` Paul Winalski
2018-12-31 6:57 ` arnold
2019-01-02 13:54 ` Tony Finch
2018-12-29 14:13 Noel Chiappa
2018-12-29 0:25 Will Senn
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=20181229045913.GA21435@minnie.tuhs.org \
--to=wkt@tuhs.org \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).