emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#9851: closed (No configure file in git cloned guil


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#9851: closed (No configure file in git cloned guile despite what README says)
Date: Mon, 07 Nov 2011 12:26:02 +0000

Your message dated Mon, 07 Nov 2011 13:22:37 +0100
with message-id <address@hidden>
and subject line Re: bug#9851: No configure file in git cloned guile despite 
what README says
has caused the debbugs.gnu.org bug report #9851,
regarding No configure file in git cloned guile despite what README says
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
9851: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9851
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- 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



--- End Message ---
--- Begin Message --- Subject: Re: bug#9851: No configure file in git cloned guile despite what README says Date: Mon, 07 Nov 2011 13:22:37 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
On Tue 25 Oct 2011 00:04, Andy Wingo <address@hidden> writes:

> On Mon 24 Oct 2011 23:39, "J. Greg Davidson" <address@hidden> 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/


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]