unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Romel R. Sandoval Palomo" <romel@lavabit.com>
To: tantalum <tantalum@online.de>
Cc: guile-user@gnu.org
Subject: Re: Guile module for sqlite
Date: Mon, 17 May 2010 20:57:08 -0500	[thread overview]
Message-ID: <1274147828.1966.0.camel@romel-compaq> (raw)
In-Reply-To: <4BEF34E5.4050705@online.de>

Thank you, its great, unfortunately to me, I'm targeting 
guile 2.0 (1.9.10) and the released guile-dbi (2.1.2) use the 
deprecated guile/gh.h

I found guile-dbi developers remove that dependency on its SVN
repository, but I failed to build because I failed to generate 
configure script using autogen.sh

I got this while running guile-dbi autogen.sh:

{{{
automake (GNU automake) 1.11
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
Creating aclocal.m4: aclocal  -I ac-helpers
automake --add-missing --copy --foreign

* * * warning: possible errors while running automake - check autogen.err

Creating configure...
configure: WARNING: unrecognized options: --enable-maintainer-mode
/configure: line 2122: syntax error near unexpected token `$PACKAGE,$VERSION,bug-guile@gnu.org'
/configure: line 2122: `AM_INIT_AUTOMAKE($PACKAGE,$VERSION,bug-guile@gnu.org)'
}}}

My autogen.err:

{{{
aclocal: couldn't open directory `ac-helpers': No existe el fichero ó directorio
configure.ac: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal).
src/Makefile.am:35: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:35:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:35:   to `configure.ac' and run `aclocal' and `autoconf' again.
src/Makefile.am:35:   If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
src/Makefile.am:35:   its definition is in aclocal's search path.
/usr/share/automake-1.11/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define `am__fastdepCC' is to add `AC_PROG_CC'
/usr/share/automake-1.11/am/depend2.am:   to `configure.ac' and run `aclocal' and `autoconf' again.
/usr/share/automake-1.11/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define `AMDEP' is to add one of the compiler tests
/usr/share/automake-1.11/am/depend2.am:     AC_PROG_CC, AC_PROG_CXX, AC_PROG_CXX, AC_PROG_OBJC,
/usr/share/automake-1.11/am/depend2.am:     AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.11/am/depend2.am:   to `configure.ac' and run `aclocal' and `autoconf' again.
src/test/Makefile.am:28: Libtool library used but `LIBTOOL' is undefined
src/test/Makefile.am:28:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/test/Makefile.am:28:   to `configure.ac' and run `aclocal' and `autoconf' again.
src/test/Makefile.am:28:   If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
src/test/Makefile.am:28:   its definition is in aclocal's search path.
}}}

Could anybody help me with this guilde-dbi configure script generation problem, please?

El dom, 16-05-2010 a las 01:57 +0200, tantalum escribió:
> Hi,
> 
> I did write a guile-dbi module for sqlite3.
> I am using it everyday successfully for basic queries.
> 
> You can find it under: http://thaseph.de/ande/guile-dbd-sqlite3.html
> 
> 
> Hope it helps
> 






  reply	other threads:[~2010-05-18  1:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15 23:57 Guile module for sqlite tantalum
2010-05-18  1:57 ` Romel R. Sandoval Palomo [this message]
2010-05-18  2:53   ` Linas Vepstas
2010-05-18 15:17   ` Linas Vepstas
2010-05-18 19:26     ` [SOLVED] " Romel R. Sandoval Palomo
2010-05-21 11:06       ` Andy Wingo
2010-05-21 22:30         ` Linas Vepstas
2010-05-18 15:14 ` Linas Vepstas
  -- strict thread matches above, loose matches on Subject: below --
2010-05-15 20:24 Romel R. Sandoval Palomo
2010-05-15 20:58 ` Linas Vepstas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1274147828.1966.0.camel@romel-compaq \
    --to=romel@lavabit.com \
    --cc=guile-user@gnu.org \
    --cc=tantalum@online.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).