Making GDBM [ a long story ]

Making GDBM [ a long story ]

[David A. Cobb]

Background: trying to configure an XEmacs-21.5.1--i686-pc-cygwin beta, 
selected --with-database=gdbm but got a complaint:
:[S!] Bash $ cd build-i686-pc-cygwin/
:[S!] Bash $ ../configure i686-pc-cygwin --prefix=/usr/local \
 > --exec-prefix=/usr/local/i686-pc-cygwin \
 > --without-x \
 > --with-gcc \
 > --with-site-lisp \
 > --with-database=gdbm \
 > --use-union-type
loading site script /etc/config.site
. . . .
checking for PostgreSQL
checking for libpq-fe.h... no
checking for pgsql/libpq-fe.h... no
checking for postgresql/libpq-fe.h... yes
checking for PQconnectdb in -lpq... yes
     Defining HAVE_POSTGRESQL
checking for PQconnectStart in -lpq... yes
! *** Even though I didn't request --with-database=postgresql !
. . . .
checking for sound support
checking for machine/soundcard.h... no
checking for sys/soundcard.h... yes
     xemacs will be linked with "linuxplay.o"
     Defining SOUNDCARD_H_FILE = "sys/soundcard.h"
     Defining HAVE_NATIVE_SOUND
checking for esd-config... no
     xemacs will be linked with "miscplay.o"
! *** THIS IS GOING TO BE ANOTHER PROBLEM *** !
. . . .
AND FINALLY
. . . .
checking for database support
checking for ndbm.h... no
Error: Required DBM support cannot be provided.
:[S!] Bash $

Aha! Maybe I need to build it locally {I thought}, so - get the source and 
. . . .
:[S!] Bash $ ../configure --target=i686-pc-cygwin \
 > --without-x \
 > --with-gnu-ld \
 > --exec-prefix=/usr/local/i686-pc-cygwin/
creating cache ./config.cache
checking for gcc... /usr/bin/gcc -mcygwin
checking whether the C compiler (/usr/bin/gcc -mcygwin  ) works... yes
. . . .
checking for /usr/bin/gcc option to produce PIC... -fPIC
checking if /usr/bin/gcc PIC flag -fPIC works... no
checking if /usr/bin/gcc static flag -static works... -static
checking if the linker 
(/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/../../../../i686-pc-cygwin/bin/ld.exe) 
is GNU ld... yes
checking whether the linker 
(/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/../../../../i686-pc-cygwin/bin/ld.exe) 
supports shared libraries... yes
checking command to parse /usr/i686-pc-Cygwin/bin//nm -B output... no
checking how to hardcode library paths into programs... immediate
checking for 
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/../../../../i686-pc-cygwin/bin/ld.exe 
option to reload object files... -r
checking dynamic linker characteristics... no
checking if libtool supports shared libraries... no
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
checking for working const... yes
. . . .
creating Makefile
creating autoconf.h
:[S!] Bash $ make
/bin/sh ../libtool --mode=compile /usr/bin/gcc -mcygwin -c   -I. -I.. -O 
../dbminit.c
../libtool: Can't open ../libtool: No such file or directory
make: *** [dbminit.lo] Error 2
:[S!] Bash $

SO, obviously I should do something differently.  What?

Tia,

David A. Cobb, Software Engineer, Public Access Advocate, All around nice guy.
Get my PGP key at
:< http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit >
Fingerprint=0x{6E3E_DB8C_2E8C_4248_62B2_FE29_08EE_CF0A_3629_E954}
:< http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=superbiskit&fingerprint=on >
"By God's Grace I am a Christian man, by my actions a great sinner."
--The Way of a Pilgrim, R. M. French [tr.]
Potentially Viral Software is any software for which you are not allowed
to examine the source.  Do not buy or use Potentially Viral Software!
<---.----!----.----!----.----!----.----!----.----!----.----!----.---->


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Making GDBM [ a long story ]

[Charles S. Wilson]

Note that normally, you don't have to specify "--with-this" or 
"--without-that".  If you have "this" installed, configure will 
automatically build with "this".  If you don't have "that" installed, 
configure will detect the absence and build without "that".

So, since you have postgres installed, Xemacs finds and uses it. 
Mystery #2 solved.  Now, about mystery #1...


> checking for pgsql/libpq-fe.h... no
> checking for postgresql/libpq-fe.h... yes
> checking for PQconnectdb in -lpq... yes
>     Defining HAVE_POSTGRESQL
> checking for PQconnectStart in -lpq... yes
> ! *** Even though I didn't request --with-database=postgresql !


[snip]

> checking for esd-config... no
>     xemacs will be linked with "miscplay.o"
> ! *** THIS IS GOING TO BE ANOTHER PROBLEM *** !


Looks like a mistake in the XEmacs 21.5 series.  Many times the linux 
folks put in a change that causes regression failures like this -- 
especially on cygwin.

> . . . .
> AND FINALLY
> . . . .
> checking for database support
> checking for ndbm.h... no
> Error: Required DBM support cannot be provided.
> :[S!] Bash $


Well, since
   (a)/usr/include/ndbm.h DOES exist (if you've installed the gdbm 
package) and
   (b) I and many others HAVE successfully built XEmacs with gdbm 
support on cygwin in the past (21.4.3 and prior)

This again looks like some sort of regression failure in XEmacs' 
configure script.


> Aha! Maybe I need to build it locally {I thought}, so - get the source 
> and . . . .


This should never be necessary.  If a package has been ported and 
included in the official dist, then it should work.  If it doesn't, then 
it's a bug -- either in the "official" package or the client code you're 
trying to build.  You shouldn't need to go rebuilding stuff on your own 
-- unless you're a glutton for punishment.


> :[S!] Bash $ ../configure --target=i686-pc-cygwin \
>  > --without-x \
>  > --with-gnu-ld \
>  > --exec-prefix=/usr/local/i686-pc-cygwin/
[snip]
> creating Makefile
> creating autoconf.h
> :[S!] Bash $ make
> /bin/sh ../libtool --mode=compile /usr/bin/gcc -mcygwin -c   -I. -I.. -O 
> ../dbminit.c
> ../libtool: Can't open ../libtool: No such file or directory
> make: *** [dbminit.lo] Error 2


Well, it looks like you're building gdbm from the official GNU source. 
AFAIRC, gdbm *does* build OOB on cygwin -- if all you want is the static 
lib.  Why didn't you use the cygwin-patched source from sourceware? 
Also, I *vaugely* remember something about the permissions in the 
official GNU tarball on "litool" not being executable -- if you're using 
CYGWIN=ntsec.  But I could be mistaken.


> SO, obviously I should do something differently.  What?


Well, w.r.t. building gdbm, I'm not sure.  "It works for me"(tm). 
However, with regards to XEmacs, I'd try to track down in the XEmacs 
configure script exactly *WHY* it claims that ndbm.h is missing, and 
take it to the xemacs-nt mailing list.

--Chuck
cygwin-gdbm maintainer



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Making GDBM [ a long story ]

[David A. Cobb]

At 7/14/01 10:55 PM (Saturday), Charles S. Wilson wrote:
[snip]

>>checking for esd-config... no
>>     xemacs will be linked with "miscplay.o"
>>! *** THIS IS GOING TO BE ANOTHER PROBLEM *** !
>
>
>Looks like a mistake in the XEmacs 21.5 series.  Many times the linux 
>folks put in a change that causes regression failures like this -- 
>especially on cygwin.

Sound is a problem all the time in Xemacs.  I probably need to 
--with-sound=native, or something similar.


>>. . . .
>>AND FINALLY
>>. . . .
>>checking for database support
>>checking for ndbm.h... no
>>Error: Required DBM support cannot be provided.
>>:[S!] Bash $
>
>
>Well, since
>   (a)/usr/include/ndbm.h DOES exist (if you've installed the gdbm 
> package) and
>   (b) I and many others HAVE successfully built XEmacs with gdbm support 
> on cygwin in the past (21.4.3 and prior)
>
>This again looks like some sort of regression failure in XEmacs' configure 
>script.

  Maybe having to do with /where/ the configure script looks for the 
ndbm?  I wasn't planning to dive right into the wonders of configure, but I 
guess now is as good a time as any.



>>Aha! Maybe I need to build it locally {I thought}, so - get the source 
>>and . . . .


>This should never be necessary.  If a package has been ported and included 
>in the official dist, then it should work.  If it doesn't, then it's a bug 
>-- either in the "official" package or the client code you're trying to 
>build.  You shouldn't need to go rebuilding stuff on your own -- unless 
>you're a glutton for punishment.

I'm _not_!



>>:[S!] Bash $ ../configure --target=i686-pc-cygwin \
>>  > --without-x \
>>  > --with-gnu-ld \
>>  > --exec-prefix=/usr/local/i686-pc-cygwin/
>[snip]
>>creating Makefile
>>creating autoconf.h
>>:[S!] Bash $ make
>>/bin/sh ../libtool --mode=compile /usr/bin/gcc -mcygwin -c   -I. -I.. -O 
>>../dbminit.c
>>../libtool: Can't open ../libtool: No such file or directory
>>make: *** [dbminit.lo] Error 2
>
>
>Well, it looks like you're building gdbm from the official GNU source. 
>AFAIRC, gdbm *does* build OOB on cygwin -- if all you want is the static 
>lib.  Why didn't you use the cygwin-patched source from sourceware? Also, 
>I *vaugely* remember something about the permissions in the official GNU 
>tarball on "litool" not being executable -- if you're using 
>CYGWIN=ntsec.  But I could be mistaken.

Nope!  The only source I have is what I downloaded from Cygwin.  I'm on a 
Win98se machine so there ain't no 'ntsec.'  I also have read various 
negative things about libtool on Cygwin, but I didn't know what they were 
talking about.


I will (also) check with Xemacs-Nt.



David A. Cobb, Software Engineer, Public Access Advocate, All around nice guy.
Get my PGP key at
:< http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit >
Fingerprint=0x{6E3E_DB8C_2E8C_4248_62B2_FE29_08EE_CF0A_3629_E954}
:< http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=superbiskit&fingerprint=on >
"By God's Grace I am a Christian man, by my actions a great sinner."
--The Way of a Pilgrim, R. M. French [tr.]
Potentially Viral Software is any software for which you are not allowed
to examine the source.  Do not buy or use Potentially Viral Software!
<---.----!----.----!----.----!----.----!----.----!----.----!----.---->


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/