From: Microbit_Ubuntu <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?
Date: Fri, 28 May 2010 07:32:12 +1000 [thread overview]
Message-ID: <1274995932.436.9.camel@ubuntu> (raw)
In-Reply-To: <201005272319.54338.yann.morin.1998@anciens.enib.fr>
Bonjour Yann, tout le monde,
On Thu, 2010-05-27 at 23:19 +0200, Yann E. MORIN wrote:
> Kris, All,
>
> On Thursday 27 May 2010 23:11:17 Microbit_Ubuntu wrote:
> > I don;t know if I'm off base here, but I notice that rc3 does not have
> > the patches for uClibc 0.9.30.1 at toolchain/uClibc folder in the
> > tarball ?????
>
> Indeed, that because the 0.9.30.x that is used is .3, and .1 is not present
> in the version choice, in the menuconfig. See:
> toolchain/uClibc/Config.in at 40
>
> Regards,
> Yann E. MORIN.
>
Thanks for reviewing.
This might have sounded like a dumb question - as of course uClibc was
compiled by ct-ng...
I haven't yet compiled BR, am about to though. I saw uClibc 0.1.29
patches, so I thought "where's 0.9.30.1 ??".
I mean, if 0.9.30.3 is used, why bother with 0.9.29 patches ???
Oh well, false alarm in any case !!
The *biggest* problem so far I had was the fact that ct-ng-1.6.1 patches
uClibc 0.9.30.1 BUT does NOT apply the ARM sysdep patch.
I kept getting "invalid module format" on my target. A rebuild with
(indeed) "new" linuxthreads enabled in uClibc of the x-tools toolchain
fixed it after manually applying the sysdeps patch !!
I'll still reply to your other post as well.
Au revoir,
Kris
next prev parent reply other threads:[~2010-05-27 21:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 12:43 [Buildroot] Buildroot 2010.05-rc3 released Peter Korsgaard
2010-05-27 18:58 ` Microbit_Ubuntu
2010-05-27 21:15 ` Yann E. MORIN
2010-05-27 21:51 ` Microbit_Ubuntu
2010-05-27 21:55 ` Microbit_Ubuntu
2010-05-28 20:20 ` Yann E. MORIN
2010-06-01 10:21 ` Microbit_Ubuntu
2010-06-01 10:57 ` Peter Korsgaard
2010-06-01 18:25 ` Microbit_Ubuntu
2010-06-01 20:21 ` Microbit_Ubuntu
2010-06-01 20:27 ` Yann E. MORIN
2010-05-28 0:49 ` Microbit_Ubuntu
2010-05-27 21:11 ` [Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ? Microbit_Ubuntu
2010-05-27 21:19 ` Yann E. MORIN
2010-05-27 21:32 ` Microbit_Ubuntu [this message]
2010-05-28 12:44 ` Peter Korsgaard
2010-06-01 10:38 ` Microbit_Ubuntu
2010-06-01 11:00 ` Peter Korsgaard
2010-05-28 0:37 ` [Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb Microbit_Ubuntu
2010-05-30 7:35 ` Peter Korsgaard
2010-06-01 10:23 ` Microbit_Ubuntu
2010-06-01 10:56 ` Peter Korsgaard
2010-06-01 18:30 ` Microbit_Ubuntu
2010-06-15 7:10 ` Thomas Petazzoni
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=1274995932.436.9.camel@ubuntu \
--to=microbit@virginbroadband.com.au \
--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