Progress:
* Some trouble building the SPEC2k tools in the new multiarch world in natty. Perl refuses to link libm and a number of other things also end up failing . Appears to be a real pain with the new multiarch world and SPEC2k's curious build system for its' tools . Will fall back to an older chroot and get the tools built natively.
* Tried breaking down the T2 performance blueprint - initial breakdown now available.
* Looked at the binutils vmov.i64 issue again. Looks like natty-updates will now pick this up.
* Some patch review and bugzilla maintenance.
Plans:
* Get SPEC tools building. * Look more at the T2 performance blueprint * Spend some time on the VFP moves and look at ivopts for a bit. * Merge review duty.
Meetings:
* 1-1s * Linaro calls.
On 05/24/2011 10:26 AM, Ramana Radhakrishnan wrote:
Progress:
- Some trouble building the SPEC2k tools in the new multiarch world in
natty. Perl refuses to link libm and a number of other things also end up failing . Appears to be a real pain with the new multiarch world and SPEC2k's curious build system for its' tools . Will fall back to an older chroot and get the tools built natively.
At least this one isn't specific to spec2k, but is perl itself (having library tests looking into specific locations).
I assume you are not allowed to patch the build system to work around these. So maybe instead of falling back to an older release, maybe create a multiarch-compat package having symlinks for all these moved files in the old places? Yes, it's a hack, and maybe such a package would only live in a PPA.
Matthias
On Tue, May 24, 2011 at 10:35:40AM +0200, Matthias Klose wrote:
On 05/24/2011 10:26 AM, Ramana Radhakrishnan wrote:
Progress:
- Some trouble building the SPEC2k tools in the new multiarch world in
natty. Perl refuses to link libm and a number of other things also end up failing . Appears to be a real pain with the new multiarch world and SPEC2k's curious build system for its' tools . Will fall back to an older chroot and get the tools built natively.
At least this one isn't specific to spec2k, but is perl itself (having library tests looking into specific locations).
I assume you are not allowed to patch the build system to work around these. So maybe instead of falling back to an older release, maybe create a multiarch-compat package having symlinks for all these moved files in the old places? Yes, it's a hack, and maybe such a package would only live in a PPA.
It would certainly be a hack; the set of libraries you would be providing compat symlinks for is arbitrary, and you can't just symlink the directories together. I think PPA-only would, sadly, be the best approach.
linaro-toolchain@lists.linaro.org
-
Matthias Klose -
Ramana Radhakrishnan -
Steve Langasek