[Exim] Compile error

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: John (TJ) Penton
Fecha:  
A: Exim users mailing list
Asunto: [Exim] Compile error
Dear All,

I use Exim on (amoung other things) a SUSE 7 box. Each time I compile I
notice a particular error, and, while I know how to solve the problem, I
thought I should post it to the mailing list in case it is a real bug.

> make

...
gcc -c -I/usr/include/db1 -I.    verify.c
gcc -c -I/usr/include/db1 -I.  -o local_scan.o ../src/local_scan.c
cc -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64  -I/usr/lib/perl5/5.6.1/i586-linux/CORE   -c perl.c
In file included from exim.h:324,
                 from perl.c:15:
dbstuff.h:101: db.h: No such file or directory
make[1]: *** [perl.o] Error 1
make[1]: Leaving directory
`/tmp/construction-yard/exim-4.10/build-Linux-i386'
make: *** [go] Error 2

> cd build-Linux-i386/
> cc -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE

-D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.6.1/i586-linux/CORE -c perl.c
-I/usr/include/db1
> cd ..
> make

...
>>> exim binary built


SUSE keeps its DB headers in /usr/include/db1, which I specify in
Local/Makefile thus:

CFLAGS = -I/usr/include/db1

but it seems for that one compile line, the -I flag doesn't get included.
I don't really know what I am talking about - is there something there
that can be fixed or am I doing something wrong myself?

HTH

John

--
"I shouldn't be surprised if it hailed a good deal tommorow," Eeyore
was saying. "Blizzards and what-not. Being fine to-day doesn't Mean
Anything. It has no sig - what's that word? Well, it has none of it.
It's just a small piece of weather."