From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libev on armv5 - illegal instruction
Date: Fri, 10 Aug 2012 21:56:23 +0200 [thread overview]
Message-ID: <20120810215623.5d7304a5@skate> (raw)
In-Reply-To: <op.witduljwyxxkfz@pohanka-pc>
Hello,
Le Fri, 10 Aug 2012 09:31:23 +0200,
"Jan Pohanka" <xhpohanka@gmail.com> a ?crit :
> Now I also discovered that the problem is machine specific. I have two
> hosts using exactly the same cross-compiler and buildroot. One works and
> the second one (my workstation) does not.
>
> working host (Ubuntu 11.10) uname -a
> Linux linux-dev 3.0.0-23-server #39-Ubuntu SMP Thu Jul 19 19:37:41 UTC
> 2012 x86_64 x86_64 x86_64 GNU/Linux
>
> my workstation (Ubuntu 12.04 lts) uname -a
> Linux pohanka-pc 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC
> 2012 x86_64 x86_64 x86_64 GNU/Linux
The toolchain is not downloaded by Buildroot in your .config. Are you
sure you have the same toolchain on both build machines?
Also, could you put online:
- A complete build log on both machines (make clean && make)
- The two binaries that are different and causing problems
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-10 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 9:43 [Buildroot] libev on armv5 - illegal instruction Jan Pohanka
2012-08-10 6:58 ` Thomas Petazzoni
2012-08-10 7:32 ` Jan Pohanka
2012-08-10 10:57 ` Jan Pohanka
[not found] ` <op.witduljwyxxkfz@pohanka-pc>
2012-08-10 19:56 ` Thomas Petazzoni [this message]
2012-08-13 6:52 ` Jan Pohanka
2012-08-15 12:45 ` Jan Pohanka
2012-08-15 14:56 ` Thomas Petazzoni
2012-08-16 8:49 ` Jan Pohanka
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=20120810215623.5d7304a5@skate \
--to=thomas.petazzoni@free-electrons.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.