From: Ta-Wei Li taweil@ucs.usc.edu
Subject: mk error on NeXT
Date: Thu, 5 Oct 1995 04:18:11 -0400 [thread overview]
Message-ID: <19951005081811.4j8IOIPthsnn7T2xXKg-28d8MlWq493roWuam2MxiPk@z> (raw)
When I try to recompile the 9nextstation, I got the following error from mk:
builtin cd ../boot
mk
mk: 'install' is up to date
2c -w '-DKERNDATE='`{date -n} nextstation.c
2l -o 9nextstation -l -H3 -T0x04000000 -R0x2000 vec.2 l.2 alarm.2
alloc.2 auth.2 chan.2 clock.2 dev.2 fault.2 fault68040.2 latin1.2
taslock.2 main.2 mmu.2 net.2 page.2 segment.2 swap.2 pgrp.2 print.2
proc.2 qlock.2 queue.2 screen.2 sysfile.2 sysproc.2 trap.2 fptrap.2
devroot.2 devcons.2 devenv.2 devpipe.2 devproc.2 devsrv.2 devmnt.2
^^^^^^^^^^
devdup.2 devbit.2 devether.2 devscc.2 devscsi.2 scsi.2 scsibuf.2
devnextfloppy.2 deviproute.2 devip.2 tcpinput.2 tcpoutput.2 tcptimer.2
tcpif.2 stil.2 devarp.2 devrtc.2 devdk.2 devaudio.2 devkprof.2
devicmp.2 bootnextstation.root.2 stream.2 sturp.2 stasync.2 stip.2
stfcall.2 bbmalloc.2 nextstation.2 -lgnot -lg -lauth -lc
size 9nextstation
nextstation.c:11 name not declared: rootreset
nextstation.c:11 name not declared: rootinit
nextstation.c:11 name not declared: rootattach
nextstation.c:11 name not declared: rootclone
nextstation.c:11 name not declared: rootwalk
nextstation.c:11 name not declared: rootstat
nextstation.c:11 name not declared: rootopen
nextstation.c:11 name not declared: rootcreate
nextstation.c:12 name not declared: rootclose
nextstation.c:12 name not declared: rootread
nextstation.c:12 name not declared: rootwrite
too many errors
All the root* functions are defined in devroot.2 but it wasn't regonized for
some reason. Can anyone help me? Thanks in advance.
Ta-Wei Li
next reply other threads:[~1995-10-05 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-05 8:18 Ta-Wei [this message]
1995-10-05 17:35 bobf
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=19951005081811.4j8IOIPthsnn7T2xXKg-28d8MlWq493roWuam2MxiPk@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).