From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building x86_64 Toolchain
Date: Tue, 17 May 2011 08:58:47 +0200 [thread overview]
Message-ID: <20110517085847.46aa97fc@surf> (raw)
In-Reply-To: <5ABE8A5E96C0364CAF2B4DC1DEB7CEAC490DDEFA@Mercury.usurf.usu.edu>
Hello,
On Mon, 16 May 2011 19:43:53 +0000
Jonathan Haws <Jonathan.Haws@sdl.usu.edu> wrote:
> (cd ./lib && tar -cf - *.so.*) | tar -xf - -C /home/jhaws/opt/svn/duster/EmbeddedLinux/buildroot/buildroot/output/host/usr/x86_64-unknown-linux-uclibc/sysroot/lib/
> tar: libpthread.so.0: no version information available (required by /lib64/librt.so.1)
> tar: libpthread.so.0: no version information available (required by /lib64/librt.so.1)
> /bin/sh: line 1: 17753 Segmentation fault (core dumped) tar -cf - *.so.*
> tar: This does not look like a tar archive
> tar: Exiting with failure status due to previous errors
It seems like "tar" is segfaulting here, so it seems to be a problem
with the tar program of your distribution. Can you check the core dump
to see to which program it comes from ?
Can you share your Buildroot .config so that I can try to reproduce the
problem on a different distribution?
> In file included from libpthread/linuxthreads/sysdeps/pthread/errno-loc.c:23:0:
> ./libpthread/linuxthreads/sysdeps/unix/sysv/linux/x86_64/sysdep-cancel.h:20:20: fatal error: sysdep.h: No such file or directory
> compilation terminated.
I am not sure if LinuxThreads new is supposed to compile or not.
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:[~2011-05-17 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ABE8A5E96C0364CAF2B4DC1DEB7CEAC490DDEBC@Mercury.usurf.usu.edu>
2011-05-16 19:43 ` [Buildroot] Building x86_64 Toolchain Jonathan Haws
2011-05-17 6:58 ` Thomas Petazzoni [this message]
2011-05-17 15:01 ` Jonathan Haws
2011-05-17 15:13 ` Jonathan Haws
2011-05-17 15:46 ` Jonathan Haws
2011-05-17 17:02 ` Jonathan Haws
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=20110517085847.46aa97fc@surf \
--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.