From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] neon: build fix
Date: Fri, 12 Jun 2015 13:32:04 -0700 [thread overview]
Message-ID: <557B41C4.2090607@gmail.com> (raw)
In-Reply-To: <CAJTo0LYABsnZBRP64=vx0a9prDvUuBmpg_6BYn1FcTGf_rokyw@mail.gmail.com>
Ok, I got this working. I will submit a new pull request soon.
- armin
On 06/09/2015 12:02 PM, Burton, Ross wrote:
> On 4 June 2015 at 20:37, Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
> fixup to allow building with api changes in gnutls.
>
>
> My world builds shows that libmusicbrainz was failing due to neon not
> linking, and to demonstrate this I added this to neon.bb <http://neon.bb>:
>
> do_compile_append() {
> oe_runmake -C test
> }
>
> Et voila:
>
> | ../x86_64-poky-linux-libtool --silent --mode=link
> x86_64-poky-linux-gcc -m64 -march=corei7 -mtune=corei7 -mfpmath=sse
> -msse4.2 --sysroot=/data/poky-master/tmp/sysroots/intel-corei7-64
> -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -no-install -o lock lock.lo
> libtest.la <http://libtest.la>
> |
> /data/poky-master/tmp/work/corei7-64-poky-linux/neon/0.30.1-r0/build/src/.libs/libneon.so:
> undefined reference to `gnutls_certificate_client_set_retrieve_function'
> |
> /data/poky-master/tmp/work/corei7-64-poky-linux/neon/0.30.1-r0/build/src/.libs/libneon.so:
> undefined reference to `gnutls_certificate_client_set_retrieve_function'
>
> Neon still doesn't build with the new gnutls.
>
> Ross
prev parent reply other threads:[~2015-06-12 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 19:37 [PATCH 0/3] Gntls update to 4.3.1 Armin Kuster
2015-06-04 19:37 ` [PATCH 1/3] nettle: update package to 3.1.1 version Armin Kuster
2015-06-04 19:37 ` [PATCH 2/3] gnutls: update to 3.4.1 Armin Kuster
2015-06-04 19:37 ` [PATCH 3/3] neon: build fix Armin Kuster
2015-06-09 19:02 ` Burton, Ross
2015-06-12 20:32 ` akuster808 [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=557B41C4.2090607@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.