Hi Hans,

Em Sun, 14 Dec 2014 12:40:58 +0100
Hans Verkuil <hverk...@xs4all.nl> escreveu:

> On 12/14/2014 12:26 PM, Mauro Carvalho Chehab wrote:
> > This is an automatic generated email to let you know that the following 
> > patch were queued at the 
> > http://git.linuxtv.org/cgit.cgi/v4l-utils.git tree:
> > 
> > Subject: Update INSTALL instructions and add a script to configure
> > Author:  Mauro Carvalho Chehab <mche...@osg.samsung.com>
> > Date:    Sun Dec 14 09:26:20 2014 -0200
> > 
> > Just running autoconf -vfi will override some needed configs
> > at libdvbv5-po. So, add a bootstrap.sh script and document it.
> 
> FYI: after running ./bootstrap.sh I get the diff shown below if I run 'git 
> diff'.
> That suggests that there are autogenerated files in the git repo that do
> not belong there.

Yes, I'm aware of that. The bootstrap.sh is for now a hack to allow
building it with different versions of gettext. I suspect that there are
better ways of doing that, so I prefer to not remove the files generated
by gettextize for now.

> 
> I also see following message twice when running bootstrap:
> 
> -------
> Please create libdvbv5-po/Makevars from the template in 
> libdvbv5-po/Makevars.template.
> You can then remove libdvbv5-po/Makevars.template.
> 
> Please run 'aclocal -I m4' to regenerate the aclocal.m4 file.
> You need aclocal from GNU automake 1.9 (or newer) to do this.
> Then run 'autoconf' to regenerate the configure file.
> 
> You might also want to copy the convenience header file gettext.h
> from the /usr/share/gettext directory into your package.
> It is a wrapper around <libintl.h> that implements the configure --disable-nls
> option.
> 
> Press Return to acknowledge the previous three paragraphs.

This is also due to the hack of running gettextize at
bootstrap.sh.

We might add a >/dev/null to avoid showing such useless messages,
although I'm trying to see if I can find a better way to implement it.

Regards,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to