From: Ken Offer <koffer@arlut.utexas.edu>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Yellow-dog-linux troubles
Date: Mon, 07 May 2001 16:29:59 -0500 [thread overview]
Message-ID: <3AF713D7.3B3500C2@arlut.utexas.edu> (raw)
Hello all-yall-linuxppc-hackers,
Has anybody out there had any luck getting a Synergy-micro VSS4 board
(i.e. a cool one-board computer with 4 PPC-G3s on it) to compile the
latest 2.4.4 and 2.4.2 yellow-dog kernels cleanly? I'm using gcc
2.95.2. Any gcc above 2.6.3 should compile the kernel cleanly, right?
--
______________________________________________________________
Kenneth Ray Offer, II
Sr. Systems Analyst
Applied Research Laboratories/SDD
University of Texas at Austin
Office (512) 835-3859 FAX (512) 835-3259
Any opinions expressed above are mine and not necessarily
those of my employer.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-05-07 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 21:29 Ken Offer [this message]
2001-05-07 21:58 ` Yellow-dog-linux troubles Gabriel Paubert
2001-05-07 23:09 ` Val Henson
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=3AF713D7.3B3500C2@arlut.utexas.edu \
--to=koffer@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).