David Wu wrote:
On Wed, 24 Nov 2004, [ISO-8859-2] Bogusław Brandys wrote:


David Wu wrote:

On Tue, 23 Nov 2004, aCaB wrote:



On 11/23/04 09:20, David Wu wrote:


I am not able to have clamd (and clamav-milter) built on BSD/OS 4.2 from
0.8 source, although everything else built and run without problem (after
fiddling with integer type define).

Found in clamd/Makefile the following with the obvious meaning that clamd
not be built.

BUILD_CLAMD_FALSE =
BUILD_CLAMD_TRUE = #

Would like to know what configure discovered to decide not to build clamd.

From configure:

if test "$have_pthreads" = "yes"; then
 BUILD_CLAMD_TRUE=
 BUILD_CLAMD_FALSE='#'
else
 BUILD_CLAMD_TRUE='#'
 BUILD_CLAMD_FALSE=
fi


Thanks for pointing me in the direction that I should be looking.  This is
what I found from the configure output :-

configure:10025: checking pthread.h usability
configure:10037: gcc -c -g -O2 -m486 -I/home/dyw/clamav-0.80/include
conftest.c >&5
configure:10043: $? = 0
configure:10046: test -z                         || test ! -s conftest.err
configure:10049: $? = 0
configure:10052: test -s conftest.o
configure:10055: $? = 0
configure:10065: result: yes
configure:10069: checking pthread.h presence
configure:10079: gcc -E -m486 -I/home/dyw/clamav-0.80/include conftest.c
configure:10085: $? = 0
configure:10105: result: yes
configure:10140: checking for pthread.h
configure:10147: result: yes

So the system does have pthread support, but as the target_os is bsdi4.2,
configure returns the following due to the case switch bsd*)

configure:11575: result: Unknown BSD detected. Disabling thread support.

I tried to modify configure to include the switch bsdi4*) and copying the
program logic from freebsd*)    Although I got rid of the above configure
output, it is still

BUILD_CLAMD_FALSE =
BUILD_CLAMD_TRUE = #

I will be fiddling a bit more with configure and sure would like more
useful pointers.

You must change configure.in and run autoheader,aclocal,autoconf and eventually automake but this is rather not needed.
I'm sure that Tomasz can explain this with details.


Did all that but the end result is the same.   I did try to change
config.status and then ran that.   clamd did compile but I saw a few lines
of compiler output (probably from the compiling of freshclam) with
-DCL_NOTHREADS in them, so I do not dare use the executables coming out as
a result of my fudge.   I am running out of ideas.   Anyone?


Best Regards David WU

_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Try to change (temporary) bsd*) to something like bsdxxx)or else , maybe after processing Your bsdi4*), bsd*) (which i suppose is later in configure) also MATCH (shoudn't)?
Anyway ,did You try make distclean to clean all before processing with make ?


As I say Tomasz Kojm is maintainer of configure script,and could give You some light on what is going on .

Regards
Boguslaw Brandys
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users

Reply via email to