All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-09-13
Date: Tue, 14 Sep 2010 08:28:31 -0400	[thread overview]
Message-ID: <4C8F6A6F.4090403@balister.org> (raw)
In-Reply-To: <4C8F5E55.9010906@balister.org>

On 09/14/2010 07:36 AM, Philip Balister wrote:
> On 09/13/2010 02:21 PM, Cliff Brake wrote:
>> last weeks testing cycle was a success.
>>
>> http://wiki.openembedded.net/index.php/Testing#Testing_Log
>>
>> Firefox is failing in some configurations if the same version of
>> firefox is installed on the host system -- it would be nice to get
>> this resolved this week.
>>
>> testing-next branch has been updated and is ready for clean builds.
>
> Next error on F13. Sorry I don't have time to debug these. I'm just
> trying to get in the rhythm. I also need to report this to tinderbox.
> Not sure why it is touching build machine files.

Here is the full log:

http://tinderbox.openembedded.net/public/logs/task/7786641.txt

Hopefully a QEMU guru can look it over.

Philip

>
> Philip
>
> | /usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libgnutls.so:
> undefined reference to `gcry_cipher_setkey@GCRYPT_1.2'
> | /usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libgnutls.so:
> undefined reference to `gcry_cipher_setiv@GCRYPT_1.2'
> | collect2: ld returned 1 exit status
> | make[1]: *** [qemu-system-mips] Error 1
> | make: *** [subdir-mips-softmmu] Error 2
> | /usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libgnutls.so:
> undefined reference to `gcry_cipher_setkey@GCRYPT_1.2'
> | /usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libgnutls.so:
> undefined reference to `gcry_cipher_setiv@GCRYPT_1.2'
> | collect2: ld returned 1 exit status
> | make[1]: *** [qemu-system-mips64el] Error 1
> | make: *** [subdir-mips64el-softmmu] Error 2
> | /usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libgnutls.so:
> undefined reference to `gcry_cipher_setkey@GCRYPT_1.2'
> | /usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libgnutls.so:
> undefined reference to `gcry_cipher_setiv@GCRYPT_1.2'
> | collect2: ld returned 1 exit status
> | make[1]: *** [qemu-system-mipsel] Error 1
> | make: *** [subdir-mipsel-softmmu] Error 2
> | FATAL: oe_runmake failed
> NOTE: package qemu-native-0.12.5-r0: task do_compile: Failed
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



  parent reply	other threads:[~2010-09-14 12:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 18:21 testing branch 2010-09-13 Cliff Brake
2010-09-13 20:55 ` Philip Balister
2010-09-13 23:33   ` Graham Gower
2010-09-14  0:03     ` Graham Gower
2010-09-14  0:57       ` [Bitbake-dev] " Chris Larson
2010-09-14  6:07         ` Frans Meulenbroeks
2010-09-14  6:18           ` Steffen Sledz
2010-09-14 11:36 ` Philip Balister
2010-09-14 11:58   ` Frans Meulenbroeks
2010-09-14 12:28   ` Philip Balister [this message]
2010-09-14 12:37     ` Jan Paesmans
2010-09-14 12:56       ` Frans Meulenbroeks
2010-09-14 12:58         ` Frans Meulenbroeks
2010-09-14 13:00         ` Gary Thomas
2010-09-14 15:53   ` Khem Raj
2010-09-14 17:45     ` Philip Balister

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=4C8F6A6F.4090403@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@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 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.