> I've been trying to find out what in the generic
> kernel image is not working on my box and have been
> unsuccessful as of yet. I tried about 8 times last
> night. It seems to always panic right after it sees
> the IDE cdrom drive. I'm going to try building the
> kernel tonight without any ide support to see if that
> is the problem or not.
Hmmm.....I'd like to say that I could start to take a look into it, but I
don't have the hardware so I think you're pretty much the best person for
the job. Have you tried changing the kernel type from "generic" to your
specific type of machine?
> As for gcc.. I've been having all sorts of issues.. so
> I think that for now egcs is the best choice. I looked
> at what the NetBSD folks are doing and it basicly
> looks like they are trying to merge gcc and egcs. They
> are spending a lot of time picking and choosing what
> goes in the compiler. Hopefully at some point.. gcc
> will work out. But for now.. egcs I think will do.
Yeah, we're sticking with egcs all over the place. And what's more, we're
sticking with glibc-2.1.3 until I can make egcs compile it correctly. I
worked on building it with the patched gcc last night, and it gave me all
sorts of random behavior. So we're going to be a little behind for a
while, but I don't really have a problem with that.
I've added another question to the FAQ in the distribution tree that
explains all of this.
Now maybe I can quit spending all my time on toolchain stuff and actually
make some progress.
--
Chris Lumens - chris@slackware.com - KG6CIH
@n=(-42,-85,-83,-19,65,2,-10,-10,-15,-3,2,-10,73,-4,8,-4,2,79,8,17,15,7,14,2);
print map{chr(-$n[$i++]+ord)} sort(split(//,'place random string here')),"\n";
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT