From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Possible libarchive.mk issue
Date: Sat, 23 May 2015 11:59:36 +0200 [thread overview]
Message-ID: <20150523095936.GA19247@free.fr> (raw)
In-Reply-To: <CALoSW64Xv5-_T3eqHG_kPzv1JsGQNcyPmLG_yBX56vMt9+1bsQ@mail.gmail.com>
Nimai, All,
On 2015-05-22 18:41 -0400, Nimai Mahajan spake thusly:
> Just wanted to get this resolved before the official 2015.05 release.
> Is there any reason libarchive has LIBARCHIVE_CONF_OPTS =
> --without-lzma hard coded/defined without if/else's?
Because nobody needed it so far. ;-)
> We use libarchive
> with xz on our project and don't know how to pre patch these
> package/*.mk files before a build so was wondering if this change
> could be made now. My assumption is that this was an oversight and
> guessing it should be like this ... will push a patch if so.
>
> ifeq ($(BR2_PACKAGE_XZ),y)
> LIBARCHIVE_DEPENDENCIES += xz
> else
> LIBARCHIVE_CONF_OPTS += --without-lzma
> endif
Yeah, looks sane. Please send a patch.
However, we're in feature-freeze for the up-coming release, only
bug-fixes are accepted, and that would be a new feature, so will not be
in the upcming release, but the next one (~3 months from now).
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:[~2015-05-23 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 22:41 [Buildroot] Possible libarchive.mk issue Nimai Mahajan
2015-05-23 9:59 ` 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=20150523095936.GA19247@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox