|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
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: firstname.lastname@example.org Date: éåí çîéùé 21 ðåáîáø 2002 16:49:16 To: email@example.com Subject: tux module problems with gcc3.2.2? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE92qzJBtoFHHwdJ/cRAkr+AKCONrufH19X54jVwQsMHQCxum45SwCfTUtb UuaNmCR9Fz+UilfRbafRVks= =sSbg -----END PGP SIGNATURE----- _______________________________________________ firstname.lastname@example.org https://listman.redhat.com/mailman/listinfo/tux-list .
[Older Fedora Users Mail] [Home] [Fedora Legacy] [Fedora Desktop] [iPod Nano] [ATA RAID] [Fedora Bible] [Fedora Marketing] [Fedora Mentors] [Fedora Packaging] [Fedora SELinux] [Big List of Linux Books] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools] [Fedora Docs]