maildrop looking for pcre.h URGENT

Hi Kevin,

If you have installed pcre to /pcrefolder.. try configuring maildrop with:

$ ./configure --prefix=/prefix/dir --includedir=/pcrefolder

then do the normal make and make install

appending configuration tag "F77" to libtool
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
checking pcre/pcre.h usability... no
checking pcre/pcre.h presence... no
checking for pcre/pcre.h... no
configure: error: pcre.h not found - install PCRE from www.pcre.org


What I had done was install prce into $HOME/prce2


Then I ran make clean, make and make install


Then onto maildrop...

$ ./configure --prefix=/prefix/dir --includedir=/pcre2




It ran until the error was given above...


Am I doing this right?

I have also been reading somewhere to download pcre-devel

I had the bz2 and bzip2 -d it,

now the tar file is in the root.

I tar -jx pcre-devel.tar the file but the folder does not appear in the root....

What am I doing wrong to try and install maildrop?

Cheers,

Kevin

Hi Kevin,

> What I had done was install prce into $HOME/prce2
> Then I ran make clean, make and make install
> Then onto maildrop...
> $ ./configure --prefix=/prefix/dir --includedir=/pcre2

the --includedir should be $HOME/pcre2

> I tar -jx pcre-devel.tar the file but the folder does not appear in the root....

use tar xf pcre-devel.tar

Hi Slyong,


tar xf tcre-devel.tar I had tried and it doesnt untar....

I also tried tar -xf tcre-devel.tar
but still no luck

I get no errors though when I do this...


Kevin

Hi Kevin,

with the original pcre-devel.tar.bz2.. try:

tar xjf pcre-devel.tar.bz2

or tar -xjf

Hi Slyong,

Both


tar xjf pcre-devel.tar.bz2
and
tar -xjf pcre-devel.tar.bz2


Didnt produce the tar file,

although i know bzip2 -d pcre-devel-4.5-1.tar.bz

did do the trick.

But now i have the .tar extension but whatever I try it doesnt extract to the folder pcre-devel-4.5-1

Cheers,

Kevin

Hi Kevin,

I am not sure where you get the pcre-devel-4.5.1.tar.bz from.  But if you get the file from pcre.org ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/.  The latest is pcre-6.6.tar.gz.  Download that file and do:

$ rm -rf $HOME/pcre2
$ mkdir -p $HOME/pcre2
$ tar xzf pcre-6.6.tar.gz
$ ./configure --prefix=$HOME/pcre2
$ make && make install

Then download maildrop-2.0.2 from http://prdownloads.sourceforge.net/courier/maildrop-2.0.2.tar.bz2

$ rm -rf $HOME/maildrop2
$ mkdir -p $HOME/maildrop2
$ tar xjf maildrop-2.0.2.tar.bz2
$ ./configure --prefix=$HOME/maildrop2 --includedir=$HOME/pcre2/include
$ make && make install

This step failed:


$ tar xzf pcre-6.6.tar.gz


tar: pcre-6.6.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors

Should I use gunzip?

Hi Kevin,

tar xzf pcre-6.6.tar.gz
        ^ with z option should gunzip the file and untar the file.

Could you do a 'ls -l' on that directory that you do tar xzf command and paste the output here?

tar xzf pcre-6.6.tar.gz failed?

The error that it is giving is telling you tht you do not have the file pcre-6.6.tar.gz

Are you 100% sure that it exists?, and that you have read permissions for this file and write permissions for the folder you are in?

(   (()
(`-' _\
 ''  ''

hey it's cool, It had the extension pcre-6.6.tar.bz2 in my directory, so I used bzip2 -d pcre-6.6.tar.bz2
then I ran tar -xf pcre-6.6.tar
then cd pcre-6.6


and then

./configure --prefix=$HOME/pcre2


So sofar so good, about to try maildrop now...

Hi,

when running ./configure --prefix=$HOME/maildrop2 --includedir=$HOME/pcre2/include
whilst being in  ~/maildrop-2.0.2

It runs but the pcre.h not found error still comes up...

Can you find pcre.h anywhere on your system?

As already suggested, Its possible that you need a pcre-devel type package/tar to possibly be installed in order to have this available.

However, try:

find /dir/of/pcre | grep pcre.h

and see if it exists.

(   (()
(`-' _\
 ''  ''

/home/koconnor/pcre2/include/pcre.h



File exists....

I typed


find $HOME/pcre2 | grep pcre.h

.....
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
checking pcre/pcre.h usability... no
checking pcre/pcre.h presence... no
checking for pcre/pcre.h... no


It's looking into the 'current' folder for pcre.h, and then it tries looking in /pcre/pcre.h. I guess that the person that configured the make file was setup by someone using a very specific setup.

You could mess around for ages with this! Easiest approach is probably to creat a pcre folder in the current makefile directory, and copy in the pcre files that it complains about. This may be a little time consuming and fiddly as ther will be a bit of 'successive approximation', but it will work. The various $include or other settings rely on the makefile developerhaving created support for them, and might not be supported in the manner that you suspect:(

(   (()
(`-' _\
 ''  ''

when running this:


./configure --prefix=$HOME/local

I had also copied into local a folder called pcre and in that folder a file called pcre.h

The same error came up, looking for pcre.h


Had I copied the files in the correct location, Local?

Cheers,

Kevin

Another deliberate mistake! - I'm really sloppy today!

It's looking for ./pcre/pcre.h not /pcre/pcre.h

(   (()
(`-' _\
 ''  ''

what is ./pcre

I have never seen that before

 How do I make it look there?

Another way of doing it might be to add:

--includedir=/home/koconnor/pcre2/include/

as that's where the header files are;)

(   (()
(`-' _\
 ''  ''

The . means the current directory. When you type ls -al you'll see a .. and a . at the top of the list. .. means up one directory and . means the current directory.

if you type:

ls .

it's effectively the same as:

ls

As to how you make it look there - you don't! As you can see from the error messages, that's where the configure script is expecting it to be.

so in the makefile/configure directory:

mkdir pcre
cp /path/to/pcre.h pcre/

and then reattempt the ./configure and make process.

(   (()
(`-' _\
 ''  ''

sorry for posting the whole file, but thought it might shed more info..

What I did was creat a folder called pcre in the root, installed pcre-6.6 using ./configure --prefix=$HOME/pcre
 then make && make install

then in maildrop I ran
./configure --prefix=$HOME/pcre



and this is the result:












./configure --prefix=$HOME/pcre
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for gawk... (cached) gawk
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-redhat-linux-gnu
checking host system type... x86_64-redhat-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... 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... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag  works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking pcre.h usability... no
checking pcre.h presence... no
checking for pcre.h... no
checking pcre/pcre.h usability... no
checking pcre/pcre.h presence... no
checking for pcre/pcre.h... no
configure: error: pcre.h not found - install PCRE from www.pcre.org





in pcre there is bin, man, lib and include.
I create pcre folder and added pcre.h and still no luck...

Hi Kevin,

Do you have root access to the system?  Appearently there is some problem with the maildrop and pcre on Fedora.  The simpler solution to this is to use the pcre-devel rpm.  However, if you don't have root access and only want to use the tarball installation then we will have to find another way out.

Hi,

I do have root access to my server.


I would like to try thr rpm but will need to know the commands for unzipping it if you could share them
Cheers,

Kevin

Could you put the output of:

# uname -a

we need to know which architecture you need.  If it is i386, download from http://rpm.pbone.net/index.php3/stat/4/idpl/2689584/com/pcre-devel-6.3-1.2.1.i386.rpm.html

with the pcre-devel-6.3-1.2.1.i386.rpm file, do:

# rpm -Uvh pcre-devel-6.3-1.2.1.i386.rpm

Hi,

Linux sparta.micfo.com 2.6.15.4-AMDv7 #2 SMP Mon Feb 13 05:06:55 CST 2006 x86_64 x86_64 x86_64 GNU/Linux


Hope this helps,

Kevin

OK - 64bit AMD....here you go:

http://rpm.pbone.net/index.php3/stat/4/idpl/2722982/com/pcre-devel-6.3-1.2.1.x86_64.rpm.html

(   (()
(`-' _\
 ''  ''

rpm: arguments to --root (-r) must begin with a /


What must I do here?

Cheers,

Kevin

??? Bizarre - never seen that before???

As root:

wget ftp://mirror.switch.ch/mirror/fedora/linux/core/5/x86_64/os/Fedora/RPMS/pcre-devel-6.3-1.2.1.x86_64.rpm
rpm -ivh /full/path/to/pcre-devel-6.3-1.2.1.x86_64.rpm

and hopefully that'll install it for you

(   (()
(`-' _\
 ''  ''

warning: pcre-devel-6.3-1.2.1.x86_64.rpm: V3 DSA signature: NOKEY, key ID 4f2a6fd2
error: Failed dependencies:
        pcre = 6.3-1.2.1 is needed by pcre-devel-6.3-1.2.1.x86_64



It seems my server is a mess?!

warning: pcre-6.3-1.2.1.x86_64.rpm: V3 DSA signature: NOKEY, key ID 652e84dc
error: can't create transaction lock


Well you are right we are making progress... Am I missing some thing else do you think?

You need to be root to run rpm install? The message indicates that you don't have sufficient permissions. (Alternatively, we may have to look at your SEL configuration - try disabling it during the install)

(   (()
(`-' _\
 ''  ''

Ok, I was speaking with the hosting company who never had originally given me full access, but apparently now I do have it...

Could you tell me how to disable SEL configuration?

THanks a million I really am appreciating yours and Slyong's help with this.

***READ WHOLE POST BEFORE RUNNING***

echo "0" >/selinux/enforce

is the easy way:)...but I'm sure that there is a tool somewhere in FC5...I just can't remember what it is:( Therefore, make a copy of your enforce file before running the above command.

(   (()
(`-' _\
 ''  ''

Hi,

I dont mean to sound silly, but I cant find enforce file anywhere, or a folder called selinux.

I am in the root directory also...

Sorry - should be /etc/selinux/enforce

If the selinux folder doesn't exist, then you do not have selinux causing the problem and we need to look elsewhere..

(   (()
(`-' _\
 ''  ''

Hi Kevin,

> warning: pcre-6.3-1.2.1.x86_64.rpm: V3 DSA signature: NOKEY, key ID 652e84dc
> error: can't create transaction lock

Could you make sure that you are running the rpm command as root and that that you are not other yum or rpm is running?

Hi,

What I typed in the root was:

$ rpm -ivh pcre-6.3-1.2.1.x86_64.rpm


This is correct is it?

What you typed in was fine, however try:

rpm -Uvh pcre-6.3-1.2.1.x86_64.rpm

Also try:

whoami

It should tell you that you are 'root' If you are not, then that is the cause of the problem. Type:

su

and enter the root password, then repeat the above commands.

(   (()
(`-' _\
 ''  ''

Hi Kevin,

the command is correct but normally when you are root you have a "#" prompt...  Try this

$ su -
<you will be prompt for password>

# rpm -ivh pcre*

make sure that both pcre-6.3-1.2.1.x86_64.rpm and pcre-devel-6.3-1.2.1.x86_64.rpm is in the directory, rpm will install them both

On typing su it says

-bash: /bin/su: Permission denied


and on typing
whoami

it says
koconnor
(my username and it doesnt say 'root')


What should I do/say to my hosting company??

Cheers guys you are geniuses!

hmm... if you could ask the hosting company if you can install software system wide.  Otherwise, we will have to go back to thinker with the tarballs...  There are two choices with the hosting company:

1) ask them to install pcre-devel... give them the rpms.. they might install it for you
2) ask them if you are supposed to have root access..

I think (1) is easier then asking for (2).

Ok I have asked them and they are usually quick to respond.

If they will not allow this can the tarballs method work out well or is there a lot more work involved?

the tarball method needs a bit of thinkering.. I am not so sure about the problem with the tarball installation.

The tarballs will work, but all the dependencies are proving particularly difficult. Offer to provide them with the rpm files and get them to do it! - Make them work;)

(   (()
(`-' _\
 ''  ''

"The tarballs will work, but all the dependencies are proving particularly difficult. Offer to provide them with the rpm files and get them to do it! - Make them work;)"


Exactly! Well let's see how they fair up.

Are they usually good to do these things? i am with a crowd called micfo.com

Hi Kevin,

Finally able to get around to test it on my system.  You can use the tarballs as follows:

1) Download pcre from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-6.6.tar.gz

2) Download maildrop from http://prdownloads.sourceforge.net/courier/maildrop-2.0.2.tar.bz2

3) unpack the files:
$ gunzip pcre-6.6.tar.gz; tar -xf pcre-6.6.tar
$ bunzip2 maildrop-2.0.2.tar.bz2; tar -xf maildrop-2.0.2.tar

4) compile and install pcre (assuming that you want to install into /home/koconnor/test)
$ cd pcre-6.6
$ mkdir -p /home/koconnor/test
$ ./configure --prefix=/home/koconnor/test && make && make install

5) compile and install maildrop, take note of the command export CPPFLAGS="-I...." thingy:
$ cd ../maildrop-2.0.2
$ export CPPFLAGS="-I/home/koconnor/test/include"
$ ./configure --prefix=/home/koconnor/test && make && make install

Got all the way to the last step, maildorp configuring and got this error:



checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.




Below is the bottom part of the config log

##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /home/koconnor/maildrop-2.0.2/missing --run aclocal-1.9'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /home/koconnor/maildrop-2.0.2/missing --run tar'
AR=''
AUTOCONF='${SHELL} /home/koconnor/maildrop-2.0.2/missing --run autoconf'
AUTOHEADER='${SHELL} /home/koconnor/maildrop-2.0.2/missing --run autoheader'
AUTOMAKE='${SHELL} /home/koconnor/maildrop-2.0.2/missing --run automake-1.9'
AWK='gawk'
CC='gcc'
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS='I/home/koconnor/local/include'
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W='echo'
DBSUBDIR=''
DEFS=''
DEPDIR=''
DEVEL_FALSE=''
DEVEL_INCLUDES=''
DEVEL_LIBS=''
DEVEL_TRUE=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
HAVE_SGML_FALSE=''
HAVE_SGML_TRUE=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_DELIVERQUOTA_FALSE=''
INSTALL_DELIVERQUOTA_TRUE=''
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LDFLAGS=''
LIBDB=''
LIBGDBM=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBOBJS=''
MAILBOT=''
MAILBOT_FALSE=''
MAILBOT_TRUE=''
MAKEINFO='${SHELL} /home/koconnor/maildrop-2.0.2/missing --run makeinfo'
OBJEXT=''
PACKAGE='maildrop'
PACKAGE_BUGREPORT='courier-maildrop@lists.sourceforge.net'
PACKAGE_NAME='maildrop'
PACKAGE_STRING='maildrop 2.0.2'
PACKAGE_TARNAME='maildrop'
PACKAGE_VERSION='2.0.2'
PATH_SEPARATOR=':'
RANLIB=''
REPOSITORY=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
USE_DB=''
USE_GDBM=''
VERSION='2.0.2'
ac_ct_AR=''
ac_ct_CC='gcc'
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${prefix}/share'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh='/home/koconnor/maildrop-2.0.2/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
mkdir_p='mkdir -p --'
oldincludedir='/usr/include'
prefix='/home/koconnor/local'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
subdirs=''
sysconfdir='${prefix}/etc'
target_alias=''
withetcdir=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_BUGREPORT "courier-maildrop@lists.sourceforge.net"
#define PACKAGE_NAME "maildrop"
#define PACKAGE_STRING "maildrop 2.0.2"
#define PACKAGE_TARNAME "maildrop"
#define PACKAGE_VERSION "2.0.2"

configure: exit 77


No errors or anything came up with the CPPFLAGS code

can you try this command?

$ g++ -v

It seems like you don't have g++ (GNU C++ compiler) installed.  If that is the case, you better talk to your hosting provider and ask for g++ to be installed.

# g++ -v
Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.5/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=x86_64-redhat-linux
Thread model: posix
gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)

I'd agree with slyond, but you can always check by looking at the config.log

(   (()
(`-' _\
 ''  ''

Hi all,

It seems to be working now.. what I did was not include the above sentence:

# export CPPFLAGS="-I/home/koconnor/test/include"

And instead did the rest and it seems to be working ...

there was an error however it didnt seem to not install?


Is there anyway I can test to see if this mail set up propgram is working ok? I ahve never used it before and just wanted to test it.

I will post the error incase you think it may cause problems later, thanks all  I really appreciate it.

Kevin

The error guys, incase you think it will not make it work



gdbmobj.c:173: error: dereferencing pointer to incomplete type
make[2]: *** [gdbmobj.lo] Error 1
make[2]: Leaving directory `/home/koconnor/maildrop-2.0.2/gdbmobj'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/koconnor/maildrop-2.0.2/gdbmobj'
make: *** [all-recursive] Error 1


Cheers,

Kevin

PS is this venturing into a new question?

Probably, but there is merit in keeping the information together as it does provide useful additional information. If you decide to set it out as a seperate question, ensure that you have a link to this one, as the history is relavent.

However, the errors appear to be in an area associated with the gnu debugging process. Personally, I'd expect that you shouldn't be using that for your system, so it may be OK? However, I believe that this error is worth highlighting to the maildrop development team as I suspect that it is a 'glitch' in the makefile.

(   (()
(`-' _\
 ''  ''

Hi Kevin,

I tested the whole thing on gcc 4 and it seems fine.  However, I don't have a machine with gcc 3.4, it might not handle some of the program properly.  One solution could be to skin the gdbm all together.  Try this:

1) in /home/koconnor/maildrop-2.0.2/
2) ./configure --prefix=/home/koconnor/test --without-db
3) make clean
4) make
5) make install

See if that helps.

Hi,

I have done as above and the same error came up in the make install

make[1]: Entering directory `/home/koconnor/maildrop-2.0.2/gdbmobj'
Compiling gdbmobj.c
In file included from gdbmobj.c:10:
gdbmobj.h:11:18: gdbm.h: No such file or directory
In file included from gdbmobj.c:10:
gdbmobj.h:20: error: syntax error before "GDBM_FILE"
gdbmobj.h:20: warning: no semicolon at end of struct or union
gdbmobj.h:24: error: syntax error before '}' token
gdbmobj.c: In function `gdbmobj_init':
gdbmobj.c:23: error: dereferencing pointer to incomplete type
gdbmobj.c:24: error: dereferencing pointer to incomplete type
gdbmobj.c:25: error: dereferencing pointer to incomplete type
gdbmobj.c: In function `gdbmobj_close':
gdbmobj.c:30: error: dereferencing pointer to incomplete type
gdbmobj.c:32: error: dereferencing pointer to incomplete type
gdbmobj.c:33: error: dereferencing pointer to incomplete type
gdbmobj.c:35: error: dereferencing pointer to incomplete type
gdbmobj.c:37: error: dereferencing pointer to incomplete type
gdbmobj.c:38: error: dereferencing pointer to incomplete type
gdbmobj.c: In function `gdbmobj_open':
gdbmobj.c:44: error: `GDBM_READER' undeclared (first use in this function)
gdbmobj.c:44: error: (Each undeclared identifier is reported only once
gdbmobj.c:44: error: for each function it appears in.)
gdbmobj.c:50: error: `GDBM_WRCREAT' undeclared (first use in this function)
gdbmobj.c:54: error: `GDBM_WRITER' undeclared (first use in this function)
gdbmobj.c:58: error: `GDBM_NEWDB' undeclared (first use in this function)
gdbmobj.c:63: error: dereferencing pointer to incomplete type
gdbmobj.c:70: error: dereferencing pointer to incomplete type
gdbmobj.c:76: error: dereferencing pointer to incomplete type
gdbmobj.c: In function `gdbmobj_store':
gdbmobj.c:87: error: `datum' undeclared (first use in this function)
gdbmobj.c:87: error: syntax error before "dkey"
gdbmobj.c:90: error: `dkey' undeclared (first use in this function)
gdbmobj.c:93: error: `dval' undeclared (first use in this function)
gdbmobj.c:96: error: dereferencing pointer to incomplete type
gdbmobj.c:96: error: dereferencing pointer to incomplete type
gdbmobj.c:98: error: `GDBM_INSERT' undeclared (first use in this function)
gdbmobj.c:98: error: `GDBM_REPLACE' undeclared (first use in this function)
gdbmobj.c: In function `gdbmobj_exists':
gdbmobj.c:103: error: `datum' undeclared (first use in this function)
gdbmobj.c:103: error: syntax error before "dkey"
gdbmobj.c:105: error: dereferencing pointer to incomplete type
gdbmobj.c:107: error: `dkey' undeclared (first use in this function)
gdbmobj.c:110: error: dereferencing pointer to incomplete type
gdbmobj.c: In function `gdbm_dofetch':
gdbmobj.c:166: error: `datum' undeclared (first use in this function)
gdbmobj.c:166: error: syntax error before "dkey"
gdbmobj.c:168: error: dereferencing pointer to incomplete type
gdbmobj.c:170: error: `dkey' undeclared (first use in this function)
gdbmobj.c:173: error: `val' undeclared (first use in this function)
gdbmobj.c:173: error: dereferencing pointer to incomplete type
make[1]: *** [gdbmobj.lo] Error 1
make[1]: Leaving directory `/home/koconnor/maildrop-2.0.2/gdbmobj'
make: *** [install-recursive] Error 1



Saying that is it possible that this may still be working?!



Cheers,


Kevin

Hi Kevin,

I am affraid not.  The make failed means that your compilation of the program is not complete.  It seems to me that:

> In file included from gdbmobj.c:10:
> gdbmobj.h:11:18: gdbm.h: No such file or directory

you don't have gdbm-devel installed.  Could you verify that by doing:

$ rpm -qa | grep gdbm

You need yout gdbm version to match the version of gdbm-devel. For example:

[root@bigserver root]# rpm -q gdbm
gdbm-1.8.0-20
[root@bigserver root]# rpm -q gdbm-devel
gdbm-devel-1.8.0-20

on my server. Once we know yout gdbm version, we can find the appropriate gdbm-devel version. Of course if you've got the install discs, then you should be able to mount the CD, and:

rpm -ivh gdbm-devel-x.x.x-xx.x86_64.rpm

And then retry the make process

(   (()
(`-' _\
 ''  ''

Hi, the answer to $ rpm -qa | grep gdbm


[~]# rpm -qa | grep gdbm
gdbm-1.8.0-24
gdbm-1.8.0-24
gdbm-devel-1.8.0-24


Does this make anything clearer?

Do you guys think we can get this working or is it a case of not enough privelidges?

Cheers guys

Kevin

Hi Kevin,

Seems like you have gdbm-devel... may be the CPPFLAGS mess it up.  Could you try this:

$ cd /home/koconnor/maildrop-2.0.2/
$ export CPPFLAGS="-I/home/koconnor/test/include -I/usr/include"
$ ./configure --prefix=/home/koconnor/test
$ make clean
$ make
$ make install

Hi Slyong,

No luck unfortunately, same error as before...


May I make the point that my directory level access says ~ # and not $ as I originally thought.

Is this a problem?

Hi Kevin,

Not sure what do you mean by directory level access... do you mean the prompt is now "#".  What does "whoami" says?  If it still says "koconnor" then it is still the same.

Regards,

yep, it still says koconnor


My hosting company said they have installed pcre-devel for me...

So perhaps I should try a different earlier version of maildrop as this one could be problematic?

Trying a different version (earlier) may help, but unfortunately, you're in a 'restricted' environment, so you may continue to have problems. On the plus side, you seem to have a good (responsive) host support setup, which is always a good start:)

Since the pcre-devel is installed... you can verify and try to build maildrop again.

# rpm -qa pcre-devel
to check if pcre-devel is installed...

# cd /home/koconnor/maildrop-2.0.2/
# ./configure --prefix=/home/koconnor/test
# make clean
# make
# make install