[Clamav-users] RE: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-28 Thread Kaplan, Andrew H.
To the people who helped me in getting ClamAV upgraded on my system, listed below are the modifications that needed to be done to get version 0.88 to install on the server in question. I appreciate the help that was given, and hopefully this information will be useful to anyone who may be

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-28 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] manager.c Modify the lines that read: switch(h_errno) To read the following: switch(errno) It's not the same functionality. You bypassed the problem but the result will not work as intended. - -- René

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-10 Thread Kaplan, Andrew H.
Hi there - One of my colleagues, who is a first-rate programmer, was able to compile a build of version 0.88 on the HP-UX box in question. He stated in his e-mail that he needed to modify the code in order for it to work due to some 'issues' with this version an the OS. I've asked him to

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread Kaplan, Andrew H.
OK Andrew, you'll have to repeat the build with: CFLAGS=-D_XOPEN_SOURCE ./configure make I ran the above command using the following syntax: CFLAGS=-D_XOPEN_SOURCE ./configure As has happened before, the configure script appeared to complete without difficulty. The

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: OK Andrew, you'll have to repeat the build with: CFLAGS=-D_XOPEN_SOURCE ./configure My mistake here, see below. make I ran the above command using the following syntax: CFLAGS=-D_XOPEN_SOURCE ./configure

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread Kaplan, Andrew H.
The configure line should be: CFLAGS=-D_XOPEN_SOURCE_EXTENDED ./configure (there is an underscore before EXTENDED). That should work, but you are not finished, you'll have to check how the shared libraries are set up in the resulting executables. But let's do one thing at a time,

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] CFLAGS=-D_XOPEN+SOURCE_EXTENDED: Command not found. My mistake, I'm using sh/bash syntax while you are using csh. When I reentered the above command using the syntax: ./configure

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread Kaplan, Andrew H.
OK, this is normal, we are missing some libraries in the link command. Easy to correct: ./configure CFLAGS=-D_XOPEN+SOURCE_EXTENDED LDFLAGS=-lsocket -lnls When I ran the above command, the configure script failed and displayed the following message: checking for C compiler

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: ./configure CFLAGS=-D_XOPEN+SOURCE_EXTENDED LDFLAGS=-lsocket -lnls - --^ Oops! The error here is obvious, did I put that? yes, dumb copy/paste. Sorry. Correction: ./configure

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 René Berber wrote: Kaplan, Andrew H. wrote: ./configure CFLAGS=-D_XOPEN+SOURCE_EXTENDED LDFLAGS=-lsocket -lnls --^ Oops! The error here is obvious, did I put that? yes, dumb copy/paste. Sorry.

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: I saw the typo and automatically corrected it when I entered the command. The problems that I mentioned in the previous e-mail were output from the correct syntax. Yes, I saw that in the log. Anyway the LDFLAGS need a

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread Kaplan, Andrew H.
Anyway the LDFLAGS need a correction, just delete the -lsocket part, the log shows that the socket library doesn't exist. I entered the configure command without -lsocket part, and the script failed with the same error mentioned in the previous e-mail. Here is the latest version of the

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: Anyway the LDFLAGS need a correction, just delete the -lsocket part, the log shows that the socket library doesn't exist. I entered the configure command without -lsocket part, and the script failed with the same error

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread Kaplan, Andrew H.
Here is an excerpt from the ntohl man page: SYNOPSIS: #include netinet/in.h _XOPEN_SOURCE_EXTENDED only #include arpa/inet.h unsigned long htonl (unsigned long hostlong); unsigned short htons (unsigned short hostshort);

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: Here is an excerpt from the ntohl man page: SYNOPSIS: #include netinet/in.h _XOPEN_SOURCE_EXTENDED only #include arpa/inet.h unsigned long htonl (unsigned long

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-09 Thread Jeff Donsbach
On 2/9/06, Kaplan, Andrew H. [EMAIL PROTECTED] wrote: Here is an excerpt from the ntohl man page: SYNOPSIS: #include netinet/in.h _XOPEN_SOURCE_EXTENDED only #include arpa/inet.h Since we're building with -D_XOPEN_SOURCE_EXTENDED now (specified

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
There are 3 tests inside configure that use netdb.h and h_errno, they seem to be testing to see what variant of gethostbyname_r does the system have. You should have the result in config.log, look for lines that say checking for gethostbyname_r and everything below that should be

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] I checked the config.log file for the text you had mentioned: and the line reads configure:13334: result: yes, and it takes 5 arguments Do you need me to send you a copy of the log file? No, not really. OK,

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
OK, that means that configure is able to use h_errno and related stuff, which is good news. Now look in the log about 8 lines above (and just below the checking for gethostbyname_r), how was the test compiled? I have gcc -c -g -O2 conftest.c 5, does your log show more parameters to

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] The line in question reads as follows:configure:13162: gcc -c -g 02 -I/usr/local/include conftest.c 5 The following text appears immediately after: cc1: warning: changing search order for system directory

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
I suggest to start with a minimal set of well defined environment variables (PATH, CC, CFLAGS, LDFLAGS, nothing else), run configure, see any complaints there, add the required parameters to configure (the defaults install everything under /usr/local, I use --sysconfdir=/etc --enable-id-

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] I defined the environment variables to use by entering the following at the command prompt: setenv CFLAGS -I/usr/tools/gcc3/include setenv LDFLAGS -L/usr/tools/gcc3/lib setenv CPPFLAGS

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Jeff Donsbach
Andrew, Let's step back for a minute once again. On your 10.20, system, go and look at /usr/include/netdb.h . Find the section where it defines h_errno which is a macro that will be defined to either a function call or an external variable depending on if the macro _REENTRANT is defined at

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
Let's step back for a minute once again. On your 10.20, system, go and look at /usr/include/netdb.h . Find the section where it defines h_errno which is a macro that will be defined to either a function call or an external variable depending on if the macro _REENTRANT is defined at compile

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
setenv CFLAGS -I/usr/tools/gcc3/include setenv LDFLAGS -L/usr/tools/gcc3/lib setenv CPPFLAGS -L/usr/tools/gcc3/include This last one is wrong, cpp is the pre-processor it doesn't have anything to do with libraries so -L is a no-op. I can try running the configure and make script again

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Jeff Donsbach
On 2/8/06, Kaplan, Andrew H. [EMAIL PROTECTED] wrote: The following text in the netdb.h file is what references h_errno: /* * Error return codes from gethostbyname() and gethostbyaddr() * (left in extern int h_errno). #ifdef _XOPEN_SOURCE EXTENDED extern int h_errno;

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
Try adding -D_XOPEN_SOURCE EXTENDED to your CFLAGS. I entered the setenv command three times using the following syntax: setenv CFLAGS -I/usr/tools/gcc3/include setenv LDFLAGS -L/usr/tools/gcc3/lib setenv CFLAGS -D_XOPEN_SOURCE EXTENDED After that, I ran the

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] The gcc line before the error message is the following: gcc -DHAVE_CONFIG_H -DCL_NOTHREADS -I. -I. -I.. -I.. -I../shared -I../libclamav -L/usr/tools/gcc3/include -I/usr/local/include

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
Try unsetting all variables except PATH (i.e. no CLFAGS, no LDFLAGS), does configure work as before? does make work? Which PATH statement(s) are you referring to? ___ http://lurker.clamav.net/list/clamav-users.html

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: Try unsetting all variables except PATH (i.e. no CLFAGS, no LDFLAGS), does configure work as before? does make work? Which PATH statement(s) are you referring to? The one called PATH (as in `echo $PATH` for bash). The

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Kaplan, Andrew H.
Try unsetting all variables except PATH (i.e. no CLFAGS, no LDFLAGS), does configure work as before? does make work? I ran the unsetenv command on the CFLAGS and LDFLAGS variables. After that, I ran configure and make. Configure worked as before, but make still gives an Error 1 message.

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Dale Walsh
On Feb 8, 2006, at 14:42 , Kaplan, Andrew H. wrote: Try adding -D_XOPEN_SOURCE EXTENDED to your CFLAGS. I entered the setenv command three times using the following syntax: setenv CFLAGS -I/usr/tools/gcc3/include setenv LDFLAGS -L/usr/tools/gcc3/lib setenv CFLAGS

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: I ran the unsetenv command on the CFLAGS and LDFLAGS variables. After that, I ran configure and make. Configure worked as before, but make still gives an Error 1 message. You keep sending just bits and pieces of the

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Jeff Donsbach
On 2/8/06, René Berber [EMAIL PROTECTED] wrote: You can use -D_XOPEN_SOURCE but if configure didn't need that I don't see the point. That assumes configure is working correctly with regards to this on hp-ux 10.20. I wouldn't necessarily make that assumption. I see checks in configure for

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Donsbach wrote: You can use -D_XOPEN_SOURCE but if configure didn't need that I don't see the point. That assumes configure is working correctly with regards to this on hp-ux 10.20. I wouldn't necessarily make that assumption. I see checks

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Donsbach wrote: Yes, but not the same as how ClamAV uses it. In this case, h_error is a local variable, so of course the symbol resolves correctly. In real code such as ClamAV, h_error is defined in system header files as an external

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread Jeff Donsbach
On 2/8/06, René Berber [EMAIL PROTECTED] wrote: Yes, I see you are correct. freshclam/manager.c depends on the external value, which is not being defined in HP-UX unless, following your sugestion CFLAGS='-D_XOPEN_SOURCE' is used. OK Andrew, you'll have to repeat the build with:

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-08 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Donsbach wrote: CFLAGS=-D_XOPEN_SOURCE ./configure make I believe the value should be -D_XOPEN_SOURCE_EXTENDED, which was the standard way to invoke UNIX95 namespace compatibility/compliance. Note here that we are talking about an OS

[Clamav-users] RE: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Kaplan, Andrew H.
Hi there -- I mounted an NFS directory that has a newer version of gcc/ I then mounted tthe following lines to my .cshrc file: setenv GCC_PATH /usr/tools/gcc3 setenv PATH ${GCC_PATH}/bin:${PATH} setenv LD_LIBRARY_PATH ${GCC_PATH}/lib alias gcc /usr/tools/gcc3/ After the

Re: [Clamav-users] RE: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Jeff Donsbach
Unless you know what version of HP-UX that version of gcc 3 was built on, I wouldn't trust that it will run on your 10.20 machine. If the compiler you are trying to use was built on 11.0 or later, don't count on it working at all. You know how old HP-UX 10.20 is, right? HP has not supported 10.20

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: I mounted an NFS directory that has a newer version of gcc/ I then mounted tthe following lines to my .cshrc file: setenv GCC_PATH /usr/tools/gcc3 setenv PATH ${GCC_PATH}/bin:${PATH} This far is OK. setenv

Re: [Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Jeff Donsbach
On 2/7/06, René Berber [EMAIL PROTECTED] wrote: But first correct the part with LD_LIBRARY_PATH above. René is right. I missed that. On 10.20, LD_LIBRARY_PATH is not what you want. SHLIB_PATH is the environment variable. That still assumes the binary was linked to allow searches for the shared

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Kaplan, Andrew H.
I made the changes you had suggested to the .cshrc file. setenv LD_LIBRARY_PATH ${GCC_PATH}/lib This won't work, get rid of it. I commented out that line. alias gcc /usr/tools/gcc3/ What's this for? Don't use this, first check if changing your path gives you the new gcc:

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: I made the changes you had suggested to the .cshrc file. [snip] I commented out that line as well, ran source .cshrc and then ran which gcc and gcc --version. The which gcc command gave me the following output: gcc:

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Kaplan, Andrew H.
Perhaps setting the header path explicitly, as in: CFLAGS=-I/usr/include ./configure ... I don't know into which file the CFLAGS line goes, or if it gets executed from the command prompt. When I ran the make script as a regular user, I got an error 1 message due to a permission denied

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: Perhaps setting the header path explicitly, as in: CFLAGS=-I/usr/include ./configure ... I don't know into which file the CFLAGS line goes, or if it gets executed from the command prompt. No file, the above is the

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Kaplan, Andrew H.
No file, the above is the command typed on a terminal to configure the package. It may be different under csh, but you can use 'setenv CFLAGS -I/usr/include' before running ./configure I ran the command setenv CFLAGS -I/usr/include as a regular user and it seemed to accept the command.

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: [snip] I removed the SHLIB_PATH command from the .cshrc file, and tried the procedure again, without success...I am at a loss here. Same message about h_errno? - -- René Berber -BEGIN PGP SIGNATURE- Version: GnuPG

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread Kaplan, Andrew H.
Same message about h_errno? Yes -- the message is the same. ___ http://lurker.clamav.net/list/clamav-users.html

[Clamav-users] Re: Problem Upgrading ClamAV on HP-UX 10.20

2006-02-07 Thread René Berber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kaplan, Andrew H. wrote: Same message about h_errno? Yes -- the message is the same. OK, let's analyze the output of running configure. There are 3 tests inside configure that use netdb.h and h_errno, they seem to be testing to see what variant