On 4/7/2010 2:35 PM, Clayton Keller wrote:
On 4/7/2010 2:33 PM, Török Edwin wrote:
On 04/07/2010 09:34 PM, Clayton Keller wrote:
On 4/7/2010 12:30 PM, Török Edwin wrote:
On 04/07/2010 08:17 PM, Clayton Keller wrote:
On 4/7/2010 11:26 AM, Török Edwin wrote:
On 04/07/2010 07:24 PM, Clayton Keller wrote:
On 4/7/2010 11:12 AM, Török Edwin wrote:
On 04/07/2010 07:08 PM, Clayton Keller wrote:
I am testing out the ./configure and make on an older RedHat 7.3
Server.
I am seeing the following in the ./configure output:
...
checking for supported C++ compiler version... configure:
error: C++
compiler too old (2.96)
You are aware that 2.96 is NOT a production compiler, but a
development
version, right?
http://gcc.gnu.org/gcc-2.96.html
"We would like to point out that GCC 2.96 is not a formal GCC
release
nor will there ever be such a release. Rather, GCC 2.96 has been
the
code- name for our development branch that will eventually
become GCC
3.0."
Oddly enough that is the compiler they shipped with this release,
as far
as I am aware of.
...
While I know this is a much out dated OS, and with that an old
compiler,
the source did seem to compile without error for me during the
make
process.
Is there anything I may need to be aware of that could come up
because
of this warning and version of the compiler?
It will disable the compilation of the JIT, and you'll get an
interpreter instead for ClamAV's bytecode.
Does 'make check' pass?
Test output:
SKIP: check_clamav
PASS: check_freshclam.sh
PASS: check_sigtool.sh
SKIP: check_unit_vg.sh
PASS: check1_clamscan.sh
PASS: check2_clamd.sh
PASS: check3_clamd.sh
PASS: check4_clamd.sh
SKIP: check5_clamd_vg.sh
SKIP: check6_clamd_vg.sh
SKIP: check7_clamd_hg.sh
SKIP: check8_clamd_hg.sh
======================
All 6 tests passed
(6 tests were not run)
======================
I don't see any other errors thrown during 'make check'. All she be
OK,
even with the skips?
Perhaps. If you want to be sure download libcheck from here:
http://sourceforge.net/projects/check/files/check/0.9.8/check-0.9.8.tar.gz/download
Then reconfigure ClamAV (with --enable-check recommended), and rerun
make check.
I receive a failure on the check_clamav test.
Here is the output for the test in the log:
FAIL: check_clamav (exit: 1)
============================
Running suite(s): cl_api
cli
jsnorm
str
regex
disasm
unique
matchers
htmlnorm
bytecode
99%: Checks: 287, Failures: 2, Errors: 0
check_bytecode.c:107:F:arithmetic:test_inflate_jit:0: Invalid return
value from bytecode run, expected: beef, have: dead2
check_bytecode.c:107:F:arithmetic:test_inflate_int:0: Invalid return
value from bytecode run, expected: beef, have: dead2
This is probably due to an old version of zlib.
What does 'grep inflate unit_tests/test-stderr.log' show?
Here you go:
# grep inflate unit_tests/test-stderr.log
LibClamAV debug: bytecode api: inflateinit2: zlib stream error!
LibClamAV debug: bytecode api: inflateinit2: zlib stream error!
You should probably upgrade zlib.
That's what I was thinking as well. Thanks for the assistance.
What could possibly occur if I installed with the current zlib version
as-is?
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
