From: Jerry W Johnson jwjohn@ecst.csuchico.edu
Subject: ALEF Installation (REPOST)
Date: Fri, 13 Aug 1993 11:30:58 -0400 [thread overview]
Message-ID: <19930813153058.AtSvQfIClyng6xXRIEhaGeRnAghK0UebewNjFo5HPXY@z> (raw)
I think this had some problems getting out. Sorry, if you got
it twice. --JJ
Hi 9'ers,
I've run into some problems installing the new ALEF files.
To get this far, I:
Copied the old alef tree to /sys/src/alef.old.
Installed the new tree into /sys/src/alef.
Copied back fcall.h and the conversions, convM2S & convS2M.
Copied the new include files to /sys/include/alef.
Installed the new sparc mkfile and mksyslib.
Made the dirs /$objtype/lib/alef where not done.
Made the new compilers (kal,val,8al) by running the mkfiles
in /sys/src/alef/k
/v
/8
using "objtype=architecture mk" and copying the resulting binary
to /$objtype/bin.
Then from /sys/src/alef I ran "objtype=architecture mk install";
all the libraries (/$objtype/lib/alef/*.a) seem to compile fine,
(assuming none generated for the 68020 & only libA.a, libbio.a for
the 386), but $objtype=mips generates the error:
val -w div64.l
div64.l":12: syntax error near symbol 'lint'
mk: val -w div64.l : exit status=rc 8989:val 8991 errors
mk: for (i in ... : exit status:=rc 8191:mk 8999:error
mk: @{cd v; mk ... : exit status=rc 8049:val 8991:errors
mk: for (i in ... : exit status=rc 8191:mk 8988:error
mk: @{cd v; mk ... : exit status=rc 8042:mk 8190:error
mk: mk $objtype.install : exit status=rc 8039:mk 8041:error
If, instead, "mk installall" is executed from /sys/src/alef,
the compile lists errors "ar: *.8 cannot open" for:
/sys/src/alef/lib/libbio,
/sys/src/alef/lib/p9, & ( announce.l:69 WARNING parameter
INT nf declared but not used )
/sys/src/alef/lib/port.
Anybody got any ideas, insights?
ALSO,
once the installation is complete, will the example code which
came on the 2nd rev cdrom, (/sys/src/alef/test, /sys/src/alef/test/Y),
all compile correctly?
reply other threads:[~1993-08-13 15:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19930813153058.AtSvQfIClyng6xXRIEhaGeRnAghK0UebewNjFo5HPXY@z \
--to=9fans@9fans.net \
/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).