Hi John,
The RAM is fine. As a matter of fact I'm getting the same types of errors
on my workstation at work too. It's really very discouraging that the darn
thing just won't compile cleanly.
--
Mark
/* I never worry about the to-jams.
* Once I've stuck my foot in my mouth
* it's already too late...just make sure
* you chew them thoroughly before swallowing!
*/
Registered Linux user #182496
* Pine 4.21 *
On Wed, 18 Oct 2000 2:34pm ,John Rye spake passionately in a message:
> Mark Weaver wrote:
> >
> > Hi list,
> >
> > Before I get started could someone please pass me the cheese to go with my
> > wine?
> >
> > That being said, I've been working on this getting this stupid kernel
> > recompiled to accomodate a Turtle Beach sound card for two stinkin weeks
> > and the darn thing continually bombs out on one error or another. If its
> > not choking on imaginary bad code, then it's telling me that something
> > else is wrong somewhere. It doesn't seem to matter "how" I configure the
> > stinkin thing it always bombs out with an error.
> >
> > The usual thing is a parsing error, or it says there's a '{' missing, or
> > there's a ')' missing, or even more bizare is the compiler error that I
> > got tonight. It doesn't matter if I'm trying to do a recompile of
> > 2.2.16-9mdk, or a new config and compile of 2.2.17. The results are the
> > same. The compile bombs on an error. On the off chance that it does
> > compile without any errors and all the modules are made and installed then
> > the damn thing doesn't work right and there are a few things that just
> > don't work on the system. pppd for one and the other that really knots my
> > shorts is the friggin sound. The whole reason I'm torturing myself in the
> > first place.
> >
> > So, what I really need is some in depth documentation that will cover, in
> > explanitory fashion, the compiler errors that gcc gives and what to do and
> > how to do "good" compilations of these darn kernels. As I write this I'm
> > preparing to torture myself some more by downloading kernel 2.4test9. I
> > don't know why I'm even thinking I'm going to get it to work. It'll
> > probably bomb like the rest of these. Frankly I don't know how others are
> > getting them to compile and work!
> >
> > thanks for letting me rant. I'm done now.
> >
> > --
> > Mark
> >
> > /* I never worry about the to-jams.
> > * Once I've stuck my foot in my mouth
> > * it's already too late...just make sure
> > * you chew them thoroughly before swallowing!
> > */
> > Registered Linux user #182496
> > * Pine 4.21 *
>
> Mark
>
> I was getting a heap of similar errors a while back, on whatever
> I attempted to compile.
>
> Check your RAM as a first step.
>
> I had no end of trouble trying compile 2.2.17 - gave it away after
> not being able to get several modules to compile with the same
> kinds of errors, (missing punctuation characters, no end of line
> in line xxx), and so on.
>
> I haven't bothered to revisit.
>
> Cheers
>
