configure on solaris 10 with argus 3.0
Eric Pancer
epancer at pobox.com
Thu Feb 14 13:42:58 EST 2008
On Thu, 2008-02-14 at 12:34:58 -0500, Carter Bullard proclaimed...
> Look in the config.log to see which bison it found. Now that I'm
> thinking about it, its possible that the make will use whatever
> bison is in your path ("V_YACC='bison -y -p argus_'"). So
> what bison does "which bison" return?
>
> Run bison by hand, with the parameters in the make file,
> adding the --verbose option to see what its complaining about.
> If that works, without error, maybe make() is finding a different
> bison? Modify the make file to run bison --version, or "which bision"
> to see what its picking up.
>
> It could be that flex is the problem, and its output is not good.
> Run it also by hand to see if the grammar.c file that it generates
> is reasonable.
>
> The big test has been for flex above 2.4, in order to get the right
> behavior for the "-Pargus_" option. The version of bison in your
> path is fine 2.3. I'm running bison 2.3 and and flex 2.5.33.
I don't know if the following will help...
Relevant sections of config.log
| PATH: /usr/bin
| PATH: /usr/local/bin
| PATH: /usr/ccs/bin
| PATH: /usr/local/argus/bin
| PATH: /usr/sbin
| PATH: /usr/local/sbin
| [..]
| configure:9096: result: no
| configure:9099: WARNING: tcp_wrapper not found
| configure:9930: checking for flex
| configure:9946: found /usr/local/bin/flex
| configure:9957: result: flex
| configure:9970: checking for flex 2.4 or higher
| configure:9982: result: yes
| configure:10000: checking for bison
| configure:10016: found /usr/local/bin/bison
| configure:10027: result: bison
| configure:10056: checking for ranlib
| configure:10072: found /usr/ccs/bin/ranlib
| configure:10083: result: ranlib
| configure:10095: checking if unaligned accesses fail
| configure:10151: result: yes
| configure:10307: checking for LD_LIBRARY_PATH
| configure:10314: result: no -- this may be a problem in a few seconds
| configure:10363: checking for a BSD-compatible install
| configure:10419: result: /usr/local/bin/install -c
| configure:10430: checking for ANSI C header files
| configure:10594: result: yes
| configure:10737: creating ./config.status
| [..]
| ac_cv_prog_V_LEX=flex
| ac_cv_prog_V_RANLIB=ranlib
| ac_cv_prog_V_YACC=bison
Where's bison?
| sunos$ find / -name bison 2>/dev/null
| /usr/local/doc/bison
| /usr/local/bin/bison
| /usr/local/share/bison
Let's run as much as we can manually....in argus/common/
| sunos$ pwd
| /archive/home/epancer/tmp/argus-3.0.0/common
| sunos$ ls -la
| total 662
| drwxr-xr-x 2 epancer other 512 Feb 12 23:16 .
| drwxr-xr-x 11 epancer other 512 Feb 12 23:16 ..
| -r-xr-xr-x 1 epancer other 3685 Feb 6 22:39 Makefile.in
| -r--r--r-- 1 epancer other 13850 Feb 4 21:37 argus_auth.c
| -r--r--r-- 1 epancer other 110869 Feb 4 21:37 argus_code.c
| -r--r--r-- 1 epancer other 76024 Feb 4 21:37 argus_filter.c
| -r--r--r-- 1 epancer other 95659 Feb 4 21:37 argus_util.c
| -r-xr-xr-x 1 epancer other 12518 Feb 4 21:37 grammar.y
| -r-xr-xr-x 1 epancer other 8877 Feb 4 21:37 scanner.l
| sunos$ /usr/local/bin/flex -Pargus_ -t scanner.l > $$.scanner.c; mv
| $$.scanner.c scanner.c
| sunos$ ls -l scanner.c
| -rw-r--r-- 1 epancer other 85346 Feb 14 12:39 scanner.c
| sunos$ bison -y -pargus_ -d grammar.y
| sunos$ ls -l
| total 826
| -r-xr-xr-x 1 epancer other 3685 Feb 6 22:39 Makefile.in
| -r--r--r-- 1 epancer other 13850 Feb 4 21:37 argus_auth.c
| -r--r--r-- 1 epancer other 110869 Feb 4 21:37 argus_code.c
| -r--r--r-- 1 epancer other 76024 Feb 4 21:37 argus_filter.c
| -r--r--r-- 1 epancer other 95659 Feb 4 21:37 argus_util.c
| -r-xr-xr-x 1 epancer other 12518 Feb 4 21:37 grammar.y
| -rw-r--r-- 1 epancer other 85346 Feb 14 12:39 scanner.c
| -r-xr-xr-x 1 epancer other 8877 Feb 4 21:37 scanner.l
Unfortunately I don't get anything when I run that; is something supposed to
actually occur?
Could the problem be with yacc?
- Eric
More information about the argus
mailing list