On 04/17/2012 09:15 AM, Jasowicz, Artur wrote:
Jasowicz,
You forced configure to skip a check which is there in order to avoid us
being flooded with "clamd crashed" bug reports where bzip2 really fails.
Configure obeys but it tells you that you are on your own. If you clamd
crashes, good luck.
Of course if you go through the trouble of tracing the crash and be sure
that it's not related to bzip2 (or other configure things you might have
messed around with) then you are still welcome to submit a bug report :)
Cheers,
-- aCaB
Fair enough, makes sense. Tho it would be nice if configure output said specifically why
it threw the warning. In my specific case it could have said "You're on your own
because you used disable-zlib-vcheck option". To someone experienced in building
clamav this may be obvious. To me - not so much.
Thanks aCaB!
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
Just a general comment on programming and error messages.
Too many times error messages are meaningless to almost anyone who is
not part of the build team. In this particular instance, that is not the
case, due to the big catch-all content of the message in combination
with the configure options. I agree with Jasowicz that it would be more
meaningful if it specifically pointed out that the warning message was
generated by the --disable-zlib-vcheck option and even better if it
included the results of the option check (if failing due to
incorrect/bad version). ./configure does this if the build actually
fails (e.g. missing a dependency).
I am a part-time C++, C#, VB, command line script programmer and fully
realize that the cost of programming will go up incrementally with the
programmatic handling of errors to give precise granular messages . But
in response to that argument I generally respond with "If you are
bothering to capture an error, might as well make the error message mean
something. If not, just let it crash without any message rather than
displaying meaningless messages". If a log is being generated, putting
the details in the log, stating the log contains the details AND giving
the name and location of the log is a good SOP starting point. For
example one of my pet peeves is the following error message "An error
has occurred". I have to work in the MS Windows world and sadly this is
a typical error message in the Wonderful World of Windows (and I used to
think WWW stood for something else.....). The programmer should not have
bothered displaying a message if that is all they are going to say about
it. It does not tell the user anything useful to try and solve the problem.
Just my 2ยข
--
Jim Preston
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
