Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Arp <tobiasarp@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] Build udev for arm -> accept4 undefined reference
Date: Wed, 22 Feb 2012 13:56:55 +0100 (CET)	[thread overview]
Message-ID: <841306327.1348388.1329915415222.JavaMail.fmail@mwmweb063> (raw)


Hi baruch,

thanks i have missed this.

Tobias

-----Urspr?ngliche Nachricht-----
Von: "Baruch Siach" <baruch@tkos.co.il>
Gesendet: 22.02.2012 13:25:56
An: "Tobias Arp" <tobiasarp@web.de>
Betreff: Re: [Buildroot] Build udev for arm -> accept4 undefined reference

>Hi Tobias,
>
>On Wed, Feb 22, 2012 at 01:17:15PM +0100, Tobias Arp wrote:
>> Hi,
>>
>> i am trying to use buildroot-2012.02-rc2 with the attached config file for an arm
>> processor. My custom toolchain was build with crosstool-NG with this config:
>>
>> arm-unknown-linux-gnueabi
>> kernel-headers: linux 3.0
>> binutils 2.19.1
>> gcc 4.3.2
>> glibc 2.9
>
>Quote from the accept(2) man page:
>
> The accept4() system call is available starting with Linux 2.6.28;
> support in glibc is available starting with version 2.10.
>
>So glibc 2.9 is just too old.
>
>baruch
>
>--
> http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
>=}------------------------------------------------ooO--U--Ooo------------{=
> - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -


___________________________________________________________
Ihr WEB.DE Postfach immer dabei: die kostenlose WEB.DE Mail App f?r iPhone und Android.
https://produkte.web.de/freemail_mobile_startseite/

             reply	other threads:[~2012-02-22 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 12:56 Tobias Arp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-22 12:17 [Buildroot] Build udev for arm -> accept4 undefined reference Tobias Arp
2012-02-22 12:25 ` Baruch Siach

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=841306327.1348388.1329915415222.JavaMail.fmail@mwmweb063 \
    --to=tobiasarp@web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox