Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Valentin Popa <valentin.popa@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-commits@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Valentin Popa : nettle: add nettle to oe-core
Date: Thu, 15 May 2014 17:49:14 +0300	[thread overview]
Message-ID: <5374D3EA.6000309@intel.com> (raw)
In-Reply-To: <20140515140723.GF2433@jama>

On 05/15/2014 05:07 PM, Martin Jansa wrote:
> On Thu, May 15, 2014 at 04:25:50PM +0300, Valentin Popa wrote:
>> On 05/15/2014 02:13 PM, Martin Jansa wrote:
>>> On Tue, May 06, 2014 at 05:01:05PM +0000, git@git.openembedded.org wrote:
>>>> Module: openembedded-core.git
>>>> Branch: master
>>>> Commit: e0e5eaee72e49c01e76d56cd03fbfb3e20febbb0
>>>> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=e0e5eaee72e49c01e76d56cd03fbfb3e20febbb0
>>>>
>>>> Author: Valentin Popa <valentin.popa@intel.com>
>>>> Date:   Mon Apr 28 17:28:19 2014 +0300
>>>>
>>>> nettle: add nettle to oe-core
>>>>
>>>> Newer versions of gnutls depends on nettle.
>>> Any idea why it fails in some builds like this:
>>>
>>> | checking whether ln -s works... yes
>>> | checking build system compiler gcc ... no
>>> | configure: error: Specified CC_FOR_BUILD doesn't seem to work
>>> | Configure failed. The contents of all config.log files follows to aid debugging
>>> | ERROR: oe_runconf failed
>>> | WARNING: exit code 1 from a shell command.
>>>
>>> config.log:
>>> configure:4412: checking build system compiler gcc
>>> configure:4425: gcc  conftest.c
>>> conftest.c: In function 'main':
>>> conftest.c:4:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default]
>>>      exit(0);
>>>      ^
>>> configure:4428: $? = 0
>>> /OE//nettle/2.7.1-r0/nettle-2.7.1/configure: line 4430: ./a.out: cannot execute binary file
>>> /OE//nettle/2.7.1-r0/nettle-2.7.1/configure: line 4430: ./b.out: No such file or directory
>>> /OE//nettle/2.7.1-r0/nettle-2.7.1/configure: line 4430: ./a.exe: No such file or directory
>>> /OE//nettle/2.7.1-r0/nettle-2.7.1/configure: line 4430: ./a_out.exe: No such file or directory
>>> /OE//nettle/2.7.1-r0/nettle-2.7.1/configure: line 4430: ./conftest: No such file or directory
>>> configure:4435: result: no
>>> configure:4440: error: Specified CC_FOR_BUILD doesn't seem to work
>>>
>>> export CC_FOR_BUILD="gcc "
>>>
>> I suspect the crosscompiler; for what arch&machine does this fail?
> cortexa8 and it's the only recipe failing like this (even after
> cleansstate) so I don't expect it to be something as simple as
> nonworking cross compiler.

I've just built nettle for beaglebone with no issue (on master).

>
>>>> Signed-off-by: Valentin Popa <valentin.popa@intel.com>
>>>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>>>>
>>>> ---
>>>>
>>>>    meta/recipes-support/nettle/nettle_2.7.1.bb | 24 ++++++++++++++++++++++++
>>>>    1 file changed, 24 insertions(+)
>>>>
>>>> diff --git a/meta/recipes-support/nettle/nettle_2.7.1.bb b/meta/recipes-support/nettle/nettle_2.7.1.bb
>>>> new file mode 100644
>>>> index 0000000..87f1639
>>>> --- /dev/null
>>>> +++ b/meta/recipes-support/nettle/nettle_2.7.1.bb
>>>> @@ -0,0 +1,24 @@
>>>> +SUMMARY = "A low level cryptographic library"
>>>> +HOMEPAGE = "http://www.lysator.liu.se/~nisse/nettle/"
>>>> +SECTION = "libs"
>>>> +LICENSE = "LGPLv2.1 & GPLv2"
>>>> +LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 \
>>>> +                    file://serpent-decrypt.c;beginline=53;endline=67;md5=bcfd4745d53ca57f82907089898e390d \
>>>> +                    file://serpent-set-key.c;beginline=56;endline=70;md5=bcfd4745d53ca57f82907089898e390d"
>>>> +
>>>> +DEPENDS += "gmp"
>>>> +
>>>> +SRC_URI = "http://www.lysator.liu.se/~nisse/archive/${BP}.tar.gz"
>>>> +
>>>> +SRC_URI[md5sum] = "003d5147911317931dd453520eb234a5"
>>>> +SRC_URI[sha256sum] = "bc71ebd43435537d767799e414fce88e521b7278d48c860651216e1fc6555b40"
>>>> +
>>>> +do_configure_prepend() {
>>>> +       if [ ! -e ${S}/acinclude.m4 -a -e ${S}/aclocal.m4 ]; then
>>>> +               cp ${S}/aclocal.m4 ${S}/acinclude.m4
>>>> +       fi
>>>> +}
>>>> +
>>>> +inherit autotools
>>>> +
>>>> +BBCLASSEXTEND = "native"
>>>>
>>>> -- 
>>>> _______________________________________________
>>>> Openembedded-commits mailing list
>>>> Openembedded-commits@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-commits



      reply	other threads:[~2014-05-15 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140506170105.9D101503BF@opal.openembedded.org>
2014-05-15 11:13 ` [oe-commits] Valentin Popa : nettle: add nettle to oe-core Martin Jansa
2014-05-15 13:25   ` Valentin Popa
2014-05-15 14:07     ` Martin Jansa
2014-05-15 14:49       ` Valentin Popa [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=5374D3EA.6000309@intel.com \
    --to=valentin.popa@intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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