Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] cmake is not building anymore
Date: Mon, 20 Mar 2017 14:47:12 +0200	[thread overview]
Message-ID: <1490014032.19767.99.camel@linux.intel.com> (raw)
In-Reply-To: <87lgs6qmwj.fsf@dell.be.48ers.dk>

On Wed, 2017-03-15 at 21:56 +0100, Peter Korsgaard wrote:
> > > > > > "Andy" == Andy Shevchenko <andriy.shevchenko@linux.intel.com
> > > > > > > writes:
> 
> Hi,
> 
> ?>> ? rm -r output/build/host-cmake*
> ?>> ? make host-cmake
> ?>>?
> ?>> Does that work?
> 
> ?> Yes, it does with `rm -rf` (I tried before with make host-cmake-
> clean-
> ?> for-reconfigutre, that didn't help)
> 
> Ok, that is good at least. So I guess the solution is to convince
> cmake
> to build its embedded libarchive copy without openssl support, or to
> move to system libraries and add host-libarchive to the dependencies.

So, is anyone going to fix it?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-03-20 12:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 14:56 [Buildroot] cmake is not building anymore Andy Shevchenko
2017-03-13 15:54 ` Andy Shevchenko
2017-03-15  1:02   ` Carlos Santos
2017-03-15 15:10     ` Andy Shevchenko
2017-03-15 16:05       ` Carlos Santos
2017-03-15 17:23         ` Andy Shevchenko
2017-03-15 18:55           ` Carlos Santos
2017-03-15 19:44             ` Andy Shevchenko
2017-03-15 19:49               ` Baruch Siach
2017-03-15 20:04                 ` Andy Shevchenko
2017-03-15 20:56                   ` Peter Korsgaard
2017-03-20 12:47                     ` Andy Shevchenko [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=1490014032.19767.99.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --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