Summary: | clamav 0.88.1 won't run on a k6-3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rodrigo Severo <rodrigo> |
Component: | New packages | Assignee: | Antivirus Team <antivirus> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | gentoo-bugs, jakub, net-mail+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rodrigo Severo
2006-04-09 04:19:21 UTC
Don't use -march=k6-(whatever), it's known to be broken... I thought this could be a duplicate of Bug #24379. I tried -mtune=k6 and even tried without any -march, -mcpu or -mtune. I still get exactly the same error. What should I do? clamav-0.88.2 is in portage now, does that one work for you? Actually, scratch that - expat-1.95.8 still provides libexpat.so.0. But still, we're going to have to add <dev-libs/expat-2 to RDEPEND. (In reply to comment #4) > Actually, scratch that - expat-1.95.8 still provides libexpat.so.0. But still, > we're going to have to add <dev-libs/expat-2 to RDEPEND. > Disregard this comment please, wrong bug. (I hate the "move to next bug in list after comment" feature.) I got something like that and did a quick gdb run which left me with this: <snip> (gdb) run Starting program: /usr/sbin/clamd [symbols not found yada yada...] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 30471)] Program received signal SIGILL, Illegal instruction. [Switching to Thread 16384 (LWP 30471)] 0xb7f45ddb in __gmpz_mul_2exp () from /usr/lib/libgmp.so.3 </snip> So the problem seems to be in libgmp rather than in clamav. Will rebuild libgmp and get back to you. Well, a emerge --oneshot -av gmp fixed the problem for me. No more "Illegal instruction" when starting clamd. I now run clamd-0.88.2 on a VIA C7 processor. (In reply to comment #7) > emerge --oneshot -av gmp > > fixed the problem for me. No more "Illegal instruction" when starting clamd. You are right. It fixed the problem to me too. Sorry for the bogus bug report. |