From: kevin diggs <diggskevin38@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Linux 2.6.29+ on PowerMac 8600
Date: Thu, 20 Jan 2011 19:55:00 -0000 [thread overview]
Message-ID: <AANLkTik9w6Q_jYjv=7deS7wbRsmex6VJ8HtHtbMLsFyM@mail.gmail.com> (raw)
Hi,
I've tried the PowerPC Linux list with no luck. Maybe someone here has an idea.
I have a PowerMac 8600 running Linux (Yellowdog 4.0). The stock
compiler is 3.3.3. I tried building the latest 3 series I could find.
That was 3.4.6. It can not compile the kernel sources. As a test of
the compiler I used it to compile Firefox 2. It will run. Experience
with Yellowdog 6.0 on a G5 (970FX x 2) suggests you need 4.1.2+ to
build Linux 2.6.29+.
So it off to version 4.3.5. After lots of fun tracking down why
Firefox won't run (issues with which libstdc++ is being used) I
finally get a kernel to compile. It won't run. I also can't get 2.6.28
to run when it is compiled with 4.3.5. I can get 2.6.28 to run
compiled with 3.4.6.
Now it gets a little weird ...
I also have a dual G4 GigE (dual 7455 @ 1.1 GHz) that is running YDL
4.0. Using the same procedure to bootstrap 4.3.5 (3.3.3 -> 3.4.6 ->
4.3.5) I CAN build 2.6.36 and boot it. I don't think the YDL installer
supports the 8600 so I am pretty sure the 4.0 installation on the 8600
was cloned from this system.
Off to the twilight zone ...
I decided to try cross system kernel building. Not recommended by the
FDA but I'm desperate. I have built a kernel for the GigE using the
8600 and 4.3.5 and it seems to boot on the G4.
Any thoughts would be appreciated.
kevin
P.S.: I also have a fun issue involving a Quadra 700: stock 25 MHz
68040 vs 50 MHz cpu upgrade and the -fno-gcse option if anyone is
interested.
reply other threads:[~2011-01-20 19:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='AANLkTik9w6Q_jYjv=7deS7wbRsmex6VJ8HtHtbMLsFyM@mail.gmail.com' \
--to=diggskevin38@gmail.com \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).