Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building curlftpfs within buildroot
Date: Tue, 30 Oct 2012 12:03:16 +0100	[thread overview]
Message-ID: <20121030120316.0faf8a0e@skate> (raw)
In-Reply-To: <508FB158.1090205@mail.ru>

Dear Alexander Varnin,

On Tue, 30 Oct 2012 14:52:08 +0400, Alexander Varnin wrote:
> Hello. I'm trying to build self-made package curlftpfs within buildroot. 
> It is simple autotools based package. Build fails with pthread error:
> 
> /home/varnin/buildroot/output/host/usr/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.5.4/../../../../arm-unknown-linux-uclibcgnueabi/bin/ld: 
> note: 'pthread_create' is defined in DSO 
> /home/varnin/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/lib/libpthread.so.0 
> so try adding it to the linker command line
> /home/varnin/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/lib/libpthread.so.0: 
> could not read symbols: Invalid operation
> collect2: ld returned 1 exit status
> 
> I'm using buildroot toolchain to build my application that uses threads, 
> and it compiles and works normally. What could be the problem?
> I'm attaching build log.

For some reason -lpthread is missing on the link command line.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-10-30 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 10:52 [Buildroot] Problem building curlftpfs within buildroot Alexander Varnin
2012-10-30 11:03 ` Thomas Petazzoni [this message]
2012-10-30 11:25   ` Alexander Varnin
2012-10-30 11:26 ` Alexander Khryukin
2012-10-30 11:34   ` Alexander Khryukin
2012-10-30 12:24 ` Richard Braun
2012-10-30 12:33   ` Alexander Varnin
2012-10-30 12:36   ` Alexander Khryukin
2012-10-30 12:51     ` Alexander Varnin

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=20121030120316.0faf8a0e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox