[Buildroot] Buildroot 2010.05-rc3 released

[Buildroot] Buildroot 2010.05-rc3 released

[Peter Korsgaard]

Hi,

Buildroot 2010.05-rc3 is released - Go download it at:

http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.gz

or

http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.bz2

Or get it from Git:

git://git.buildroot.net/buildroot

Please give it a spin and report any problems to the mailing list or bug
tracker. Many thanks to the people contributing to this release:

git shortlog -s -n 2010.05_rc2..
    49  Peter Korsgaard
    32  Thomas Petazzoni
     1  Baruch Siach
     1  Bj?rn Forsman
     1  H Hartley Sweeten
     1  Julien Boibessot
     1  Nick Leverton
     1  Yann E. MORIN
     1  cmchao

Unless any big issues are found, expect the final 2010.05 release by the
end of the week - So please give it a good test.

-- 
Bye, Peter Korsgaard

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

Hi Peter,


On Thu, 2010-05-27 at 14:43 +0200, Peter Korsgaard wrote:
> Hi,
> 
> Buildroot 2010.05-rc3 is released - Go download it at:
> 
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.gz
> 
> or
> 
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.bz2
> 
> Or get it from Git:
> 
> git://git.buildroot.net/buildroot
> 
> Please give it a spin and report any problems to the mailing list or bug
> tracker. Many thanks to the people contributing to this release:
> 
> git shortlog -s -n 2010.05_rc2..
>     49  Peter Korsgaard
>     32  Thomas Petazzoni
>      1  Baruch Siach
>      1  Bj?rn Forsman
>      1  H Hartley Sweeten
>      1  Julien Boibessot
>      1  Nick Leverton
>      1  Yann E. MORIN
>      1  cmchao
> 
> Unless any big issues are found, expect the final 2010.05 release by the
> end of the week - So please give it a good test.
> 
> -- 
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


While I started a clean install w/ ext toolchain (crosstool-ng -1.6.1),
I noticed that menuconfig still has a snag in it when starting from
scratch with config :

When HAL is not used and ext toolchain selected, udev & hotplug are
*not* displayed nor selected. 
busybox-show-others has to be enabled and they both have to be
explicitly enabled from there.
BR versions < 2009.11 turned 'em on when mdev was selected.

Perhaps it's deemed that HAL should be selected, dunno.

In any case, hotplug & udev should not be suppressed by SHOW_OTHERS,
since even busybox-1.16.1 does NOT offer them...

More feedback when I completely rebuild.

PS : ct-ng only offers "linuxthreads". So are we supposed to use
"stable/old" in BR or "new" (latter, I guess) ????
I seem to have had problems with that - invoking gdbserver prompts :
"can't load libthread_db.so.1".
This worked fine with internal toolchain... Anyone ?

HTH
Best regards,
Kris

[Buildroot] Buildroot 2010.05-rc3 released

[Yann E. MORIN]

Kris, All,

On Thursday 27 May 2010 20:58:43 Microbit_Ubuntu wrote:
[--SNIP--]
> PS : ct-ng only offers "linuxthreads".

That's only true if you build a uClibc-based toolchain. If you build a
glibc- or a eglibc-based toolchain, then crosstool-NG allows you to
use NPTL.

So I'll take that you build a uClibc-based toolchain...

> So are we supposed to use 
> "stable/old" in BR or "new" (latter, I guess) ????

That has to match the way you configured uClibc in your toolchain.
Check the uClibc .config file for that.

> I seem to have had problems with that - invoking gdbserver prompts :
> "can't load libthread_db.so.1".
> This worked fine with internal toolchain... Anyone ?

libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
your target, in the standard libraries search path.

Also, there is a known dangling issue wrt cross-gdb + gdbserver.
See this thread:
  http://lists.busybox.net/pipermail/buildroot/2010-May/034435.html

In short, you have to get the cross-gdb *and* the gdbserver from the
same version of gdb, to be sure they know how to speak to each other.
So: either get both from crosstool-NG, or get both from buildroot.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

Hi Yann, All,

On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 20:58:43 Microbit_Ubuntu wrote:
> [--SNIP--]
> > PS : ct-ng only offers "linuxthreads".
> 
> That's only true if you build a uClibc-based toolchain. If you build a
> glibc- or a eglibc-based toolchain, then crosstool-NG allows you to
> use NPTL.
> 
> So I'll take that you build a uClibc-based toolchain...
> 
> > So are we supposed to use 
> > "stable/old" in BR or "new" (latter, I guess) ????
> 
> That has to match the way you configured uClibc in your toolchain.
> Check the uClibc .config file for that.
> 
> > I seem to have had problems with that - invoking gdbserver prompts :
> > "can't load libthread_db.so.1".
> > This worked fine with internal toolchain... Anyone ?
> 
> libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> your target, in the standard libraries search path.
> 
> Also, there is a known dangling issue wrt cross-gdb + gdbserver.
> See this thread:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034435.html
> 
> In short, you have to get the cross-gdb *and* the gdbserver from the
> same version of gdb, to be sure they know how to speak to each other.
> So: either get both from crosstool-NG, or get both from buildroot.
> 
> Regards,
> Yann E. MORIN.
> 


I've been compiling with both from buildroot at all times, so that
should be OK.
While I was doing a sanity check vis-a-vis (sorry for the missing accent
grave) module inserting (solved), I used an older kernel uImage
(generated when I still used internal BR toolchain).

gdbserver of course is still happy there, but I can't find a trace of
libthread_db.so.1 on my rootfs target. (looked in /lib and /usr/lib).
I do have libpthread.so.0 etc.
I tried with an ltrace but that's not helping much.. (only see
__uClib_main)

I'll compile shortly and keep you posted.

Thanks for the help Yann, it's greatly appreciated !

-- Kris

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

A propos,

On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 20:58:43 Microbit_Ubuntu wrote:
> [--SNIP--]
> > PS : ct-ng only offers "linuxthreads".
> 
> That's only true if you build a uClibc-based toolchain. If you build a
> glibc- or a eglibc-based toolchain, then crosstool-NG allows you to
> use NPTL.
> 
> So I'll take that you build a uClibc-based toolchain...
> 
> > So are we supposed to use 
> > "stable/old" in BR or "new" (latter, I guess) ????
> 
> That has to match the way you configured uClibc in your toolchain.
> Check the uClibc .config file for that.
> 
> > I seem to have had problems with that - invoking gdbserver prompts :
> > "can't load libthread_db.so.1".
> > This worked fine with internal toolchain... Anyone ?
> 
> libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> your target, in the standard libraries search path.
> 
> Also, there is a known dangling issue wrt cross-gdb + gdbserver.
> See this thread:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034435.html
> 
> In short, you have to get the cross-gdb *and* the gdbserver from the
> same version of gdb, to be sure they know how to speak to each other.
> So: either get both from crosstool-NG, or get both from buildroot.
> 
> Regards,
> Yann E. MORIN.
> 




> libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> your target, in the standard libraries search path.

When gdbserver was bleating about libthread_db.so.1, it was in the staging directory,
but it wasn't placed on the target rootfs.
When I manually added it on the target (libthread_db.so.1 I mean), gdbserver worked good as gold then...

-- Kris

[Buildroot] Buildroot 2010.05-rc3 released

[Yann E. MORIN]

Kris, All,

On Thursday 27 May 2010 23:55:59 Microbit_Ubuntu wrote:
> On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> > libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> > your target, in the standard libraries search path.
> When gdbserver was bleating about libthread_db.so.1, it was in the staging directory,
> but it wasn't placed on the target rootfs.
> When I manually added it on the target (libthread_db.so.1 I mean), gdbserver worked good as gold then...

I've just submitted a fix for this:
  http://lists.busybox.net/pipermail/buildroot/2010-May/034848.html

Care to test it and report, please?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

Hi Yann et al,

On Fri, 2010-05-28 at 22:20 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 23:55:59 Microbit_Ubuntu wrote:
> > On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> > > libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> > > your target, in the standard libraries search path.
> > When gdbserver was bleating about libthread_db.so.1, it was in the staging directory,
> > but it wasn't placed on the target rootfs.
> > When I manually added it on the target (libthread_db.so.1 I mean), gdbserver worked good as gold then...
> 
> I've just submitted a fix for this:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034848.html
> 
> Care to test it and report, please?
> 
> Regards,
> Yann E. MORIN.
> 


Sorry for brief delay.
Have my feet back under desk now. Need to do some fiddling on XP first,
but then back to Linux.
I noticed that 2010.05 is fully released now, so I'll start from there.
I'm not sure if your fix is in 2010.05 final or not, but I guess we'll
see shortly.
I will delete 2010.05-rc3 folder and rebuild with 2010.05 final and go
from there. Will keep you posted.

Thanks for reviewing !

Best regards,
Kris

[Buildroot] Buildroot 2010.05-rc3 released

[Peter Korsgaard]

>>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:

Hi,

 Microbit> Have my feet back under desk now. Need to do some fiddling on
 Microbit> XP first, but then back to Linux.  I noticed that 2010.05 is
 Microbit> fully released now, so I'll start from there.  I'm not sure
 Microbit> if your fix is in 2010.05 final or not, but I guess we'll see
 Microbit> shortly.  I will delete 2010.05-rc3 folder and rebuild with
 Microbit> 2010.05 final and go from there. Will keep you posted.

It is.

-- 
Bye, Peter Korsgaard

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

Hi Yann,

On Fri, 2010-05-28 at 22:20 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 23:55:59 Microbit_Ubuntu wrote:
> > On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> > > libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> > > your target, in the standard libraries search path.
> > When gdbserver was bleating about libthread_db.so.1, it was in the staging directory,
> > but it wasn't placed on the target rootfs.
> > When I manually added it on the target (libthread_db.so.1 I mean), gdbserver worked good as gold then...
> 
> I've just submitted a fix for this:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034848.html
> 
> Care to test it and report, please?
> 
> Regards,
> Yann E. MORIN.
> 

Works beautiful !
Thanks for the effort.

B rgds & 73s
Kris

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

Hi Yann/all,

On Fri, 2010-05-28 at 22:20 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 23:55:59 Microbit_Ubuntu wrote:
> > On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> > > libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> > > your target, in the standard libraries search path.
> > When gdbserver was bleating about libthread_db.so.1, it was in the staging directory,
> > but it wasn't placed on the target rootfs.
> > When I manually added it on the target (libthread_db.so.1 I mean), gdbserver worked good as gold then...
> 
> I've just submitted a fix for this:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034848.html
> 
> Care to test it and report, please?
> 
> Regards,
> Yann E. MORIN.
> 

FYI, strace now does show the proper lib call (naturally :-) :

# strace gdbserver
execve("/usr/bin/gdbserver", ["gdbserver"], [/* 16 vars */]) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40005000
open("/lib/libthread_db.so.1", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0755, [SNIP].... etc....




Best regards, 
Kris

[Buildroot] Buildroot 2010.05-rc3 released

[Yann E. MORIN]

Kris, All,

On Tuesday 01 June 2010 22:21:57 Microbit_Ubuntu wrote:
> FYI, strace now does show the proper lib call (naturally :-) :
> # strace gdbserver
> execve("/usr/bin/gdbserver", ["gdbserver"], [/* 16 vars */]) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x40005000
> open("/lib/libthread_db.so.1", O_RDONLY) = 3
> fstat(3, {st_mode=S_IFREG|0755, [SNIP].... etc....

Good, then! Thanks for reporting success! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Buildroot 2010.05-rc3 released

[Microbit_Ubuntu]

Hi Yann,

On Thu, 2010-05-27 at 23:15 +0200, Yann E. MORIN wrote:
> Kris, All,
> 
> On Thursday 27 May 2010 20:58:43 Microbit_Ubuntu wrote:
> [--SNIP--]
> > PS : ct-ng only offers "linuxthreads".
> 
> That's only true if you build a uClibc-based toolchain. If you build a
> glibc- or a eglibc-based toolchain, then crosstool-NG allows you to
> use NPTL.
> 
> So I'll take that you build a uClibc-based toolchain...
> 
> > So are we supposed to use 
> > "stable/old" in BR or "new" (latter, I guess) ????
> 
> That has to match the way you configured uClibc in your toolchain.
> Check the uClibc .config file for that.
> 
> > I seem to have had problems with that - invoking gdbserver prompts :
> > "can't load libthread_db.so.1".
> > This worked fine with internal toolchain... Anyone ?
> 
> libthread_db.so.1 is dlopen(3)ed by gdbserver, so you have to get it on
> your target, in the standard libraries search path.
> 
> Also, there is a known dangling issue wrt cross-gdb + gdbserver.
> See this thread:
>   http://lists.busybox.net/pipermail/buildroot/2010-May/034435.html
> 
> In short, you have to get the cross-gdb *and* the gdbserver from the
> same version of gdb, to be sure they know how to speak to each other.
> So: either get both from crosstool-NG, or get both from buildroot.
> 
> Regards,
> Yann E. MORIN.
> 

I hope the list will forgive me sending to you & list.
Your posts have not reached me at all yet through busybox.net :-(

A follow-up as promised.
I'm rather surprised that the new build still bleats about 'can't load
libthread_db.so.1' when starting gdbserver...
That lib is in ../staging/lib as a symlink to libthread_db-0.9.30.1.so.
There's also a symlink in /staging/usr/lib called libthread_db.so which
points to libthread_db.so.1 - hmm.

As mentioned, the previous rootfs runs fine, however there is no trace
of this lib on the target.

I'm a bit stumped on this one.
I've used linuxthreads (new) in uclibc 0.9.30.1 config.

TIA
Ici avec beaucoup de soucis !!!
(rather than "sans soucis" :-)
-- Kris

[Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?

[Microbit_Ubuntu]

Hallo peter,

Hoe gaat het ? :-)

On Thu, 2010-05-27 at 14:43 +0200, Peter Korsgaard wrote:
> Hi,
> 
> Buildroot 2010.05-rc3 is released - Go download it at:
> 
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.gz
> 
> or
> 
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.bz2
> 
> Or get it from Git:
> 
> git://git.buildroot.net/buildroot
> 
> Please give it a spin and report any problems to the mailing list or bug
> tracker. Many thanks to the people contributing to this release:
> 
> git shortlog -s -n 2010.05_rc2..
>     49  Peter Korsgaard
>     32  Thomas Petazzoni
>      1  Baruch Siach
>      1  Bj?rn Forsman
>      1  H Hartley Sweeten
>      1  Julien Boibessot
>      1  Nick Leverton
>      1  Yann E. MORIN
>      1  cmchao
> 
> Unless any big issues are found, expect the final 2010.05 release by the
> end of the week - So please give it a good test.
> 
> -- 
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


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 ?????

Beste groeten,
Kris

[Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?

[Yann E. MORIN]

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.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?

[Microbit_Ubuntu]

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

[Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?

[Peter Korsgaard]

>>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:

 Microbit> Hallo peter,
 Microbit> Hoe gaat het ? :-)

Goed (I'm actually from Denmark rather than Belgium).

 Microbit> I don;t know if I'm off base here, but I notice that rc3 does
 Microbit> not have the patches for uClibc 0.9.30.1 at toolchain/uClibc
 Microbit> folder in the tarball ?????

Indeed, as we don't have support for the obsolete 0.9.30.1 version
anymore (the closest is 0.9.30.3).

-- 
Bye, Peter Korsgaard

[Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?

[Microbit_Ubuntu]

Hi Peter,

On Fri, 2010-05-28 at 14:44 +0200, Peter Korsgaard wrote:
> >>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:
> 
>  Microbit> Hallo peter,
>  Microbit> Hoe gaat het ? :-)
> 
> Goed (I'm actually from Denmark rather than Belgium).
> 
>  Microbit> I don;t know if I'm off base here, but I notice that rc3 does
>  Microbit> not have the patches for uClibc 0.9.30.1 at toolchain/uClibc
>  Microbit> folder in the tarball ?????
> 
> Indeed, as we don't have support for the obsolete 0.9.30.1 version
> anymore (the closest is 0.9.30.3).
> 

I must have given away somewhere, I guess, that I'm originally Belgian ?
I live in Australia since 1989, but lived 25 years in Belgium. I mean, I
could have been Dutch ? :-)

Tusend Tak ! :-) (I think this is acceptable Danish ?)

Best regards,
Kris

[Buildroot] Buildroot 2010.05-rc3 released uClibc 0.9.30.1 patches missing ?

[Peter Korsgaard]

>>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:

Hi,

 Microbit> Tusend Tak ! :-) (I think this is acceptable Danish ?)

Yes, except that it's 'tusind tak' ;)

-- 
Bye, Peter Korsgaard

[Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb

[Microbit_Ubuntu]

Hi Peter,

On Thu, 2010-05-27 at 14:43 +0200, Peter Korsgaard wrote:
> Hi,
> 
> Buildroot 2010.05-rc3 is released - Go download it at:
> 
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.gz
> 
> or
> 
> http://buildroot.net/downloads/buildroot-2010.05-rc3.tar.bz2
> 
> Or get it from Git:
> 
> git://git.buildroot.net/buildroot
> 
> Please give it a spin and report any problems to the mailing list or bug
> tracker. Many thanks to the people contributing to this release:
> 
> git shortlog -s -n 2010.05_rc2..
>     49  Peter Korsgaard
>     32  Thomas Petazzoni
>      1  Baruch Siach
>      1  Bj?rn Forsman
>      1  H Hartley Sweeten
>      1  Julien Boibessot
>      1  Nick Leverton
>      1  Yann E. MORIN
>      1  cmchao
> 
> Unless any big issues are found, expect the final 2010.05 release by the
> end of the week - So please give it a good test.
> 
> -- 
> Bye, Peter Korsgaard
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

I still come across 2 build errors with rc3 :

1. lockfile-progs-0.1.11
========================
The generated Makefile causes a build error in :
CFLAGS    := -g -Wall -Werror -O2
I still need to remove the -Werror to resume the build ??

2. gdb symlink
==============
ct-ng generates arm-unknown-linux-uclibcgnueabi where I have
arm-elf-xxx as an alias.
The build stops when the symlink for gdb fails. I need to manually
insert a folder 'arm-unknown-linux-uclibcgnueabi' with 'bin' as a
subfolder under ../output/staging/usr

The error is some such :

install
-c /home/kris/buildroot-2010.05-rc3/output/toolchain/gdbhost-6.8/gdb/gdb /home/kris/x-tools/arm-unknown-linux-uclibcgnueabi/bin/arm-elf-gdb
ln -snf ../../bin/arm-unknown-linux-uclibcgnueabi-gdb \
		/home/kris/buildroot-2010.05-rc3/output/staging/usr/arm-unknown-linux-uclibcgnueabi/bin/gdb
ln: creating symbolic link
`/home/kris/buildroot-2010.05-rc3/output/staging/usr/arm-unknown-linux-uclibcgnueabi/bin/gdb': No such file or directory
make: ***
[/home/kris/x-tools/arm-unknown-linux-uclibcgnueabi/bin/arm-elf-gdb]
Error 1


AFAIK I'm using the tool turnkey manner.
Can you advise ?

-- Kris

[Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb

[Peter Korsgaard]

>>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:

 Microbit> I still come across 2 build errors with rc3 :

 Microbit> 1. lockfile-progs-0.1.11
 Microbit> ========================
 Microbit> The generated Makefile causes a build error in :
 Microbit> CFLAGS    := -g -Wall -Werror -O2
 Microbit> I still need to remove the -Werror to resume the build ??

 Microbit> 2. gdb symlink
 Microbit> ==============
 Microbit> ct-ng generates arm-unknown-linux-uclibcgnueabi where I have
 Microbit> arm-elf-xxx as an alias.
 Microbit> The build stops when the symlink for gdb fails. I need to manually
 Microbit> insert a folder 'arm-unknown-linux-uclibcgnueabi' with 'bin' as a
 Microbit> subfolder under ../output/staging/usr

Both issues should be fixed in git now.

-- 
Bye, Peter Korsgaard

[Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb

[Microbit_Ubuntu]

Hi Peter,

On Sun, 2010-05-30 at 09:35 +0200, Peter Korsgaard wrote:
> >>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:
> 
>  Microbit> I still come across 2 build errors with rc3 :
> 
>  Microbit> 1. lockfile-progs-0.1.11
>  Microbit> ========================
>  Microbit> The generated Makefile causes a build error in :
>  Microbit> CFLAGS    := -g -Wall -Werror -O2
>  Microbit> I still need to remove the -Werror to resume the build ??
> 
>  Microbit> 2. gdb symlink
>  Microbit> ==============
>  Microbit> ct-ng generates arm-unknown-linux-uclibcgnueabi where I have
>  Microbit> arm-elf-xxx as an alias.
>  Microbit> The build stops when the symlink for gdb fails. I need to manually
>  Microbit> insert a folder 'arm-unknown-linux-uclibcgnueabi' with 'bin' as a
>  Microbit> subfolder under ../output/staging/usr
> 
> Both issues should be fixed in git now.
> 

Thanks for reviewing. 
Does this mean the fix is also in final 2010.05 tarball ?
(I'm not used to git, I probably should learn, have been thinking about
using it for my CVS)

B rgds
Kris

[Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb

[Peter Korsgaard]

>>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:

Hi,

 >> Both issues should be fixed in git now.
 >> 

 Microbit> Thanks for reviewing. 
 Microbit> Does this mean the fix is also in final 2010.05 tarball ?
 Microbit> (I'm not used to git, I probably should learn, have been thinking about
 Microbit> using it for my CVS)

Yes.

-- 
Bye, Peter Korsgaard

[Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb

[Microbit_Ubuntu]

Hi Peter,

On Sun, 2010-05-30 at 09:35 +0200, Peter Korsgaard wrote:
> >>>>> "Microbit" == Microbit Ubuntu <microbit@virginbroadband.com.au> writes:
> 
>  Microbit> I still come across 2 build errors with rc3 :
> 
>  Microbit> 1. lockfile-progs-0.1.11
>  Microbit> ========================
>  Microbit> The generated Makefile causes a build error in :
>  Microbit> CFLAGS    := -g -Wall -Werror -O2
>  Microbit> I still need to remove the -Werror to resume the build ??
> 
>  Microbit> 2. gdb symlink
>  Microbit> ==============
>  Microbit> ct-ng generates arm-unknown-linux-uclibcgnueabi where I have
>  Microbit> arm-elf-xxx as an alias.
>  Microbit> The build stops when the symlink for gdb fails. I need to manually
>  Microbit> insert a folder 'arm-unknown-linux-uclibcgnueabi' with 'bin' as a
>  Microbit> subfolder under ../output/staging/usr
> 
> Both issues should be fixed in git now.
> 

2010.05 builds 100% fine now, except for the little snag with the gdb
symlink. I'll see if I can figure out what the common denominator is,
but I'm a bit stumped.

I find I still have to manually insert the folder
'arm-unknown-linux-uclibcgnueabi' with 'bin' as a subfolder under
buildroot-2010.05/output/staging/usr

(ext toolchain built with CT-NG 1.6.1, alias used is 'arm-elf-xxx'

Can you advise ?

All the best
Kris

[Buildroot] Buildroot 2010.05-rc3 released :: 2 build errors - lockfile-progs & gdb

[Thomas Petazzoni]

On Wed, 02 Jun 2010 04:30:22 +1000
Microbit_Ubuntu <microbit@virginbroadband.com.au> wrote:

> 2010.05 builds 100% fine now, except for the little snag with the gdb
> symlink. I'll see if I can figure out what the common denominator is,
> but I'm a bit stumped.
> 
> I find I still have to manually insert the folder
> 'arm-unknown-linux-uclibcgnueabi' with 'bin' as a subfolder under
> buildroot-2010.05/output/staging/usr

Can you give a .config or reproduction steps for this ?

> (ext toolchain built with CT-NG 1.6.1, alias used is 'arm-elf-xxx'

FWIW, arm-elf is a prefix typically used for bare-metal toolchains, but
here you're doing an uClibc/Linux toolchain, which is fairly different.
It probably doesn't cause particular problems but might be confusing.

Regards,

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