I'm considering getting a Dell Streak when they release in the USA -
probably around the 19th.
Does anyone know if that would work for Linaro Dev?
Thanks
Joel
--
The cyder is strong in this one Lord!
Hey
Sorry for the belated post; please find below the minutes from Monday's
Toolchain Working Group meeting and the activity reports from the
preceding week.
You can find the full meeting notes at
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-07-12
= Monday 12th July 2010 =
== Agenda ==
* Review action items from last meeting
* New linaro-toolchain mailing-list
* Topics for sprint [[Internal/Events/2010-07-PlatformSprint]]
* Release, version numbers, uploading tarballs
* No meetings next week
* Blueprint status
* Initial delivery of Linaro GCC 4.4
* Cross Compiler Packages
== Action Items from this Meeting ==
* Andrew to propose the triplet change to toolchain upstream
* Andrew to send email to Debian ARM on best triplet
* MLH to pickup perl if pbrook doesn't have a patch by Monday evening UTC
* MLH to write up wants as a toolchain developer/tester
* Marcin to check if xdeb incorrectly produces a package findutils-armel
* Loic to push changes on mysql
== Action Items from Previous Meeting ==
* Loic and Andrew to extend wiki page to track progress of the merging
of Ubuntu patches, assignees etc. DONE
* Loic to setup and run a call on merge workflow with bzr DONE
* Matthias to sort autotools issues with new cell-4.4 Linaro patch or
to ask Ulrich for help :-) DONE
* Marcin to fix -gcc symlink (LP #600927) and update-alternatives
installability issue in his public cross-compiler packages DONE
* Yao to update
https://wiki.linaro.org/WorkingGroups/ToolChain/UbuntuGCCPatches wiki
page for the issue with ADA support and the patches he merged
* Yao to update
https://wiki.linaro.org/WorkingGroups/ToolChain/UbuntuRegressions
wiki page for the removal of the license patch DONE
* Loic to create a linaro-toolchain-drivers team which can upload
tarballs PARTIAL Group created, tarball upload currently not working
== Minutes ==
* The linaro-toolchain list for toolchain related chatter; please
subscribe!
* Loic called for sprint topics. See
https://wiki.linaro.org/Events/2010-07-PlatformSprint/ToolChainWG
* Meetings have been cancelled for the week of the sprint
* Mentioned the upcoming hardfp port that Debian is investigating
* Port is too large for Linaro itself
* Toolchain should support - best place to support, easiest to
maintain due to doko
* Better choice for Debian as they may get support from Linaro; won't
from CSL 2010 Lite edition
* Noted that there's disagreement on the Debian triplet and position
of the hf marker. Problem is what is correct vs which is the path
of least resistance.
* ACTION Andrew to propose the triplet change to toolchain upstream?
* Noted that the ARM EABI is a family of ABIs that different vendors
take variants from
* ACTION Andrew to send email to Debian ARM on best triplet
* Milestone issue review
* ACTION MLH to try perl if no progress is made by pbrook
* getfem++ can't be reproduced
* vect/* won't fix
* mysql fix is ugly
* pr9771-1.c MLH to continue or send patch otherwise
* neon triggered by march=armv7a which should have occurred with
Lucid GCC
* Can lower priority if a missed optimisation
* MLH wants help on how to best use the packaging system to do what
he's used to such as
* Build exactly what the Ubuntu PPA will end up as
* Build a cross-compiler to try ARM failures on a fast machine
* Do an incremental build
* Do a non-bootstrap build
* Run the compiler under a debugger
* Use the test compiler to build a package
* ACTION MLH to write up wants
* Andrew has a process to build the tarball and will run the
certification process afterwards
* Loic recommended CSL developers to have local hardware
* Blueprints status
* Initial 4.4 release reviewed. Done except Ada patch. Andrew to
edit whiteboard to note
* Update broken Ubuntu patches
* Loic suggests reviewing Ubuntu patches month to month
* Cross compiler (Marcin)
* Tidying up ugly GCC hacks
* Stage 1 is now clean
* ACTION Marcin to check if xdeb incorrectly produces a package
called findutils-armel
* ACTION Loic to push changes to mysql
* Michael will run Wednesday standup call
Activity reports from preceding week:
= Ulrich Weigand =
== GCC ==
* Resolved merge conflicts between cell-branch.diff and gcc444-linaro.diff
(investigated and fixed additional autoconf-related build issue)
* Investigated bug #602287; resolved as won't-fix for Linaro 4.4
* Started investigating bug #602289
== GDB ==
* Completed build and regression test of GDB 7.2 branch on beagle board
* Started working on hardware-breakpoint-support blueprint
== Education ==
* Continued getting familiar with Debian package build process
* Continued getting familiar with Launchpad infrastructure
* Read ARMv7 Architecture Reference Manual
== Infrastructure ==
* Got remote access to Loic's beagle board
* Started process to acquire IGEPv2 board
= Yao Qi =
== Linaro GCC ==
* Ubuntu patch ada-acats.diff on linaro gcc 4.4.
ada-acats.diff and its dependent patches cause some regression
failures. Spent a lot of time on trying different patch sets to
linoar gcc 4.4, but failures do go away. Checked the build log of
ubuntu gcc, and the same failures are there. We decide to leave
this ubuntu patch.
* Merged 19 ubuntu patches to linaro gcc 4.4.
Learn bzr push/merge/branch/commit. Very good version control tool,
and well-collaborated with launchpad.
* Revert license patch in linaro gcc 4.4.
* Merge CS GCC 4.4 patches to CS GCC 4.5.
Choose three patches from Julian's ARM patch list. Two of them are
committed into CS GCC 4.5. The third is sent to CS internal review.
== Misc ==
* Some meetings on linaro status.
= Andrew Stubbs =
== GCC 4.4 ==
* Continued refining the blueprints. We now have the initial 4.4
toolchain delivery blueprint finalised.
* Entered bugs for each of the test regressions in the Ubuntu GCC vs.
FSF GCC.
* Reviewed Yao's launchpad merge request for the Ubuntu GCC patches.
It was all good, so I approved the request and did the merge.
* Reviewed the ARM test failures to make sure they were what we
anticipated they would be.
* Reviewed some of the Ubuntu patches marked "Needs review". Decided
not to use two, rewrote the third and submitted the new patch for
review. Matthias has now accepted it, and applied it to Debian also.
* Found out how to create gnu-style release tarballs and wrote a
Linaro GCC release procedure document for the wiki.
https://wiki.linaro.org/WorkingGroups/ToolChain/GCCReleaseProcess
== GCC 4.5 ==
* Assisted Yao with his patch porting work, and made sure he had
things to do.
= Loic Minier =
* Repaired Beagleboard to boot again
* Cross-built ncurses; did other xdeb tests
* Added color codes and improved structure of
https://wiki.linaro.org/WorkingGroups/ToolChain/UbuntuRegressions and
https://wiki.linaro.org/WorkingGroups/ToolChain/UbuntuGCCPatches
* Discussed armhf port, started
http://wiki.debian.org/ArmHardFloatPort
* Started sprint planning and associated wiki pages
Bye,
--
Loïc Minier
I'm terrible with faces and worse with names. I couldn't resist
knocking up a quick set of flash cards:
http://wiki.seabright.co.nz/linaro-boo/
This is generated from the Engineeering Team wiki page by a simple
Python script. Let me know if you want to be removed.
-- Michael
Hey
I don't quite like the [Linaro-foo] prefix which our mailing-list
software adds to all emails' Subject: line. They clutter the subject
to make filtering easier, but the list software also adds a List-Id
header.
Would anybody mind if we were to remove them?
Thanks!
--
Loïc Minier
Hi
I'm sure people tracking linaro-dev@ will be interested about the
ongoing discussion on a new ARM hard-float ABI port which is taking
place on the debian-arm@ mailing-list:
http://lists.debian.org/debian-arm/2010/07/threads.html#00019
Cheers,
--
Loïc Minier
Hi,
A new Linaro Toolchain mailing-list was just created.
This list will serve Linaro development, discussions, and planning
around the usual bits: GCC, Binutils, GNU C Library / EGLIBC, and GDB
bits -- but the list of tools is very open, so LLVM, Valgrind or QEMU
are fine topics too!
(Discussions around upstream patches or new upstream features should
still be preferably done on the respective upstream mailing-lists.)
Once they see the new list, I bet the folks from the Linaro Toolchain
Working Group will be rushing to subscribe. ;-)
You can subscribe from:
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Read you there!
Cheers,
--
Loïc Minier
Hello everyone!
I'd like to ask for early testing of a new launch-control branch adding
support for generating system profile information on ARM systems. I need
you to find all the ARM hardware you have access to and run a bit of
python code and send me the result. See below for details.
== Prerequisites ==
1) Debian-based system
2) Installed packages:
* python-2.6 (2.5 support is coming)
* python-apt
* python-debian
* lsb-release
* usbutils
== Instructions ==
The branch is at: lp:~zkrynicki/launch-control/hw-profile
Instructions:
$ bzr get lp:~zkrynicki/launch-control/hw-profile \
launch-control.hw-profile
$ cd launch-control.hw-profile
$ ./get-system-profile -i -o system-profile-with-a-sensible-name.json
If something goes wrong please attach the output of the following
commands:
* lsb_release -a
* cat /proc/cpuinfo
* cat /proc/meminfo
* lsusb
* uname -m
Report bugs at: https://bugs.edge.launchpad.net/launch-control/+filebug
== About launch-control ==
Launch control is project that aims to implement the Validation
Dashboard spec. See:
https://blueprints.launchpad.net/ubuntu/+spec/arm-m-validation-dashboard
== System Detection Features ==
Hardware:
* CPU (for x86, x86_64 and arm, PPC is *not* supported yet)
* Board detection
* Memory
* USB
Software:
* distribution
* installed debian packages (via apt)
Best regards
Zygmunt
PS: re-sent from @linaro.org account, ignore the @canonical.com dupe if
it shows up please.
--
Zygmunt Bazyli Krynicki <zygmunt.krynicki(a)canonical.com>
Hi folks
Just a note that gcc-linaro branches have been moved. They used to be
owned by the gcc-linaro-dev team, and are now owned by the
linaro-toolchain-dev team (used also for binutils, gdb etc.). You can
still branch the official aliases:
lp:gcc-linaro/4.4
lp:gcc-linaro/4.5
However, if you had pushed to ~gcc-linaro-dev/gcc-linaro/4.4, you have
to explicitly push once to ~linaro-toolchain-dev/gcc-linaro/4.4
instead:
bzr push --remember lp:~linaro-toolchain-dev/gcc-linaro/4.4
Sorry for the inconvenience.
Thanks,
--
Loïc Minier
Hi
These are the notes from today's standup call, also at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2010-07-09
== Attendess ==
* Marcin Juszkiewicz
* Ulrich Weigand
* Yao Qi
* Andrew Stubbs
* Loic Minier
== Minutes ==
* Yao
* ADA patches cause regressions in the testsuite; deferred
* doko to get back to Yao on the issue
* Merged Ubuntu patches
* ACTION update wiki page
* Worked on reverting the license patch; DONE;
* ACTION update wiki page
* Merging some CodeSourcery 4.4 patches to 4.5 now
* Ulrich
* Working on https://bugs.launchpad.net/gcc-linaro/+bug/602287
* Caused by the inclusion of updated backend features, raising the
test expectations
* No actual regression since 4.4.0
* Final changes are very different and rework the infrastructure
* Decision not to backport the new infrastructure
* Recommendation to ignore failure and mark as wontfix in 4.4
* This is fixed in 4.5
* HW breakpoints and watchpoints
* Expand wiki page
* Request merging in arm_next.git to Nicolas Pitre
* Follow new versions of the patches
* Test gdb part
* Marcin
* working on intermediate stages for linux, eglibc, gcc
* linux patch got rev-ed and is pending a new review
* gcc and eglibc: hackish versions ready, need to cleanup
* Andrew
* Did a release notes wiki page; Loic reviewed
* Updated version in source tree
* Where to host the tarball?
=> Launchpad; ACTION: Loic to create a linaro-toolchain-drivers
team which can upload tarballs
* Need to review the ~4 patches in yellow; thinks it's doable before
release
* Will skip ada ones for now
* Loic
* Created milestone for Tuesday release
* Proof-read various stuff
* Sprint
* Would like to spend time with Michael Hope and Loic to discuss how
we're going to work going forward
* Andrew to discuss multiarch topic
* Ulrich would like to discuss cross-compilation
* Yao will think of some sprint topics
* Marcin would like to discuss the cross-toolchain package and the
automated bootstrap spec
* Loic would like to cover patch tracking; how do we ensure stuff is
upstream and we don't pile up delta
* Multiarch
* Andrew would like to know which advice to follow in the multiarch path bug
=> for now, wait for Steve Langasek's input and implement that
first, as it covers the existing multiarch spec
https://wiki.ubuntu.com/MultiarchSpec
* Michael Hope: stuck on a few things, but more process than code, so
will catchup after call
Thanks,
--
Loïc Minier