From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@9fans.net
Subject: Re: [9fans] System build: /sparc64 file does not exist; NOT on sparc64
Date: Sun, 22 Apr 2012 07:06:03 +0200 [thread overview]
Message-ID: <d0e51a88b26735271bc6628f06c8b399@proxima.alt.za> (raw)
In-Reply-To: <CAL3m8eAW2tCto5m3=W4ad=EKc4EjOyZFJPR9PWLXQh8uBqPUAQ@mail.gmail.com>
> I am not on sparc64 machine. I tried to disable all arch but (6 9) in
> mkfile, but then build fails thus:
What are you on?
Obviously there is an error in the build procedure, but it would be useful to know what is triggering it.
On my workstation:
term% cat /dev/archctl
cpu PentiumIII/Xeon 931 pge
pge on
coherence mb586
cmpswap cmpswap486
i8253set on
cache default uc
cache 0x0 268435456 wb
cache 0xf800000 8388608 uc
cache 0xd8000000 67108864 wc
cache 0xd0000000 67108864 wc
++L
next prev parent reply other threads:[~2012-04-22 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 1:17 Strake
2012-04-22 5:06 ` Lucio De Re [this message]
2012-04-22 8:34 ` David du Colombier
2012-04-22 17:30 ` Strake
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=d0e51a88b26735271bc6628f06c8b399@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=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).