All of 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: Wed, 15 Mar 2017 19:23:33 +0200	[thread overview]
Message-ID: <1489598613.19767.6.camel@linux.intel.com> (raw)
In-Reply-To: <372249453.14780914.1489593932103.JavaMail.zimbra@datacom.ind.br>

On Wed, 2017-03-15 at 13:05 -0300, Carlos Santos wrote:
> > From: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
> > To: "Carlos Santos" <casantos@datacom.ind.br>
> > Cc: "buildroot" <buildroot@busybox.net>
> > Sent: Wednesday, March 15, 2017 12:10:57 PM
> > Subject: Re: [Buildroot] cmake is not building anymore
> > On Tue, 2017-03-14 at 22:02 -0300, Carlos Santos wrote:
> > $ git clean -xdf
> > # I suppose you agree this is more stronger than make clean
> > 
> > $ make defconfig
> > $ make
> > 
> > --- 8< --- 8< ---
> > 
> > [ 65%] Linking C static library libcmcurl.a
> > 
> > In file included from .../output/build/host-cmake-
> > 3.6.3/Utilities/cmlibarchive/libarchive/archive_write_set_format_zip
> > .c:5
> > 2:0:
> > .../output/build/host-cmake-
> > 3.6.3/Utilities/cmlibarchive/libarchive/archive_cryptor_private.h:10
> > 7:17
> > : error: field ?ctx? has incomplete type
> > ??EVP_CIPHER_CTX ctx;
> > ?????????????????^~~
> > --- 8< --- 8< ---
> > 
> > 100% reproducible
> 
> If you use "make BR2_JLEVEL=1" the compilation will stop at the first
> error and it will be easier to identify the cause.

This is *first* error.

>  I guess you don't have the openssl-dev package installed on the host
> machine neither built host-openssl in buildroot, since EVP_CIPHER_CTX
> is defined in openssl/ossl_typ.h.

It is installed.

$ dpkg -l \*ssl-dev
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-
aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name???????????????????Version??????????Architecture?????Description
+++-======================-================-================-
==================================================
...
ii??libcurl4-openssl-dev:a 7.52.1-3?????????amd64????????????development 
files and documentation for libcurl (O
...
ii??libssl-dev:amd64???????1.1.0e-1?????????amd64????????????Secure
Sockets Layer toolkit - development files

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

  reply	other threads:[~2017-03-15 17:23 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 [this message]
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

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=1489598613.19767.6.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.