All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1] package/speechd: fix gettext version mismatch
Date: Mon, 27 Feb 2023 22:41:13 +0100	[thread overview]
Message-ID: <20230227224113.0eb16910@gmx.net> (raw)
In-Reply-To: <PH1P110MB16030F6BC0949CA7477F0B829FAF9@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>

Hello Vincent,

On Mon, 27 Feb 2023 21:17:40 +0000, Vincent Fazio <vfazio@xes-inc.com> wrote:

> Peter,
>
> > -----Original Message-----
> > From: buildroot <buildroot-bounces@buildroot.org> On Behalf Of Peter
> > Seiderer
> > Sent: Monday, February 27, 2023 3:08 PM
> > To: buildroot@buildroot.org
> > Subject: [External] - [Buildroot] [PATCH v1] package/speechd: fix gettext
> > version mismatch
> >
> > - fix gettext version mismatch in case of BR2_SYSTEM_ENABLE_NLS and
> >   BR2_PACKAGE_PROVIDES_HOST_GETTEXT="host-gettext-gnu" by setting
> >   SPEECHD_GETTEXTIZE
> >
> > Fixes:
> >
> >   -
> > http://autobuild.buildroot.net/results/283333290c5adb48d0c6e592b3261992
> > 537f92d3
> >
> >   Making all in po
> >   *** error: gettext infrastructure mismatch: using a Makefile.in.in from
> > gettext version 0.19 but the autoconf macros are from gettext version 0.20
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> >  package/speechd/speechd.mk | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/package/speechd/speechd.mk b/package/speechd/speechd.mk
> > index dee94a6752..ec62980986 100644
> > --- a/package/speechd/speechd.mk
> > +++ b/package/speechd/speechd.mk
> > @@ -11,6 +11,7 @@ SPEECHD_LICENSE_FILES = COPYING.GPL-2
> > COPYING.GPL-3 COPYING.LGPL  SPEECHD_INSTALL_STAGING = YES  #
> > speechd source code is released without configure script
> > SPEECHD_AUTORECONF = YES
> > +SPEECHD_GETTEXTIZE = YES
>
> I wonder if this will actually be necessary after https://patchwork.ozlabs.org/project/buildroot/list/?series=343029
>
> Can you test to see if it's still a problem after applying the series and using autopoint?

Yes, already on my ToDo list ;-), in the meantime (and for master branch/2023.2) this minimal patch...

> Otherwise I'll try to find some time to test your patch with autopoint to see if there's still an issue.

Thanks for taking a look at it...

Regards,
Peter

>
> >  SPEECHD_DEPENDENCIES = host-pkgconf dotconf libglib2 libsndfile
> > SPEECHD_CONF_ENV = ac_cv_prog_HELP2MAN=""
> >  SPEECHD_CONF_OPTS = --without-kali
> > --
> > 2.39.2
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot@buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
> > CAUTION: This email originated from outside of the organization. Do not click
> > links or open attachments unless you recognize the sender and know the
> > content is safe.
>

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-02-27 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 21:17 [Buildroot] [PATCH v1] package/speechd: fix gettext version mismatch Vincent Fazio
2023-02-27 21:41 ` Peter Seiderer [this message]
2023-02-27 21:56   ` Peter Seiderer
  -- strict thread matches above, loose matches on Subject: below --
2023-02-27 21:08 Peter Seiderer
2023-03-09 20:24 ` Arnout Vandecappelle

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=20230227224113.0eb16910@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=vfazio@xes-inc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.