[arch-dev-public] bash 4.0 / readline 6.0 rebuilds

Eric Bélanger snowmaniscool at gmail.com
Fri Mar 27 23:43:59 EDT 2009

On Fri, Mar 27, 2009 at 8:01 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On Fri, Mar 27, 2009 at 6:34 PM, Eric Bélanger <snowmaniscool at gmail.com> wrote:
>> On Mon, Mar 2, 2009 at 2:43 AM, Allan McRae <allan at archlinux.org> wrote:
>>> Thomas Bächler wrote:
>>>> Allan McRae schrieb:
>>>>> This is the point of this comment:
>>>>> # Run in minimal chroot to avoid false positives due to dependencies. #
>>>>> Chroot can be built with:
>>>>> # sudo mkarchroot <chrootdir>/root glibc coreutils findutils grep tar
>>>>> gzip
>>>>> So, in your example, if you are testing if libA needs a rebuild due to
>>>>> libC, you only extract libA in your chroot, not libB.  The ldd can not chain
>>>>> its way to libC.  So ti ends up doing the same thing as readelf.
>>>> Now I understand it.
>>>> Still, if you use readelf it does not matter what the environment is, you
>>>> could run it on any system which is not even Arch, or is the wrong
>>>> architecture or anything.
>>> Well, if that did not convince me, this does.  I just noticed that "readelf
>>> --dynamic" appears to be a lot faster than "ldd".  On my /usr/bin/*, readelf
>>> takes ~0.2sec while ldd takes ~12sec.  I will test this out with an actual
>>> run of the script tomorrow.
>>> Allan
>> Status update on the rebuild?
> Well, mkinitcpio fails miserably under bash 4.0, so I definitely don't
> even want to push it to testing yet - and I think it's actually a bash
> issue (It errors saying that ;; is not a valid token in a certain case
> statement... ?).
> I can put up what I have so far somewhere, but I wanted to look at the
> mkinitcpio / bash interaction first before making people's systems
> unbootable (I did it to myself, hah). I've been real busy with work
> deadlines and pycon (which is neat, by the way) to deal with this now.
> I hope I'll have some time this weekend to play with it and get it all
> shaped up - maybe Dusty (who is here at pycon) and I can get the
> readline/bash rebuilds in shape on Saturday.
> Dusty, you interested? We can even do a "ArchLinux packaging" open
> session on it :)

No problem. Take your time. I just asked because I wanted to update 2
packages from your list (fvwm-devel and rosegarden) and wanted to have
that done at the same time as the rebuild. I'll just update them on
Sunday night unless you manage to fix the mkinitcpio issue.

More information about the arch-dev-public mailing list