From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] cmake is not building anymore
Date: Wed, 15 Mar 2017 22:04:08 +0200 [thread overview]
Message-ID: <1489608248.19767.11.camel@linux.intel.com> (raw)
In-Reply-To: <20170315194910.d5bftkd7vtozqfid@tarshish>
On Wed, 2017-03-15 at 21:49 +0200, Baruch Siach wrote:
> Hi Andy,
>
> On Wed, Mar 15, 2017 at 09:44:00PM +0200, Andy Shevchenko wrote:
> > On Wed, 2017-03-15 at 15:55 -0300, Carlos Santos wrote:
> > > Ouch! Does it build using host-openssl, instead?
> >
> > At least I don't see any folder like that in output/.
> >
> > $ ls -1d output/build/*ssl*
> > ls: cannot access 'output/build/*ssl*': No such file or directory
>
> What Carlos suggests is to build host-openssl manually
>
> ? make host-openssl
>
> and then rerun the cmake build
>
> ? 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)
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-15 20:04 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 [this message]
2017-03-15 20:56 ` Peter Korsgaard
2017-03-20 12:47 ` Andy Shevchenko
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=1489608248.19767.11.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 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.