#10 configure script and solaris
trying to compile and install on solaris, I found two problems:
the code that creates the drivers.c file is not interpreted correctly. The solaris sh doesn't seem to have a -e option, and doesn't interpret the square brackets correctly - so what happens is that the first line of the drivers.c file looks like this:
-e static const CALDRIVER *driver_registry\133\135 = {
this makes the compiler die.
secondly (although much more minor), was that the install script in the makefile doesn't seem to take notice of the --prefix option that you can use with configure. Would it be possible to modify the script to pick this up, and use it - which would allow non-standard locatiosn to be used easily?
One other suggestion I would make is that in the mkdir section of the install, would it be possible to add a check to see whether the directories already exist? I think that you could maybe use the install.sh and mkdir.sh scripts that come with the apache distribution (in the directory src/helpers) would maybe make this stuff a bit easier to do...
hope this is of help
Lindsay
email: l.b.jack@liv.ac.uk
This behaviour is also exhibited under FreeBSD 3.3.4.
I am also getting this under FreeBSD 3.2
gcc -O0 -Wall -g -Imstore -Iicap -I. -c mcal.c
In file included from mcal.c:37:
drivers.c:1: stray \'\\\' in program
drivers.c:1: parse error before `33\'
drivers.c:1: stray \'\\\' in program
mcal.c: In function `cal_getdriver\':
mcal.c:68: `driver_registry\' undeclared (first use this function)
mcal.c:68: (Each undeclared identifier is reported only once
mcal.c:68: for each function it appears in.)
drivers.c looks like:
static const CALDRIVER *driver_registry\\133\\135 = {
&icap_driver,
&mstore_driver,
NULL
};
Why has this bug been outstanding for so long? This bug was a pain for several minutes until I figured out what was going on. It is a pretty trivial fix and I can supply patches if needed.