From: David Morris <lists@morris-clan.net>
To: 9fans@cse.psu.edu
Subject: [9fans] plan9port build failure on Linux (debian)
Date: Sun, 2 Mar 2008 21:20:17 -0700 [thread overview]
Message-ID: <20080303042017.GE14610@morris-clan.net> (raw)
I am trying to install plan9port on a Linux system (Debian),
and am getting the following error:
9 yacc -d -s bc bc.y
fatal error:can't create , <nil>:1
mk: 9 yacc -d ... : exit status=exit(1)
mk: for i in ... : exit status=exit(1)
Everything compiles just fine up to this point with no
errors. This looks to be the first step of building the
lexx application. Because there is no filename listed in
the error message, I am guessing this is the result of a bug
in the code or the makefile (err, mkfile, I suppose).
Any idea of what the problem is? Or if its a bug in the
code, where I can get a stable version?
Details of my build environment and my install process
follow....
OS : Debian lenny (with a few packages from sid (unstable))
Arch: i386
plan9port version:
downloaded Saturday from http://swtch.com/plan9port/
After bug, updated from CVS
Install location: /usr/local
Install process:
# cd /usr/local
# sudo tar xvzf plan9port.tgz
# cd plan9
# sudo ./INSTALL
(failed with noted error)
# sudo cvs update -dP
# sudo ./INSTALL
(failed with noted error)
Thanks,
--David
next reply other threads:[~2008-03-03 4:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 4:20 David Morris [this message]
2008-03-03 5:23 ` Hongzheng Wang
[not found] ` <20080303084557.GA24732@morris-clan.net>
2008-03-03 8:46 ` David Morris
2008-03-03 15:09 ` sqweek
2008-03-03 16:25 ` David Morris
2008-03-03 16:17 ` Russ Cox
2008-03-03 17:27 ` David Morris
2008-03-03 19:02 ` erik quanstrom
[not found] ` <20080303195459.GE28226@morris-clan.net>
2008-03-03 19:56 ` David Morris
2008-03-04 4:42 ` Russ Cox
2008-03-05 16:21 ` Douglas A. Gwyn
2008-03-03 14:10 erik quanstrom
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=20080303042017.GE14610@morris-clan.net \
--to=lists@morris-clan.net \
--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).