Re: tux module problems with gcc3.2.2?

Thanks for the response Alex.
(Strange Date: header below!)

I will try to find the time to search for your diffs and also determine what 
Redhat has done.

On November 21, 2002 10:25 am, Alex Kramarov wrote:
>  redhat supply their kernel with the latest tux module, and they compile
> their kernel for RH 8.0 with gcc 3.2.x - you can check what they did.
>
> but your error is not about that. you are trying to compile the standard
> tux module with a non-standard kernel (or redhat's kernel, which is the
> same) that has the O1 sheduler - tux as is will not compile with that.
>
> once again, you will need to see the changes that redhat did in their
> kernel with tux - i posted a diff once to the list.
>
> Alex.
>
> -------Original Message-------
>
> From: [email protected]
> Date: éåí çîéùé 21 ðåáîáø 2002 16:49:16
> To: [email protected]
> Subject: tux module problems with gcc3.2.2?
>
> Has anyone successfully compiled Tux as a module with the latest gcc-3.2.2
> with the most recent glibc-2.2.5?
> I can't do it. I get unresolved symbols.
> Also, other packages I compile like win4lin now get unresolved symbols and
> they have compiled and worked great for 6 months with and older gcc. Errors
> like this:
>
> /lib/modules/2.4.18/kernel/arch/i386/mki-adapter/mki-adapter.o: unresolved
> symbol sys_sched_yield
>
> Thanks.

-- 
Schedule your world with ScheduleWorld.com
http://www.ScheduleWorld.com/