From: Johannes Morgenroth <morgenroth@ibr.cs.tu-bs.de>
To: buildroot@busybox.net
Subject: [Buildroot] SIGSEGV in __pthread_initialize_minimal_internal ()
Date: Fri, 07 Feb 2014 09:21:31 +0100 [thread overview]
Message-ID: <52F4978B.8040707@ibr.cs.tu-bs.de> (raw)
In-Reply-To: <52F3F866.5000701@mind.be>
Hello Arnout,
thank you for the response.
Am 06.02.2014 22:02, schrieb Arnout Vandecappelle:
> You're trying to use the cross-compiled binary directly on your host.
> This may work by accident, but may not work as well. In this particular
> case, I suspect it may be an issue with kernel headers: the cross-build
> is using 3.13.x while your host is probably running an earlier kernel.
>
> Try running it under a system qemu so you have the corresponding kernel,
> or build the toolchain with kernel headers corresponding to your host.
>
> Regards,
> Arnout
The binary is compiled using and for x86. Thus, starting on the same
system should work and actually it had worked with older releases (at
least with 2012.02). I could not test the kernel issue you mentioned
because the system runs a 3.8 and buildroot only support older or newer
one. I tried both 3.2 and 3.13, none of them had worked. However, I do
not understand why a statically linked binary should depend on the
system kernel it runs on. Also this was never an issue with release 2012.02.
Kind regards,
Johannes Morgenroth
--
Johannes Morgenroth Institut fuer Betriebssysteme und Rechnerverbund
Tel.: +49-531-391-3249 Muehlenpfordtstrasse 23
Fax.: +49-531-391-5936 TU Braunschweig D-38106 Braunschweig
next prev parent reply other threads:[~2014-02-07 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:05 [Buildroot] SIGSEGV in __pthread_initialize_minimal_internal () Johannes Morgenroth
2014-02-06 21:02 ` Arnout Vandecappelle
2014-02-07 8:21 ` Johannes Morgenroth [this message]
2014-02-07 15:59 ` Johannes Morgenroth
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=52F4978B.8040707@ibr.cs.tu-bs.de \
--to=morgenroth@ibr.cs.tu-bs.de \
--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.