GNU bug report logs - #9851
No configure file in git cloned guile despite what README says

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 9851 in the body.
You can then email your comments to 9851 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "J. Greg Davidson" <jgd <at> well.com>
To: bug-guile <at> gnu.org
Subject: No configure file in git cloned guile despite what README says
Date: Sat, 22 Oct 2011 20:35:51 -0700 (PDT)

Dear Guile Maintainers:

I used the git command
  git clone git://git.sv.gnu.org/guile.git
from the guile webpage
   https://www.gnu.org/software/guile/download.html
and got a nice directory with a README file which
tells me to run ./configure which does not exist.
I tried to create one with autoconf but it gave lots
of error messages.

Please revise the README file (or provide a traditional
INSTALL file) with correct installation information.

Thanks,

_Greg

Message #8 received at 9851 <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: "J. Greg Davidson" <jgd <at> well.com>
Cc: 9851 <at> debbugs.gnu.org
Subject: Re: bug#9851: No configure file in git cloned guile despite what
	README says
Date: Mon, 24 Oct 2011 02:43:31 -0400

"J. Greg Davidson" <jgd <at> well.com> writes:
> I used the git command
>   git clone git://git.sv.gnu.org/guile.git
> from the guile webpage
>    https://www.gnu.org/software/guile/download.html
> and got a nice directory with a README file which
> tells me to run ./configure which does not exist.

The README for those who have downloaded a release tarball.  When
downloading a development version from git, you must generate the build
system yourself using recent versions of the autotools.  See the HACKING
file for details.

    Best,
     Mark

Message #11 received at 9851 <at> debbugs.gnu.org (full text, mbox):

From: "J. Greg Davidson" <jgd <at> well.com>
To: Mark H Weaver <mhw <at> netris.org>
Cc: 9851 <at> debbugs.gnu.org
Subject: Re: bug#9851: No configure file in git cloned guile despite what
	README says
Date: Mon, 24 Oct 2011 14:39:14 -0700

Thank you for pointing me to the HACKING file.  I hope
that someone will fix the README to reference it.  It would
also be appropriate to correct the HACKING file which says

"Then you must run the autogen.sh script, as described below."

but I do not recognize anything "below" as explaining autogen.sh
further - in fact there is no later mention of it!  Fortunately,
"./autogen.sh" did the trick with none of the scary configuration
"described below" being necessary.

I do not mean my feedback to be snarky but rather to assist
you in your commitment to have the latest Guile available to
testers beyond the development team.

Well, autogen.sh and configure both seem happy, but when I try
to run make I get:

  CC     libguile_2.2_la-scmsigs.lo
scmsigs.c:155:1: error: static declaration of 'GC_get_suspend_signal'
follows non-static declaration
/usr/local/include/gc/gc.h:1067:22: note: previous declaration of
'GC_get_suspend_signal' was here
make[3]: *** [libguile_2.2_la-scmsigs.lo] Error 1
make[3]: Leaving directory `/usr/local/src/guile-2.0.3/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/local/src/guile-2.0.3/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/guile-2.0.3'
make: *** [all] Error 2

Perhaps my libgc is too new (7.3alpha1)  I'll fiddle around and
see what works.

Thanks,

_Greg


On Mon, 2011-10-24 at 02:43 -0400, Mark H Weaver wrote:
> "J. Greg Davidson" <jgd <at> well.com> writes:
> > I used the git command
> >   git clone git://git.sv.gnu.org/guile.git
> > from the guile webpage
> >    https://www.gnu.org/software/guile/download.html
> > and got a nice directory with a README file which
> > tells me to run ./configure which does not exist.
> 
> The README for those who have downloaded a release tarball.  When
> downloading a development version from git, you must generate the build
> system yourself using recent versions of the autotools.  See the HACKING
> file for details.
> 
>     Best,
>      Mark

Message #14 received at 9851 <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: jgd <at> well.com
Cc: Mark H Weaver <mhw <at> netris.org>, 9851 <at> debbugs.gnu.org
Subject: Re: bug#9851: No configure file in git cloned guile despite what
	README says
Date: Tue, 25 Oct 2011 00:04:25 +0200

On Mon 24 Oct 2011 23:39, "J. Greg Davidson" <jgd <at> well.com> writes:

> Perhaps my libgc is too new (7.3alpha1)  I'll fiddle around and
> see what works.

That could be.  I'll have to update my checkout and see what happens.

Apologies for the mess!

Andy
-- 
http://wingolog.org/

Message #19 received at 9851-done <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: jgd <at> well.com
Cc: Mark H Weaver <mhw <at> netris.org>, 9851-done <at> debbugs.gnu.org
Subject: Re: bug#9851: No configure file in git cloned guile despite what
	README says
Date: Mon, 07 Nov 2011 13:22:37 +0100

On Tue 25 Oct 2011 00:04, Andy Wingo <wingo <at> pobox.com> writes:

> On Mon 24 Oct 2011 23:39, "J. Greg Davidson" <jgd <at> well.com> writes:
>
>> Perhaps my libgc is too new (7.3alpha1)  I'll fiddle around and
>> see what works.
>
> That could be.  I'll have to update my checkout and see what happens.

I have tried with git libgc, and cannot reproduce this issue.  I think
it must be that you ran configure with an old libgc, then updated, then
tried to build again without reconfiguring.  Assuming this is the case,
I'm closing this bug.

Regards,

Andy
-- 
http://wingolog.org/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.