unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: romel@lavabit.com
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: [SOLVED] Re: Problems building GNU Greg testing framework
Date: Mon, 10 Jan 2011 20:24:00 -0500 (EST)	[thread overview]
Message-ID: <10104.189.148.181.157.1294709040.squirrel@lavabit.com> (raw)
In-Reply-To: <8739p1g5sr.fsf@gnu.org>

Thanks Ludovic,

I delete config.guess and config.sub, then regenerate them and voila.

I see Greg it's very old, Does have Guile DBI project a plan to remove
this dependency or to give some maintenance to Greg? Just curious.

As a side note, in order to build Guile DBI on Guile 1.9.14 I had to
remove a hardcoded -lguile library reference from /src/test/Makefile.am.

Before:
libguile_dbd_test_la_LIBADD = -ldl -lz -lguile

After:
libguile_dbd_test_la_LIBADD = -ldl -lz

Regards,

Romel Sandoval

> Hi!
>
> romel@lavabit.com writes:
>
>> I'm trying to build GNU Greg 1.4 in order to build Guile DBI but when I
>> run ./configure something goes wrong.
>>
>> $ ./configure --prefix $HOME/opt/
>> loading cache ./config.cache
>> checking host system type... Invalid configuration
>> `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized
>
> This means that Greg’s ‘config.guess’ (which originates from
> Autoconf)
> is very, very old, and doesn’t know this architecture, leading to:
>
>> ltconfig: you must specify a host type if you use `--no-verify'
>> Try `ltconfig --help' for more information.
>> configure: error: libtool configure failed
>
> AFAIK Greg has been mostly unmaintained for several years.  Still, you
> could try regenerating the configure machinery with a current Autoconf
> and see what happens.
>
> Thanks,
> Ludo’.
>
>
>






  reply	other threads:[~2011-01-11  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08  1:03 Problems building GNU Greg testing framework romel
2011-01-09 20:50 ` Ludovic Courtès
2011-01-11  1:24   ` romel [this message]
2011-01-11  5:56     ` [SOLVED] " Linas Vepstas
2011-01-23 13:03       ` Andrew Horton

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=10104.189.148.181.157.1294709040.squirrel@lavabit.com \
    --to=romel@lavabit.com \
    --cc=guile-user@gnu.org \
    --cc=ludo@gnu.org \
    /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).