Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARM EABI toolchain - anyone build it successfully?
Date: Wed, 20 Aug 2008 12:21:02 +0200	[thread overview]
Message-ID: <20080820102102.GB20285@mx.loc> (raw)
In-Reply-To: <48ABEB53.4030104@wpkg.org>

On Wed, Aug 20, 2008 at 12:00:51PM +0200, Tomasz Chmielewski wrote:

> BTW, I know why it initially failed for me - I removed networking support in uClibc configuration, which resulted in:

well yes, that's somewhat expected :) I usually do not do threads. If
you need threads, you should at least turn on socket support for obvious
reasons.
>
>
>  CC libpthread/linuxthreads.old/pthread.oS
>  STRIP -x -R .note -R .comment libpthread/linuxthreads.old/libpthread_so.a
>  AR cr libpthread/linuxthreads.old/libpthread_so.a
>  LD libpthread-0.9.29.so
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `sendto':
> wrapsyscall.c:(.text+0x44): undefined reference to `__libc_sendto'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `sendmsg':
> wrapsyscall.c:(.text+0x90): undefined reference to `__libc_sendmsg'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `send':
> wrapsyscall.c:(.text+0xe4): undefined reference to `__libc_send'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `recvmsg':
> wrapsyscall.c:(.text+0x130): undefined reference to `__libc_recvmsg'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `recvfrom':
> wrapsyscall.c:(.text+0x194): undefined reference to `__libc_recvfrom'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `recv':
> wrapsyscall.c:(.text+0x1e8): undefined reference to `__libc_recv'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `connect':
> wrapsyscall.c:(.text+0x234): undefined reference to `__libc_connect'
> libpthread/linuxthreads.old/libpthread_so.a(wrapsyscall.os): In function `accept':
> wrapsyscall.c:(.text+0x280): undefined reference to `__libc_accept'
> collect2: ld returned 1 exit status
> make[1]: *** [lib/libpthread.so] Error 1
> make[1]: Leaving directory `/home/build/buildroot/buildroot-arm-gcc-4.3.1-EABI/toolchain_build_arm/uClibc'
> make: *** [/home/build/buildroot/buildroot-arm-gcc-4.3.1-EABI/toolchain_build_arm/uClibc/lib/libc.a] Error 2

      reply	other threads:[~2008-08-20 10:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 15:34 [Buildroot] ARM EABI toolchain - anyone build it successfully? Tomasz Chmielewski
2008-08-19 15:49 ` Bernhard Reutner-Fischer
2008-08-19 15:54   ` Tomasz Chmielewski
2008-08-19 16:28     ` Bernhard Reutner-Fischer
2008-08-20  9:29       ` Tomasz Chmielewski
2008-08-20  9:49         ` Bernhard Reutner-Fischer
2008-08-20  9:55           ` Tomasz Chmielewski
2008-08-20 10:07           ` Tomasz Chmielewski
2008-08-20 10:16             ` Bernhard Reutner-Fischer
2008-08-20 10:22               ` Tomasz Chmielewski
2008-08-20 10:59               ` Tomasz Chmielewski
2008-08-20 11:24                 ` Tomasz Chmielewski
2008-08-20 10:00         ` Tomasz Chmielewski
2008-08-20 10:21           ` Bernhard Reutner-Fischer [this message]

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=20080820102102.GB20285@mx.loc \
    --to=rep.dot.nop@gmail.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