T.O,
Sorry, didn't quite follow your question:
Is there a bad place to reference with the make command?
Scanning is taking 25% longer than with the previous version? What sort of
files are you scanning? That sounds like a very broad metric, and I'm not sure
what to do with that information.
Hi, Micah.
No, I didn't attach anything.
Thank you for your advice.
As your advice, I tried.
As a result, the warning messages is no longer outputed.
However, link errors are the problem.
To resolve this, it was necessary to create "libclammspack.a" in advance.
Is there a bad place to reference
Did you try to attach something? Attachments don't work with the mailing list.
If needed, you can add attachments to comments on the related bugzilla ticket
(https://bugzilla.clamav.net/show_bug.cgi?id=12089)
-Micah
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Apr 25, 2018,
Thank you for your reply.
Try this. The results are reported after the test.
T.O
On Fri, 20 Apr 2018 14:55:00 +
"Micah Snyder (micasnyd)" wrote:
> Sorry for the lag time getting back to you Tsutomu.
>
> That is a very good question.
>
> At a minimum, it looks as though the function defini
Sorry for the lag time getting back to you Tsutomu.
That is a very good question.
At a minimum, it looks as though the function definition should be
static inline int64_t cli_readint64(const void *buff)
instead of
static inline int32_t cli_readint64(const void *buff)
That said, it also ap
Thank you for your advice.
I tried.
# export OBJECT_MODE="64"
# export CFLAGS="-maix64"
# export LDFLAGS="-maix64 -Wl,-bbigtoc"
# ./configure
# make
However, this time it was another error.
---
# make
(snip)
CC libclamav_internal_utils_la-regfree.lo
In file included
It will be tough for us to fix this, because I don't have an AIX machine to
test with.
A quick Google search for "conflicting types for 'fsync_range64'" shows a bunch
fo people with similar errors compiling other software on AIX. The 2nd link
down had a similar issue and appear to have to work
Thank you for your reply.
It certainly seems to be the same thing.
Is this a bug?
By the way, I tried to configure it with "CFLAGS =-maix64" And it was an error
the following.
-
# make
make all-recursive
Making all in libltdl
cp ./argz_.h argz.h-t
mv argz.h-t argz
It looks like Dwight is experiencing the same issue with AIX 5.3:
https://bugzilla.clamav.net/show_bug.cgi?id=12089
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Apr 12, 2018, at 8:49 AM, Tsutomu Oyamada
mailto:oyam...@promark-inc.com>> wrote:
I am experimenting with compiling
I am experimenting with compiling a new version of ClamAV 0.100 on Aix
6.1.
The result of configure is as follows:
--
# ./configure --prefix=/usr/lib/clamav --exec-prefix=/usr/lib/clamav
--bindir=/usr/lib/clamav --sbindir=/usr/lib/clamav
--sysconfdir=/etc/clamav --libdir=/usr/lib/clamav --
10 matches
Mail list logo