All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libatasmart_0.13.bb: `No package 'libudev' found` and `./strpool: ./strpool: cannot execute binary file`
Date: Thu, 23 Sep 2010 16:13:35 +0200	[thread overview]
Message-ID: <4C9B608F.4060602@dresearch.de> (raw)
In-Reply-To: <4C9B57F8.6000605@dresearch.de>

On 09/23/2010 03:36 PM, Steffen Sledz wrote:
> Am 23.09.2010 13:30, schrieb Paul Menzel:
>> Using Ȧngström 2008.1 this error was not met though. But `do_compile()`
>> fails with `./strpool: cannot execute binary file`.
>>
>>         Log data follows:
>>         | NOTE: make
>>         |   CC     strpool.o
>>         |   CCLD   strpool
>>         | ./strpool atasmart.c atasmart.strpool.c
>>         | ./strpool: ./strpool: cannot execute binary file
>>         | make: *** [atasmart.strpool.c] Error 126
>>         | FATAL: oe_runmake failed
>>         | ERROR: Function do_compile failed
>>         NOTE: package libatasmart-0.13-r1: task do_compile: Failed
>>
>> But as far as I understand the recipe takes care of that by compiling
>> `strpool` for the build host [2].
>>
>>         do_compile_prepend() {
>>         	rm strpool -f
>>         	${BUILD_CC} -o strpool strpool.c
>>         	chmod +x strpool
>>         }
>> ...
>> [2] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/devicekit/libatasmart_0.13.bb?id=67ab615dac83b0460fa1b88dfb11c72d7c93e259
> 
> I hit the same problem. But just when building libatasmart for the first time. A second build succeeds.

I tried the following to find the cause for this.

First i added

  pwd
  file strpool

to the do_compile_prepend().

Aftre running

  bitbake libatasmart -c clean
  bitbake libatasmart

i saw

  ERROR: log data follows (/home/sledz/work/HydraIP/OE/tmp.6/work/armv5te-angstrom-linux-gnueabi/libatasmart-0.13-r1/temp/log.do_compile.29576)
  | /home/sledz/work/HydraIP/OE/tmp.6/work/armv5te-angstrom-linux-gnueabi/libatasmart-0.13-r1/git
  | strpool: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped
  ...

Then i called a devshell

  bitbake libatasmart -c devshell

Within it

  > pwd
  /home/sledz/work/HydraIP/OE/tmp.6/work/armv5te-angstrom-linux-gnueabi/libatasmart-0.13-r1/git
  > file strpool
  strpool: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not stripped

So the binary has changed in between.

Steffen



  reply	other threads:[~2010-09-23 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 11:30 libatasmart_0.13.bb: `No package 'libudev' found` and `./strpool: ./strpool: cannot execute binary file` Paul Menzel
2010-09-23 12:21 ` Steffen Sledz
2010-09-23 13:36 ` Steffen Sledz
2010-09-23 14:13   ` Steffen Sledz [this message]
2010-09-24  9:03     ` Steffen Sledz
2010-09-24  9:23       ` [PATCH] libatasmart-0.13: resolve cross compile problem Steffen Sledz
2010-09-24  9:29         ` Koen Kooi
2010-09-24  9:55           ` Paul Menzel
2010-09-24 10:01             ` Steffen Sledz

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=4C9B608F.4060602@dresearch.de \
    --to=sledz@dresearch.de \
    --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.