On Mon, 08 Sep 2008 18:00:19 -0500
René Berber <[EMAIL PROTECTED]> wrote:
> The idea of Cygwin is to be able to build with the same sources used
> under Linux. Of course there are problem areas, those are few, and the
> Cygwin maintainers/package porters should take care of them.
>
> My recommen
Tomasz Kojm wrote:
> On Thu, 04 Sep 2008 18:14:24 -0500
> René Berber <[EMAIL PROTECTED]> wrote:
>
>> Do we get back support for Cygwin?
>
> Hello René,
>
> we generally had not so good experience with Cygwin based builds of ClamAV
> over the past few years. The most common problem was differen
On Thu, 04 Sep 2008 18:14:24 -0500
René Berber <[EMAIL PROTECTED]> wrote:
> Do we get back support for Cygwin?
Hello René,
we generally had not so good experience with Cygwin based builds of ClamAV
over the past few years. The most common problem was different detection
results depending on the
Török Edwin wrote:
[snip]
>>> I built 0.94rc1 myself on cygwin, and confirmed this.
>>>
>>> For some reason lstat() works with 0.94 ... after we dropped cygwin support.
>>> Weird isn't it?
>>>
>> No, programming is deterministic, something changed in the code.
>>
>
> My guess is that one
On 2008-09-03 22:54, René Berber wrote:
> Török Edwin wrote:
>
> [snip]
>
>> Try the same with 0.94rc1, it doesn't work with relative paths, it shows:
>> ../test/clam.exe: lstat() failed. ERROR
>>
>
> Nope, clamdscan doesn't work at all :
>
> $ clamdscan -V
> ClamAV 0.94rc1/8145/Wed Sep 3
Török Edwin wrote:
[snip]
> Try the same with 0.94rc1, it doesn't work with relative paths, it shows:
> ../test/clam.exe: lstat() failed. ERROR
Nope, clamdscan doesn't work at all :
$ clamdscan -V
ClamAV 0.94rc1/8145/Wed Sep 3 01:00:57 2008
$ clamdscan clam.exe
clam.exe: lstat() failed. ERROR
On 2008-09-03 13:07, René Berber wrote:
> $ clamdscan ../test/clam.exe
> /home/rberber/Projects/clamav-0.94/test/../test/clam.exe:
> ClamAV-Test-File FOUND
>
> --- SCAN SUMMARY ---
> Infected files: 1
> Time: 0.109 sec (0 m 0 s)
>
> What is supposed to not do? Or you meant run it c
René Berber wrote:
> The problems with lstat() are well known, and it doesn't fail randomly.
Oops! sorry, lstat() doesn't have problems, I was thinking of lseek().
If a lstat() problem was reported the usual cause is (just like in
Unix/Linux):
1. Permission problems;
2. File system problems (i
Török Edwin wrote:
[snip]
> Have a look at bb #1139 for an example: lstat() failing for no apparent
> reason.
The problems with lstat() are well known, and it doesn't fail randomly.
But your point is that it affects clamav; I have never seen that
particular failure, and I test clamscan/clamdscan
On 2008-09-03 01:39, René Berber wrote:
> Brandon Perry wrote:
>
>
>> IIRC, the announcement said that POSIX breakage would happen if you tried to
>> compile 0.94 on cygwin...
>>
>
> If you mean this part :
>
> ** This version drops the special support for Cygwin. Our QA process showed
> **
Sarocet wrote:
> René Berber wrote:
>> "serious problems" ? Only problem is the test I mentioned, passing a
>> file descriptor is not supported under Cygwin as far as I know.
>>
> I have no cygwin experience, but Windows *does* allow passing file
> descriptors to child process. Not in the sam
René Berber wrote:
> "serious problems" ? Only problem is the test I mentioned, passing a
> file descriptor is not supported under Cygwin as far as I know.
>
I have no cygwin experience, but Windows *does* allow passing file
descriptors to child process. Not in the same way as unix, but I'd fi
Brandon Perry wrote:
> IIRC, the announcement said that POSIX breakage would happen if you tried to
> compile 0.94 on cygwin...
If you mean this part :
** This version drops the special support for Cygwin. Our QA process showed
** serious problems with ClamAV builds under Cygwin due to some low-
>From the announcement:
** This version drops the special support for Cygwin. Our QA process showed
** serious problems with ClamAV builds under Cygwin due to some low-level
** incompatibilities in the POSIX compatibility layer, resulting in
unreliable
** ClamAV behaviour.
On Tue, Sep 2, 2008 at
IIRC, the announcement said that POSIX breakage would happen if you tried to
compile 0.94 on cygwin...
On Tue, Sep 2, 2008 at 4:16 PM, René Berber <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Something changed in configure which results on a wrong setting for the
> existence of gethostbyname_r, it worked
Hi,
Something changed in configure which results on a wrong setting for the
existence of gethostbyname_r, it worked fine on 0.94rc1, now it doesn't
build unless using the following.
Simple solution: add '--disable-gethostbyname_r' to configure line.
I haven't found what changed and how the resul
16 matches
Mail list logo
