GNU bug report logs - #25377
No INSTALL in git sources

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 25377 in the body.
You can then email your comments to 25377 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: jean-christophe manciot <actionmystique <at> gmail.com>
To: bug-sed <at> gnu.org
Subject: No INSTALL in git sources
Date: Fri, 6 Jan 2017 14:24:23 +0100

[Message part 1 (text/plain, inline)]

sed sources from git://git.sv.gnu.org/sed

I could not find any autogen.sh nor configure.
All the usual tools trigger error(s):

git-sed# export ACLOCAL_AMFLAGS="-I m4"
git-sed# autoreconf -v --install
autoreconf: Entering directory `.'
autoreconf: running: autopoint
Copying file ABOUT-NLS
...
Copying file po/remove-potcdate.sin
autoreconf: running: aclocal
sh: 1: build-aux/git-version-gen: not found
configure.ac:24: error: AC_INIT should be called with package and version
arguments
/usr/share/aclocal-1.15/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
configure.ac:24: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoreconf: aclocal failed with exit status: 1

or:

git-sed# git-reset-clean-pull-checkout.sh master
git-sed# autoconf
sh: 1: build-aux/git-version-gen: not found
configure.ac:22: error: possibly undefined macro: AM_CONFIG_HEADER
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:24: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.ac:26: error: possibly undefined macro: AM_SILENT_RULES
configure.ac:30: error: possibly undefined macro: AM_PROG_CC_C_O
configure.ac:105: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION
configure.ac:106: error: possibly undefined macro: AM_GNU_GETTEXT
configure.ac:116: error: possibly undefined macro: AM_CONDITIONAL

How are we supposed to build configure?

-- 
Jean-Christophe

[Message part 2 (text/html, inline)]

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: jean-christophe manciot <actionmystique <at> gmail.com>, 25377 <at> debbugs.gnu.org
Subject: Re: bug#25377: No INSTALL in git sources
Date: Fri, 6 Jan 2017 18:08:03 -0500

tag 25377 notabug
thanks

Hello,

On 01/06/2017 08:24 AM, jean-christophe manciot wrote:
> sed sources from git://git.sv.gnu.org/sed
> 
> I could not find any autogen.sh nor configure.
[...]
> How are we supposed to build configure?

When building from git, the './bootstrap' script should be used
(it is similar to but more elaborate than just 'autogen.sh' or
'autoreconf -if').
Running 'bootstrap' will also create the INSTALL file.

This is explained in README-hacking file (since building directly from
git is considered more advanced, e.g. for 'hackers').

I do notice that the plain README file does refer to the non-existing
INSTALL file (which does exist if built from tarball).

I'll add a small patch to improve it (leaving this bug open until I do).

regards,
 - assaf

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: jean-christophe manciot <actionmystique <at> gmail.com>, 25377 <at> debbugs.gnu.org
Subject: Re: bug#25377: No INSTALL in git sources
Date: Fri, 6 Jan 2017 23:08:42 -0500

[Message part 1 (text/plain, inline)]

> On 01/06/2017 08:24 AM, jean-christophe manciot wrote:
> 
> I do notice that the plain README file does refer to the non-existing
> INSTALL file (which does exist if built from tarball).
> 
> I'll add a small patch to improve it (leaving this bug open until I do).

Here's a suggestion for updating README.

Comments welcomed,
 - assaf

[0001-doc-improve-README.patch (application/octet-stream, attachment)]

[Message part 3 (text/plain, inline)]

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

From: Jim Meyering <jim <at> meyering.net>
To: Assaf Gordon <assafgordon <at> gmail.com>
Cc: 25377 <at> debbugs.gnu.org, jean-christophe manciot <actionmystique <at> gmail.com>
Subject: Re: bug#25377: No INSTALL in git sources
Date: Fri, 13 Jan 2017 20:59:04 -0800

On Fri, Jan 6, 2017 at 8:08 PM, Assaf Gordon <assafgordon <at> gmail.com> wrote:
>
>> On 01/06/2017 08:24 AM, jean-christophe manciot wrote:
>>
>> I do notice that the plain README file does refer to the non-existing
>> INSTALL file (which does exist if built from tarball).
>>
>> I'll add a small patch to improve it (leaving this bug open until I do).
>
> Here's a suggestion for updating README.
>
> Comments welcomed,

What do you think of using this paragraph from coreutils' README?

If you obtained this file as part of a "git clone", then see the
README-hacking file.  If this file came to you as part of a tar archive,
then see the file INSTALL for compilation and installation instructions.

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

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: 25377 <at> debbugs.gnu.org, jean-christophe manciot <actionmystique <at> gmail.com>
Subject: Re: bug#25377: No INSTALL in git sources
Date: Mon, 16 Jan 2017 21:54:06 -0500

tag 25377 fixed
close 25377
thanks

> On Jan 13, 2017, at 23:59, Jim Meyering <jim <at> meyering.net> wrote:
> 
> What do you think of using this paragraph from coreutils' README?


Indeed much better.

I pushed it here:
 http://git.savannah.gnu.org/cgit/sed.git/commit/?id=2ecd4e1d919b9b728b4b18696e0682496294dc13


regards,
 - assaf
 

Previous Next

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