From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libconfuse: switch to the new upstream
Date: Fri, 18 Jul 2014 00:46:15 +0200 [thread overview]
Message-ID: <20140717224615.GG3737@free.fr> (raw)
In-Reply-To: <1405549965-22539-1-git-send-email-yann.morin.1998@free.fr>
Thomas, All,
On 2014-07-17 00:32 +0200, Yann E. MORIN spake thusly:
> libconfuse is being migrated to github (see http://www.nongnu.org/confuse/)
> So, just follow suite.
>
> Needs a bit of a hack so gettextize + autoreconf does not step on each
> other's toes. See comment in the patch.
[--SNIP--]
OK, so this bump is causing a bunch of autobuild failures:
http://autobuild.buildroot.org/?reason=libconfuse-V2_7
Some of them are due to a problem while either gettextizing or
autoreconfiguring the package.
Thomas was able to reproduce this build failure:
http://autobuild.buildroot.org/results/f60/f6089c90d4f0ba579725ac834d8ac43b839bbc3b/
However, I was not able to reproduce it; it builds fine for me, in a
Debian Squeeze 32-bit chroot.
I'm lost.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-07-17 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 22:32 [Buildroot] [PATCH] package/libconfuse: switch to the new upstream Yann E. MORIN
2014-07-16 22:34 ` Yann E. MORIN
2014-07-16 22:40 ` Arnout Vandecappelle
2014-07-17 6:38 ` Alvaro Gamez
2014-07-17 7:58 ` Thomas Petazzoni
2014-07-17 22:46 ` Yann E. MORIN [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=20140717224615.GG3737@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.