Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libcurl: packages that use it need mmu also
Date: Thu, 14 Feb 2013 10:50:56 -0300	[thread overview]
Message-ID: <511CEBC0.60009@zacarias.com.ar> (raw)
In-Reply-To: <20130214144713.632dcc63@skate>

On 02/14/2013 10:47 AM, Thomas Petazzoni wrote:
> I don't agree. I believe the libcurl package should not depend on
> BR2_USE_MMU instead. I have a patch that I'll send as a reply to this
> e-mail.

Cool, i don't have much time to look into it so i went the fast route.
Careful though, 7.28.1 is security vulnerable and a bump to 7.29.0 is
necessary.
That said the bump doesn't build since it doesn't like macro definitions
in CFLAGS, it's probably safer to just patch the security vulnerability
since moving over the largefile defs to CPPFLAGS isn't probably clean at
this point in the upcoming release.
Regards.

  parent reply	other threads:[~2013-02-14 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 13:03 [Buildroot] [PATCH 1/2] gesftpserver: needs mmu Gustavo Zacarias
2013-02-14 13:03 ` [Buildroot] [PATCH 2/2] libcurl: packages that use it need mmu also Gustavo Zacarias
2013-02-14 13:47   ` Thomas Petazzoni
2013-02-14 13:50     ` [Buildroot] [PATCH] libcurl: re-enable on non-MMU platforms Thomas Petazzoni
2013-02-17 22:02       ` Peter Korsgaard
2013-02-14 13:50     ` Gustavo Zacarias [this message]
2013-02-17 21:57 ` [Buildroot] [PATCH 1/2] gesftpserver: needs mmu Peter Korsgaard

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=511CEBC0.60009@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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