9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Herbert B. Hancock" <bhancock@rutgers.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new pcauth compilation problem
Date: Thu, 28 Aug 2003 09:38:06 -0400	[thread overview]
Message-ID: <683f2653a4.653a4683f2@rutgers.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]

Hi Dave, thanks for the reply.  The files:

ethermedium.8
netdevmedium.8
loopbackmedium.8

are not in the list of args even after running 'mk clean'.

Regards,
Brian

----- Original Message -----
From: David Presotto <presotto@closedmind.org>
Date: Thursday, August 28, 2003 9:14 am
Subject: Re: [9fans] new pcauth compilation problem

> Have you done a 'mk clean' in the /sys/src/9/pc directory and tried
> again?  It looks
> like the files:
> 	ethermedium.8
> 	netdevmedium.8
> 	loopbackmedium.8
> are screwed up.  These files should have those symbols defined.
>
> Also, make sure that those .8's appear in the list of args when 8l
> links the
> kernel.  For example:
>
> 8l -o 9pcauth -T0x80100020 -l l.8 plan9l.8 cga.8 i8253.8 i8259.8
> kbd.8 main.8 memory.8 mmu.8 random.8 rdb.8 trap.8 pcauth.root.8
> pcauth.rootc.8 vga.8 ether82557.8 uarti8250.8 sdata.8 devmnt.8
> iproute.8 devtls.8 devdup.8 devenv.8 tcp.8 apm.8 devsd.8 vgax.8
> devarch.8 ipifc.8 devether.8 chandial.8 devsrv.8 icmp.8
> ethermedium.8 devcap.8 devproc.8 dma.8 devmouse.8 devrtc.8
> devfloppy.8 ip.8 udp.8 ipv6.8 devcons.8 devpnp.8 il.8 devuart.8
> arp.8 uartpci.8 screen.8 devip.8 ptclbsum386.8 devkprof.8
> pktmedium.8 vgamach64xx.8 ipaux.8 devpipe.8 loopbackmedium.8
> apmjump.8 devfs.8 sdscsi.8 inferno.8 devroot.8 netlog.8 devvga.8
> mouse.8 devdraw.8 devssl.8 nullmedium.8 netif.8 pci.8 icmp6.8
> netdevmedium.8 alarm.8 alloc.8 allocb.8 auth.8 cache.8 chan.8 dev.8
> fault.8 latin1.8 nulledf.8 page.8 parse.8 pgrp.8 portclock.8
> print.8 proc.8 qio.8 qlock.8 rebootcmd.8 segment.8 swap.8 sysfile.8
> sysproc.8 taslock.8 tod.8 xalloc.8 pcauth.8 /386/lib/libmemlayer.a
> /386/lib/libmemdraw.a /386/lib/libdraw.a /386
> /lib/libc.a /386/lib/libsec.a
>
> If not, something else is wrong and we can bang at it off line.

[-- Attachment #2: Type: message/rfc822, Size: 2873 bytes --]

From: "Herbert B. Hancock" <bhancock@rutgers.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] new pcauth compilation problem
Date: Thu, 28 Aug 2003 09:04:23 -0400
Message-ID: <670a2665a6.665a6670a2@rutgers.edu>

Hi, I've just completed a replica/pull and now find pcauth won't compile properly.  I haven't modified the file and get the error messages:

..........
size pcauth
links: undefined: ethermediumlink in links
links: undefined: netmediumlink in links
links: undefined: loopbackmediumlink in links
mk: 8c -FVw '-DKERNDATE=''{date ... :exit status=rc 1313: 8l 1317: error
...........
The link section in pcauth has not been changed.
Does anyone have any ideas why this might happen.  I had no trouble compiling pcauth before upgrading.
Thanks,
Brian



             reply	other threads:[~2003-08-28 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 13:38 Herbert B. Hancock [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-28 13:14 David Presotto
2003-08-28 13:04 Herbert B. Hancock

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=683f2653a4.653a4683f2@rutgers.edu \
    --to=bhancock@rutgers.edu \
    --cc=9fans@cse.psu.edu \
    /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).