Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] uclibc .9.31 & usleep
Date: Wed, 05 May 2010 15:44:46 +0200	[thread overview]
Message-ID: <87bpcubgz5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <000c01caec58$eb209a20$6f01a8c0@apexlaptop> (Sagaert Johan's message of "Wed, 5 May 2010 15:43:17 +0200")

>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:

 Sagaert> Hi
 Sagaert> i tried to build a rootfs with the new uclibc 0.9.31
 
 Sagaert> building gdb 6.7.1 failed complaining about usleep 
 Sagaert>  see also this link :
 
 Sagaert> http://old.nabble.com/Problems-with-i686_defconfig-td28240927.html
 
 Sagaert> Should i set something special in the new uclibc config ?

Yes, ensure you're using the uclibc 0.9.31 defconfig
(BR2_UCLIBC_CONFIG). It's the default for new configs, but if you are
reusing an old config it might be wrong.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-05-05 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 13:43 [Buildroot] uclibc .9.31 & usleep Sagaert Johan
2010-05-05 13:44 ` Peter Korsgaard [this message]
2010-05-05 14:00   ` Will Moore
2010-05-10  9:24   ` [Buildroot] Method of moving to new releases of buildroot Will Moore

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=87bpcubgz5.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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