From: David Pirotte <david@altosw.be>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>, Carlo Zancanaro <carlo@zancanaro.id.au>
Subject: Re: Shepherd release!
Date: Fri, 16 Mar 2018 23:47:24 -0300 [thread overview]
Message-ID: <20180316234724.60e0beb8@capac> (raw)
In-Reply-To: <20180316135546.GA5407@jurong>
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]
Hello,
Though I don't use neither contribute to shepherd, nor guix, guixsd either, I got
curious, because the error message did trigger a bell, so I went on and visited the
source code and here is my few cents :)
> I am already failing in getting the shepherd configured. On a fresh git
> checkout, I do
> autoreconf -vfi
> and obtain the following:
I think it would be better if the tree had the traditional ./autogen.sh
or ./bootstrap, especially because it would contain more then just 'autoreconf -vfi'
(see below)
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal --force -I m4
> aclocal: warning: couldn't open directory 'm4': No such file or directory
Not sure why this happens, I don't see the usual 'AC_CONFIG_MACRO_DIR([m4])'
in the shepherd configure.ac file, maybe someone else has a clue? It's a warning
though, so it might be ok anyway ...
> ...
> configure.ac:17: error: required file 'build-aux/config.rpath' not found
> configure.ac:17: error: required file './ABOUT-NLS' not found
Don't know about the later, but wrt the former, I started to get these errors soon
after I started to contribute to guile-gnome/guile-clutter, and here is what I wrote
in their respective ./autogen.sh
<---- autogen.sh starts here ---->
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
# configure.ac uses the guile.m4 GUILE_FLAGS macro, among others,
# which needs build-aux/config.rpath which is not installed anymore by
# modern version of automake, and without it, this script will raise
# an error. For why it's needed, see the comments wtr in m4/guile.m4.
if [ ! -d "build-aux" ]; then
mkdir build-aux
fi
touch build-aux/config.rpath
autoreconf -vif
echo
echo "Now run ./configure --prefix=/your/prefix."
<---- autogen.sh ends here ---->
> ...
> config.status: creating Makefile
> config.status: error: cannot find input file: `po/Makefile.in.in'
> ...
Here there are two problems:
1- the configure.ac has a tipo
line 86, it has '... po/Makefile.in'
but it should be '... po/Makefile'
2- the po subdir does not have a Makefile.in
HTH,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-17 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 12:44 Shepherd release! Ludovic Courtès
2018-03-16 13:55 ` Andreas Enge
2018-03-17 2:47 ` David Pirotte [this message]
2018-03-19 16:42 ` Ludovic Courtès
2018-03-19 19:14 ` Andreas Enge
2018-03-20 16:31 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180316234724.60e0beb8@capac \
--to=david@altosw.be \
--cc=andreas@enge.fr \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).