The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warren Toomey <wkt@tuhs.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Deleted lib1 and lib2 in v6, recoverable?
Date: Sat, 29 Dec 2018 11:35:27 +1000	[thread overview]
Message-ID: <20181229013527.GA3844@minnie.tuhs.org> (raw)
In-Reply-To: <20181229010900.19F6218C074@mercury.lcs.mit.edu>

On Fri, Dec 28, 2018 at 08:09:00PM -0500, Noel Chiappa wrote:
> Odd. 'run' in /usr/sys on my V6 machine (not that I use that, mind) says:
>   
>   chdir ken
>   cc -c -O *.c
>   ar r ../lib1
>   rm *.o
>   chdir ../dmr
>   cc -c -O *.c
>   ar r ../lib2
>   rm *.o        
> 
> which should regenerate them - sort of.

I just tried it here. I had to do:
	chdir ken; ...
	ar r ../lib1 *.o
	chdir ../dmr; ...
	ar r ../lib2 *.o

to get them to rebuild. Otherwise, I had empty libraries.

Cheers, Warren

  parent reply	other threads:[~2018-12-29  1:35 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 [this message]
     [not found]   ` <82e23dba-38a4-3ee4-e35a-6293b8eef749@gmail.com>
2018-12-29  4:59     ` Warren Toomey
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=20181229013527.GA3844@minnie.tuhs.org \
    --to=wkt@tuhs.org \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@minnie.tuhs.org \
    /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).