From: David Morris <lists@morris-clan.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9port build failure on Linux (debian)
Date: Mon, 3 Mar 2008 01:46:39 -0700 [thread overview]
Message-ID: <20080303084639.GB24732@morris-clan.net> (raw)
In-Reply-To: <20080303084557.GA24732@morris-clan.net>
On Mon, Mar 03, 2008 at 01:23:06PM +0800, Hongzheng Wang wrote:
> Hi,
>
> I have just cvsed and rebuilt the whole system. No error
> occurs. And my system is Debian sid. So, I think the
> problem you encountered might due to some missing or
> mismatched packages on your debian box. Perhaps, the
> install.log in /usr/local/plan9/ would be helpful to
> discover what's wrong during installation.
Well, one step forward, one step back....
install.log was no help, the message I quoted was everything
relevant.
I took a stab at running gdb through yacc, but the compiler
optimized the code to the point finding the problem was
nearly impossible.....best I can say is its somewhere in the
dofmt() function (lib9/fmt/dofmt.c) or something it calls.
So I pulled out my VERY slow laptop and spent a few hours
letting it compile plan9port.
This time the build worked, so looks like some lenny/sid
packages don't work well together. Hmm, or another
possibility occurs to me. I use the AMD64 kernel
(2.6.22-3-amd64) on my desktop, but i686 on the laptop
(2.6.22-3-i686). Any chance that could cause a problem?
I tried copying the "pure lenny" install to the main system
file structure, but that clearly does not work because wmii
(the application I need plan9port for) does not run.
So, any ideas on how to fix the build process? The problem
stems from yacc.c at line #2173 in the sprint() function.
Could I replace that with the standard library sprintf()
function as a stop-gap measure?
--David
next prev parent reply other threads:[~2008-03-03 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 4:20 David Morris
2008-03-03 5:23 ` Hongzheng Wang
[not found] ` <20080303084557.GA24732@morris-clan.net>
2008-03-03 8:46 ` David Morris [this message]
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=20080303084639.GB24732@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).