Mailing List Archive

[clamav-users] Problems compiling 0.102.4 on OLD system
Hi, I have an old system I'm compiling.

I have 0.102.3 working on it.

Here's the config line:

CC=/usr/local/gcc4.2.4/bin/gcc ./configure --prefix=/usr/local/clamav
--with-user=defang --with-group=defang --enable-llvm=no
--with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre2
--with-zlib=/usr/local/zlib --with-xml=/usr/local/libxml2
--disable-clamonacc --disable-unrar

I believe the relevant error info is below if anyone has advice.  It's
an old system and just trying to keep it limping a few more weeks.

make[2]: Entering directory `/usr/src/clamav-0.102.4/libfreshclam'
  CC       output.lo
  CC       optparser.lo
  CC       getopt.lo
  CC       misc.lo
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/output.c:56:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/optparser.c:48:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       cdiff.lo
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/misc.c:48:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       tar.lo
  CC       cert_util.lo
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/cdiff.c:40:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       libfreshclam.lo
In file included from ../shared/cert_util.c:30:
../shared/cert_util.h:121:7: warning: no newline at end of file
  CC       libfreshclam_internal.lo
  CC       dns.lo
In file included from libfreshclam.c:61:
../shared/cert_util.h:121:7: warning: no newline at end of file
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from libfreshclam.c:65:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       cert_util_linux.lo
In file included from libfreshclam_internal.c:85:
../shared/cert_util.h:121:7: warning: no newline at end of file
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from libfreshclam_internal.c:88:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
In file included from ../shared/linux/cert_util_linux.c:32:
../shared/cert_util.h:121:7: warning: no newline at end of file
  OBJCLD   libfreshclam.la
make[2]: Leaving directory `/usr/src/clamav-0.102.4/libfreshclam'
Making all in clamscan
make[2]: Entering directory `/usr/src/clamav-0.102.4/clamscan'
  CC       output.o
  CC       optparser.o
  CC       getopt.o
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/optparser.c:48:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       actions.o
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/actions.c:51:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/output.c:56:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       misc.o
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from ../shared/misc.c:48:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CC       clamscan.o
  CC       manager.o
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from clamscan.c:42:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
In file included from ../libclamav/execs.h:28,
                 from ../libclamav/matcher.h:30,
                 from ../libclamav/others.h:22,
                 from manager.c:61:
../libclamav/pe_structs.h:159:7: warning: no newline at end of file
  CCLD     clamscan
actions.o: In function `traverse_to':
../shared/actions.c:328: undefined reference to `openat'
actions.o: In function `traverse_unlink':
../shared/actions.c:568: undefined reference to `unlinkat'
actions.o: In function `action_move':
../shared/actions.c:455: undefined reference to `renameat'
collect2: ld returned 1 exit status
make[2]: *** [clamscan] Error 1
make[2]: Leaving directory `/usr/src/clamav-0.102.4/clamscan'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/clamav-0.102.4'

make: *** [all] Error 2

Regards,

KAM


_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problems compiling 0.102.4 on OLD system [ In reply to ]
On 2020-07-16 17:22, Kevin A. McGrail via clamav-users wrote:
> Hi, I have an old system I'm compiling.
>
> I have 0.102.3 working on it.
>
> Here's the config line:
>
> ...
>   CCLD     clamscan
> actions.o: In function `traverse_to':
> ../shared/actions.c:328: undefined reference to `openat'
> actions.o: In function `traverse_unlink':
> ../shared/actions.c:568: undefined reference to `unlinkat'
> actions.o: In function `action_move':
> ../shared/actions.c:455: undefined reference to `renameat'

This is from the fix for CVE-2020-3350. The "at" system calls are
POSIX.1-2008 and are more or less necessary to handle links safely.
ClamAV have gone out of their way to provide a compatibility function on
Windows, though, so maybe you're not totally out of luck.

Micah: openat() only provides "one level of safety" in that when opening
/foo/bar/baz, it ensures that "baz" is where you think it is. You may
want to investigate whether or not an attacker can replace "bar" by a
symlink in that situation. Other programs address this same problem by
running openat() on /, /foo, /foo/bar, and then /foo/bar/baz all in
succession to ensure that everything is trustworthy (the root is assumed
to be sacred). See http://michael.orlitzky.com/cves/cve-2018-6954.xhtml.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problems compiling 0.102.4 on OLD system [ In reply to ]
On 2020-07-16 19:10, Michael Orlitzky via clamav-users wrote:
>
> Micah: openat() only provides "one level of safety" in that when opening
> /foo/bar/baz, it ensures that "baz" is where you think it is. You may
> want to investigate whether or not an attacker can replace "bar" by a
> symlink in that situation.

False alarm, I guess this is the problem that was reported because the
fix already traverses the path from the root upwards.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problems compiling 0.102.4 on OLD system [ In reply to ]
Hi Kevin,

It looks like you will have to create/enable private versions of the
openat(), ranameat() and unlinkat() functions.

These can be simulated using regular C functions open(), unlink(),
rename(), stat() and readdir().

You will need to get manual pages for openat(), ranameat() and
unlinkat() functions to understand the differences with the regular
versions.

Parsing paths is not always the easiest thing to do but the learning
curve can be useful.

Regards
Mark.

On 16/07/2020 22:22, Kevin A. McGrail via clamav-users wrote:
> Hi, I have an old system I'm compiling.
>
> I have 0.102.3 working on it.
>
> Here's the config line:
>
> CC=/usr/local/gcc4.2.4/bin/gcc ./configure --prefix=/usr/local/clamav
> --with-user=defang --with-group=defang --enable-llvm=no
> --with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre2
> --with-zlib=/usr/local/zlib --with-xml=/usr/local/libxml2
> --disable-clamonacc --disable-unrar
>
> I believe the relevant error info is below if anyone has advice.  It's
> an old system and just trying to keep it limping a few more weeks.
>
> make[2]: Entering directory `/usr/src/clamav-0.102.4/libfreshclam'
>   CC       output.lo
>   CC       optparser.lo
>   CC       getopt.lo
>   CC       misc.lo
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/output.c:56:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/optparser.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       cdiff.lo
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/misc.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       tar.lo
>   CC       cert_util.lo
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/cdiff.c:40:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       libfreshclam.lo
> In file included from ../shared/cert_util.c:30:
> ../shared/cert_util.h:121:7: warning: no newline at end of file
>   CC       libfreshclam_internal.lo
>   CC       dns.lo
> In file included from libfreshclam.c:61:
> ../shared/cert_util.h:121:7: warning: no newline at end of file
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from libfreshclam.c:65:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       cert_util_linux.lo
> In file included from libfreshclam_internal.c:85:
> ../shared/cert_util.h:121:7: warning: no newline at end of file
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from libfreshclam_internal.c:88:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
> In file included from ../shared/linux/cert_util_linux.c:32:
> ../shared/cert_util.h:121:7: warning: no newline at end of file
>   OBJCLD   libfreshclam.la
> make[2]: Leaving directory `/usr/src/clamav-0.102.4/libfreshclam'
> Making all in clamscan
> make[2]: Entering directory `/usr/src/clamav-0.102.4/clamscan'
>   CC       output.o
>   CC       optparser.o
>   CC       getopt.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/optparser.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       actions.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/actions.c:51:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/output.c:56:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       misc.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/misc.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       clamscan.o
>   CC       manager.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from clamscan.c:42:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from manager.c:61:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CCLD     clamscan
> actions.o: In function `traverse_to':
> ../shared/actions.c:328: undefined reference to `openat'
> actions.o: In function `traverse_unlink':
> ../shared/actions.c:568: undefined reference to `unlinkat'
> actions.o: In function `action_move':
> ../shared/actions.c:455: undefined reference to `renameat'
> collect2: ld returned 1 exit status
> make[2]: *** [clamscan] Error 1
> make[2]: Leaving directory `/usr/src/clamav-0.102.4/clamscan'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/clamav-0.102.4'
>
> make: *** [all] Error 2
>
> Regards,
>
> KAM
>
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problems compiling 0.102.4 on OLD system [ In reply to ]
Achtung, falscher Empfänger

-----Ursprüngliche Nachricht-----
Von: clamav-users <clamav-users-bounces@lists.clamav.net> Im Auftrag von Mark Fortescue via clamav-users
Gesendet: Freitag, 17. Juli 2020 12:46
An: clamav-users@lists.clamav.net
Cc: Mark Fortescue <mark.lists@thurning-instruments.co.uk>
Betreff: Re: [clamav-users] Problems compiling 0.102.4 on OLD system

Hi Kevin,

It looks like you will have to create/enable private versions of the openat(), ranameat() and unlinkat() functions.

These can be simulated using regular C functions open(), unlink(), rename(), stat() and readdir().

You will need to get manual pages for openat(), ranameat() and
unlinkat() functions to understand the differences with the regular versions.

Parsing paths is not always the easiest thing to do but the learning curve can be useful.

Regards
Mark.

On 16/07/2020 22:22, Kevin A. McGrail via clamav-users wrote:
> Hi, I have an old system I'm compiling.
>
> I have 0.102.3 working on it.
>
> Here's the config line:
>
> CC=/usr/local/gcc4.2.4/bin/gcc ./configure --prefix=/usr/local/clamav
> --with-user=defang --with-group=defang --enable-llvm=no
> --with-openssl=/usr/local/ssl --with-pcre=/usr/local/pcre2
> --with-zlib=/usr/local/zlib --with-xml=/usr/local/libxml2
> --disable-clamonacc --disable-unrar
>
> I believe the relevant error info is below if anyone has advice.  It's
> an old system and just trying to keep it limping a few more weeks.
>
> make[2]: Entering directory `/usr/src/clamav-0.102.4/libfreshclam'
>   CC       output.lo
>   CC       optparser.lo
>   CC       getopt.lo
>   CC       misc.lo
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/output.c:56:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file In
> file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/optparser.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       cdiff.lo
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/misc.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       tar.lo
>   CC       cert_util.lo
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/cdiff.c:40:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       libfreshclam.lo
> In file included from ../shared/cert_util.c:30:
> ../shared/cert_util.h:121:7: warning: no newline at end of file
>   CC       libfreshclam_internal.lo
>   CC       dns.lo
> In file included from libfreshclam.c:61:
> ../shared/cert_util.h:121:7: warning: no newline at end of file In
> file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from libfreshclam.c:65:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       cert_util_linux.lo
> In file included from libfreshclam_internal.c:85:
> ../shared/cert_util.h:121:7: warning: no newline at end of file In
> file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from libfreshclam_internal.c:88:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file In
> file included from ../shared/linux/cert_util_linux.c:32:
> ../shared/cert_util.h:121:7: warning: no newline at end of file
>   OBJCLD   libfreshclam.la
> make[2]: Leaving directory `/usr/src/clamav-0.102.4/libfreshclam'
> Making all in clamscan
> make[2]: Entering directory `/usr/src/clamav-0.102.4/clamscan'
>   CC       output.o
>   CC       optparser.o
>   CC       getopt.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/optparser.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       actions.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/actions.c:51:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file In
> file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/output.c:56:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       misc.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from ../shared/misc.c:48:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CC       clamscan.o
>   CC       manager.o
> In file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from clamscan.c:42:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file In
> file included from ../libclamav/execs.h:28,
>                  from ../libclamav/matcher.h:30,
>                  from ../libclamav/others.h:22,
>                  from manager.c:61:
> ../libclamav/pe_structs.h:159:7: warning: no newline at end of file
>   CCLD     clamscan
> actions.o: In function `traverse_to':
> ../shared/actions.c:328: undefined reference to `openat'
> actions.o: In function `traverse_unlink':
> ../shared/actions.c:568: undefined reference to `unlinkat'
> actions.o: In function `action_move':
> ../shared/actions.c:455: undefined reference to `renameat'
> collect2: ld returned 1 exit status
> make[2]: *** [clamscan] Error 1
> make[2]: Leaving directory `/usr/src/clamav-0.102.4/clamscan'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/clamav-0.102.4'
>
> make: *** [all] Error 2
>
> Regards,
>
> KAM
>
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] Problems compiling 0.102.4 on OLD system [ In reply to ]
No worries Michael! Yes we're doing traversal from root to avoid that issue. :-)

Kevin: Any chance you can upgrade those old systems? We try to support roughly the last 2 LTS releases for major distros / operating systems but don't have time to go out of our way to maintain compatibility with really old systems.

If you or someone else wants to craft a patch to maintain compatibility with those older systems and can submit a PR on Github, we'd be happy to test it & integrate it -- provided it doesn't break other things.

-Micah

?On 7/16/20, 4:24 PM, "clamav-users on behalf of Michael Orlitzky via clamav-users" <clamav-users-bounces@lists.clamav.net on behalf of clamav-users@lists.clamav.net> wrote:

On 2020-07-16 19:10, Michael Orlitzky via clamav-users wrote:
>
> Micah: openat() only provides "one level of safety" in that when opening
> /foo/bar/baz, it ensures that "baz" is where you think it is. You may
> want to investigate whether or not an attacker can replace "bar" by a
> symlink in that situation.

False alarm, I guess this is the problem that was reported because the
fix already traverses the path from the root upwards.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml


_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] [External] Re: Problems compiling 0.102.4 on OLD system [ In reply to ]
On 7/17/2020 3:38 PM, Micah Snyder (micasnyd) via clamav-users wrote:
> Kevin: Any chance you can upgrade those old systems? We try to support roughly the last 2 LTS releases for major distros / operating systems but don't have time to go out of our way to maintain compatibility with really old systems.
>
> If you or someone else wants to craft a patch to maintain compatibility with those older systems and can submit a PR on Github, we'd be happy to test it & integrate it -- provided it doesn't break other things.

Hi Micah, do you happen to know where the upgrade is needed?  Is it
glibc, a version of gcc, etc?  That will help us dig into it more for a
patch for others.  We are DEFINITELY working on the upgrade.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] [External] Re: Problems compiling 0.102.4 on OLD system [ In reply to ]
Hi Kevin,

It looks like the openat and unlinkat system calls were added to Linux in kernel 2.6.16; library support was added to glibc in version 2.4.

-Micah

?On 7/30/20, 11:02 AM, "clamav-users on behalf of Kevin A. McGrail via clamav-users" <clamav-users-bounces@lists.clamav.net on behalf of clamav-users@lists.clamav.net> wrote:

On 7/17/2020 3:38 PM, Micah Snyder (micasnyd) via clamav-users wrote:
> Kevin: Any chance you can upgrade those old systems? We try to support roughly the last 2 LTS releases for major distros / operating systems but don't have time to go out of our way to maintain compatibility with really old systems.
>
> If you or someone else wants to craft a patch to maintain compatibility with those older systems and can submit a PR on Github, we'd be happy to test it & integrate it -- provided it doesn't break other things.

Hi Micah, do you happen to know where the upgrade is needed? Is it
glibc, a version of gcc, etc? That will help us dig into it more for a
patch for others. We are DEFINITELY working on the upgrade.

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml


_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] [External] Re: Problems compiling 0.102.4 on OLD system [ In reply to ]
On 7/30/2020 8:17 PM, Micah Snyder (micasnyd) wrote:
> It looks like the openat and unlinkat system calls were added to Linux in kernel 2.6.16; library support was added to glibc in version 2.4.

Hi Micah, thank you for that guidance.  It looks like this is too high a
hill to fight.  Better to upgrade the system.

However, we believe we have found a work around working more with
clamdscan with 0.102.3 going to a modern system with 0.102.4.  That will
buy us a few weeks as we are modernize things!

Regards,

KAM



_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml