From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Still unable to build from tardist due to libgcrypt (and probably more) POTFILES
Date: Thu, 18 Apr 2013 23:16:38 +0400 [thread overview]
Message-ID: <20130418231638.013fc7fb@opensuse.site> (raw)
In-Reply-To: <20130417214902.52abf063@opensuse.site>
В Wed, 17 Apr 2013 21:49:02 +0400
Andrey Borzenkov <arvidjaar@gmail.com> пишет:
> I do not quite understand how po/POTFILES are maintained but they refer
> to files that are not distributed, so rebuild later fails.
>
OK, I fixed out package to avoid attempt to rebuild pot files.
> It is not just one or two files which is why I do not know how to fix
> it. Here is full list of files that are present in POTFILES but missing
> in tarball:
> util/spkmodem-recv.c
I guess this needs patch below. spkmodem-recv.c is documented in
grub.texi, so it should be available in tarball.
diff --git a/ChangeLog b/ChangeLog
index eb92ae4..c5db731 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2013-04-18 Andrey Borzenkov <arvidjaar@gmail.com>
+
+ * conf/Makefile.extra-dist: Add util/spkmodem-recv.c, it is required
+ if user wants to use spkmodem output.
+
2013-04-17 Vladimir Serbinenko <phcoder@gmail.com>
* util/grub-mkrescue.in: Add GPT for EFI boot.
diff --git a/conf/Makefile.extra-dist b/conf/Makefile.extra-dist
index 2e36500..b21039a 100644
--- a/conf/Makefile.extra-dist
+++ b/conf/Makefile.extra-dist
@@ -38,6 +38,7 @@ EXTRA_DIST += grub-core/lib/LzmaDec.c
EXTRA_DIST += BUGS
EXTRA_DIST += util/i386/efi/grub-dumpdevtree
EXTRA_DIST += util/import_gcrypth.sed
+EXTRA_DIST += util/spkmodem-recv.c
EXTRA_DIST += m4/gnulib-cache.m4
EXTRA_DIST += m4/glibc2.m4
prev parent reply other threads:[~2013-04-18 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 17:49 Still unable to build from tardist due to libgcrypt (and probably more) POTFILES Andrey Borzenkov
2013-04-18 19:16 ` Andrey Borzenkov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130418231638.013fc7fb@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-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.
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 NNTP newsgroup(s).