From: Hellwig.Geisse@mni.fh-giessen.de (Hellwig.Geisse@mni.fh-giessen.de)
Subject: [TUHS] V7 unix
Date: Sat, 27 May 2006 11:23:25 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20060527112325.Hellwig.Geisse@mni.fh-giessen.de> (raw)
In-Reply-To: <000301c68109$edd3b040$2f01a8c0@myhome.westell.com>
Hi Bill,
On 26-May-2006 Bill Cunningham wrote:
> I have noticed something about your v7 creation. When I try to use the C
> compiler to compile fp support or any system structures(not structs but
> components) I get an error /lib/c0 so there's something wrong with the c0
> pass in libc. It was probably that way when the tapes were recovered. I have
> managed to compile and assemble all the c source in the /usr/src/cmd/c
> directory into object files so the assembler works. What should I do
> manually with all these .o files? I need a working compiler.
in principle, the .o files have to be bound (together with
the libraries) by the linker, which produces the executable.
But this is tedious to do manually, so you better use the
makefile (and the "make" utility) to run the necessary
commands automatically.
I can reproduce your problem with the c0 pass. I don't
know the exact cause but I guess it has nothing to do
with the compiler itself. I found a workaround: reset
the sticky bit for cc, i.e., do a "chmod 755 cc" in /bin.
At least on my machine I then can run the makefile for
building cc without errors.
Hellwig
prev parent reply other threads:[~2006-05-27 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 21:18 Bill Cunningham
2006-05-27 8:07 ` Andrzej Popielewicz
2006-05-27 9:23 ` Hellwig.Geisse [this message]
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=XFMail.20060527112325.Hellwig.Geisse@mni.fh-giessen.de \
--to=hellwig.geisse@mni.fh-giessen.de \
/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).