You could also try './configure --enable-llvm=no' and compile with gcc 3. This will disable compiling the bytecode just-in-time compiler and use the bytecode interpreter instead.
On Fri, Jun 5, 2015 at 5:24 AM, Yuri Voinov <[email protected]> wrote: > Solaris 10 have shipped GCC 3. You need to use fresh GCC 4 from, for > example, http://opencsw.org repository. > > Or, you can build GCC 4 with shipped GCC 3 yourself. > > 05.06.15 13:42, MAYER Hans пишет: > > Dear all, >> >> Thanks for your feedback. >> In the meantime I could compile the latest version on Solaris 11.2 and >> run successfully. >> But not on Solaris 10. Here it compiles but does not run. >> The difference is the following >> On Solaris 11 I have gcc version 4.5.2 >> On Solaris 10 I have gcc version 3.4.3 >> Maybe this is a hint too. >> Generally I have to say I have a cookbook how to compile. This I follow >> using ClamAV since ages ( definitely more than 10 year ) >> But I will follow your ideas too. >> To answer Ged's question. Yes, it's an upgrade. >> >> Kind regards and 73 >> Hans >> >> >> -----Original Message----- >> From: Mark Fortescue [mailto:[email protected]] >> Sent: Thursday, May 07, 2015 12:04 PM >> To: MAYER Hans >> Cc: [email protected] >> Subject: Re: [clamav-users] daily.cvd: Malformed database >> >> Hi Hans, >> >> As you are using SPARC, it may be that someone has changed and/or >> incorrectly compiled something so that a variable is being read using the >> wrong byte alignment. ARM also has byte alignment constraints. >> >> Try running 'gdb --args /usr/local/sbin/clamd --debug' or use an >> equivalent dbx command. >> >> This should help track down the issue. >> >> On x86, there are only performance hits if the alignment is wrong so x86 >> developers rarely know that they have messed up the alignment because you >> don't even get a compiler warning. One reason why developers should use >> SPARC and ARM in addition to x86 for testing. >> >> Regards >> Mark. >> _______________________________________________ >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> > > _______________________________________________ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
