> -----Original Message-----
> From: Rost, Werner
> Sent: Wednesday, September 18, 2002 2:43 AM
>
> seems you are a great specialist for SquidGuard. Did you develop this
> software?
No sir, I'm just a squidGuard user donating my efforts to help other
squidGuard users.
> snip
> Using OS TRU64 5.1A ...
> snip
I didn't realize that you were on a TRU64 Unix box; my fault for not
asking.
There are obviously differences between TRU64 and Linux, and I'm
virtually clueless about TRU64.
Perhaps there is someone else here on the list that can pick up the
ball and run with it?
Rick
> Ok, let me do it again - step by step.
>
> 1. delete directory /usr/local/BerkelyDB.3.2
> and /usr/local/db-3.2.9
>
> --> no Berkely* -Directories and no db-*Directories
> exist anymore
>
>
> 2. cd /usr/local/squidGuard-1.2.0
> make clean
>
>
> 3. Create directory /usr/local/db-3.2.9
>
> # gunzip db_3.2.9.tar.gz
> # tar -xf db_3.2.9.tar
>
>
>
> 4. Install the two patches
>
> # pwd
> /usr/local/db-3.2.9
> # ls -l db_pat*
> -rw-r--r-- 1 root users 2139 Sep 18 09:04 db_patch.3.2.9.1
> -rw-r--r-- 1 root users 495 Sep 18 09:04 db_patch.3.2.9.2
> #
> # patch -p0 < db_patch.3.2.9.1
> Hmm... Looks like a new-style context diff to me...
> The text leading up to this was:
> --------------------------
> |*** include/log.h.orig 2001/01/25 18:22:51 11.20
> |--- include/log.h 2001/02/06 05:02:28 11.21
> --------------------------
> Patching file include/log.h using Plan A...
> Hunk #1 succeeded at 198.
> Hmm... The next patch looks like a new-style context diff to me...
> The text leading up to this was:
> --------------------------
> |*** log/log.c.orig 2001/01/25 18:22:55 11.43
> |--- log/log.c 2001/02/06 05:02:28 11.44
> --------------------------
> Patching file log/log.c using Plan A...
> Hunk #1 succeeded at 309.
> Hunk #2 succeeded at 385.
> Hunk #3 succeeded at 414.
> Hunk #4 succeeded at 424.
> done
> #
> # patch -p0 < db_patch.3.2.9.2
> Hmm... Looks like a new-style context diff to me...
> The text leading up to this was:
> --------------------------
> |*** log/log_rec.c.orig 2001/01/25 18:22:56 11.49
> |--- log/log_rec.c 2001/02/07 22:17:46
> --------------------------
> Patching file log/log_rec.c using Plan A...
> Hunk #1 succeeded at 404.
> Hmm... Ignoring the trailing garbage.
> done
> #
>
>
>
>
> 5. Configure + make db
>
> # cd /usr/local/db-3.2.9/build_unix
> # ../dist/configure
> # make
> # make install
>
>
> see appending logfile db_configure.txt
>
> =========================================================
> Now BerkeleyDB is installed
> There exists a directory /usr/local/BerkeleyDB.3.2
> =========================================================
>
>
> 6. ldconfig
>
> Using OS TRU64 5.1A there is no command ldconfig
> nor exists a file /etc/ld.so.conf
>
> Therefore I skip these recommended steps.
>
>
>
>
> 7. Creating the SqudiGuard-Directory
>
> # pwd
> /usr/local
> # tar -xf squidGuard-1.2.0.tar
> #
>
>
>
>
> 8a. Configure SquidGuard using the Standard C-Compiler
>
> cd /usr/local/squidGuard-1.2.0
> ./configure --with-db-lib=/usr/local/BerkeleyDB.3.2/lib \
> --with-sg-config=/usr/local/squidGuard/filter.conf
>
> checking for gcc... no
> checking for cc... cc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> checking whether we are using the GNU C compiler... no
> checking whether cc accepts -g... yes
> checking how to run the C preprocessor... cc -E
> checking whether make sets ${MAKE}... yes
> checking for a BSD compatible install... ./install-sh -c
> checking for bison... no
> checking for byacc... no
> checking for flex... flex
> checking for yywrap in -lfl... no
> checking for yywrap in -ll... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... yes
> checking for lynx... false
> checking for perl... /usr/bin/perl
> checking for db_version in -ldb... no
>
> ** The Berkley DB library is required for squidGuard
> to compile. Get it from http://www.sleepycat.com
> use --with-db=DIR or --with-db-lib=DIR to specify
> its location. (default is /usr/local/BerkeleyDB)
>
> No Makefile / Makefile.in are built.
>
> ---> see appending C_config.log
>
>
>
> 8b. Configure SquidGuard using the GNU GCC-Compiler 3.0
>
> cd /usr/local/squidGuard-1.2.0
> (setenv CC "/usr/local/bin/gcc"; setenv CFLAGS "-O3"; \
> ./configure --with-sg-config=/usr/local/squidGuard/filter.conf \
> --with-db=/usr/local/BerkeleyDB.3.2)
>
>
> checking for gcc... /usr/local/bin/gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> checking whether we are using the GNU C compiler... yes
> checking whether /usr/local/bin/gcc accepts -g... yes
> checking how to run the C preprocessor... /usr/local/bin/gcc -E
> checking whether make sets ${MAKE}... yes
> checking for a BSD compatible install... ./install-sh -c
> checking for bison... no
> checking for byacc... no
> checking for flex... flex
> checking for yywrap in -lfl... no
> checking for yywrap in -ll... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... yes
> checking for lynx... false
> checking for perl... /usr/bin/perl
> checking for db_version in -ldb... yes
> checking for ANSI C header files... yes
> checking for db.h... yes
> checking for regex.h... yes
> checking for unistd.h... yes
> checking for /usr/local/bin/gcc option to accept ANSI C... none needed
> checking for an ANSI C-conforming const... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... no
> checking for unistd.h... (cached) yes
> checking for size_t... yes
> checking whether struct tm is in sys/time.h or time.h... time.h
> checking for regcomp... yes
> checking for regerror... yes
> checking for regexec... yes
> checking for strdup... yes
> checking for strerror... yes
> checking for vsprintf... yes
> checking for sigaction... yes
> checking for signal... yes
> checking for regexec... yes
> checking for strdup... yes
> checking for strerror... yes
> checking for vsprintf... yes
> checking for sigaction... yes
> checking for signal... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating src/Makefile
> config.status: creating src/sg.h
> config.status: creating doc/Makefile
> config.status: creating test/Makefile
> config.status: creating test/test1.conf
> config.status: creating test/test2.conf
> config.status: creating samples/Makefile
> config.status: creating samples/sample.conf
> config.status: creating samples/squidGuard.cgi
> config.status: creating samples/squidGuard-simple.cgi
> config.status: creating contrib/Makefile
> config.status: creating contrib/squidGuardRobot/squidGuardRobot
> config.status: creating contrib/sgclean/sgclean
> config.status: creating contrib/hostbyname/hostbyname
> config.status: creating src/config.h
>
>
> Makefile + Makefile.in are created
>
>
> see appending GCC_config.log
>
>
> 9. make squidGuard
>
> # pwd
> /usr/local/squidGuard-1.2.0
> # make
> making all in squidGuard-1.2.0
> making all in src
> /usr/local/bin/gcc -I.. -I. -I. -I/usr/local/BerkeleyDB.3.2/include
> -DHAVE_CONFI
> G_H -O3 -I/usr/local/BerkeleyDB.3.2/include -c main.c
> In file included from main.c:19:
> sg.h:195: parse error before "DB_INFO"
> sg.h:195: warning: no semicolon at end of struct or union
> sg.h:201: parse error before '}' token
> *** Exit 1
> Stop.
> *** Exit 1
> Stop.
> #
>
>
>
>
> Any hints were welcome.
>
> Thanks a lot
>
> Werner Rost
>
>
>
> > -----Urspr�ngliche Nachricht-----
> > Von: Rick Matthews [mailto:[EMAIL PROTECTED]]
> > Gesendet am: Dienstag, 17. September 2002 19:24
> > An: Rost, Werner
> > Betreff: RE: domainlist empty, removed from memory FINAL CORRECTION
> >
> > I'm really sorry that you are experiencing all of these problems. I'm
> > no expert, but I've been reviewing this information and researching
> > a few things for the last hour or so, and I have a few thoughts. I
> > don't know if the answer is in here anywhere, but I believe my
> > questions are reasonable, considering the data.
> >
> > - Copy /usr/local/src/squidGuard-1.2.0/config.log to another name
> > so we don't lose it.
> >
> > - Did you delete the Berkeley 3.2.9 directories (in /usr/local/src/
> > and /usr/local/) before reinstalling the Berkeley DB? (I probably
> > would have.)
> >
> > - Before starting over each time with 'make', did you run
> > 'make clean'?
> >
> > - Did you run the command
> > 'echo /usr/local/BerkeleyDB.3.2/lib >> /etc/ld.so.conf'?
> >
> > - What is the content of your /etc/ld.so.conf file?
> >
> > - Did you run the command 'ldconfig'?
> >
> > It bothers me that the first make indicated:
> > > checking for db_version in -ldb... no
> > and the second make indicated:
> > > checking for db_version in -ldb... yes
> >
> > This relates to the "echo..." and ldconfig questions above.
> >
> > The echo command adds the /usr/local/BerkeleyDB.3.2/lib directory
> > to the ld.so.conf file. The ldconfig command reconfigures the links
> > and cache that is used by the run-time linker.
> >
> > The '-ldb' that is mentioned is a directive to the compiler
> > (-l library) that tells it to search the library 'db' when linking.
> > To find that library, it prepends 'lib' and appends '.a' and looks
> > through the search directories (which should now include
> > /usr/local/BerkeleyDB.3.2/lib) for libdb.a (which should be located in
> > /usr/local/BerkeleyDB.3.2/lib).
> >
> > If you don't see anything obvious, would you send me a copy of
> > /usr/local/src/squidGuard-1.2.0/config.log
> >
> > Thanks,
> > Rick
> >
>
>
>
> ---------------------------------------------------------
> This Mail has been checked for Viruses
> Attention: Encrypted mails can NOT be checked!
>
> **
>
> Diese Mail wurde auf Viren geprueft
> Hinweis: Verschluesselte mails koennen NICHT auf Viren geprueft werden!
> ---------------------------------------------------------
>
>
