owing fast already!
Here's a free link so all can read.
http://lwn.net/SubscriberLink/481055/581bc0245cc94be4/
Buy a subscription if you don't have one. In fact perhaps linaro
should have a corporate sub?
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonbo
g this, not
least because now everyone has SD-card based systems disk space mostly
stopped being an issue. People using 'proper flash' still care.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
+++ C.A, Subramaniam [2012-02-20 13:32 -0600]:
> On Mon, Feb 20, 2012 at 12:40 PM, Wookey wrote:
> Would there be a buildroot like setup? Like Wookey mentioned size does matter.
No, if you want to use buildroot, use buildroot (or openbricks, or
yocto, or OE). Debian/Ubuntu are binary distr
is possible to
make a debian-based image this small, but it is not a sustainable
thing without changes in Debian/Ubuntu to support a busybox base.
Nobody is really working on this because there are so many other ways
to achieve an image of this size which, frankly,
+++ Zach Pfeffer [2012-02-29 11:38 -0600]:
> Come one and all to change the world
Difficult without some clue as to what '#img' might be or where it might
be found. IRC channel? twitter hashtag? some website I've never heard
of? Something else?
Wookey
--
Principal hats:
airly trivial matter of telling openjdk to use jogl
and then 'stuff goes fast'. If we aren't doing this already in our
images we probably should be.
Just posting so that whoever worries about graphics and java and stuff
knows about this.
Wookey
--
Principal hats: Linaro
-dependency/cross-building issues summarised here:
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/MultiarchCrossBuildStatus
with logfiles here
http://people.linaro.org/~wookey/buildd/precise/sbuild-ma/status.html
There is a pile of stuff, much of which is _really easy_. This page
tells
installable):
http://edos.debian.net/weather/weather.php?distro=testing&arch=armhf
(Is anyone running edos-distcheck on Ubuntu?)
The ongoing 'make multiarch cross-building work' process is also still
running and there are still easy pickings:
Logfiles:
http://people.linaro.org/~wookey/
etimes years, for people to get what we are doing via a
distro, and that's too long for many of them, which is where the
pressure comes from. We are all aware of that tension.
So are we a distro now or not?
Wookey
--
Principal hats: Linaro,
hat I'm not involved with the Debian arm kernel team, so
this is merely my general impression from afar. Someone closer to the
problem could be more authoratative.
Wookey
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
+++ Arnd Bergmann [2012-05-04 15:17 +]:
> On Friday 04 May 2012, Russell King - ARM Linux wrote:
> >
> > On Fri, May 04, 2012 at 03:20:57PM +0100, Wookey wrote:
> > > Debian tries very hard not to support anything in the kernel that
> > > upstream don't s
d to find it.
This is one of the clearest docs currently:
http://suihkulokki.blogspot.co.uk/2012/04/cross-compiling-with-multiarch-congrats.html
The details are also on the linaro wiki here:
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/UsingMultiArch
Linked from the index page:
https://wik
et more than enough
mail (especially from bloody launchpad :-), please try not to send
this sort of spam to all - just people who will finds it useful.
Ah, that's better...
Wookey
(who has lost his sig)
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
t missing files as it looks for amd64 on ports.u.c and arm* on
archive.u.c
Sadly this can't be automagically configured because of bug
https://bugs.launchpad.net/launchpad/+bug/645127
Wookey
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
l
On Ubuntu (dpkg 1.16.1 to < 1.16.3) it is:
echo "foreign-architecture armel" > /etc/dpkg.cfg.d/multiarch
That should allow $package:armel as well as $package:armhf packages to
be installed, but I don't know if that will actually solve your problem.
Wookey
__
count. It'd be
good not to be scrambling to do that at 1am monday morning.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.o
could also be part of it, or at least request a few
> > topics to be covered.
> > Package cross build and multi-arch would be interesting to have.
Yep. I'll be back from hols by then (just) so should be able to do something
on how to do M-A crossbuilds.
How does it work - one do
d. I suspect all of those are mixed in.
Interesting nevertheless.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
gt; I assume the Ogg encoder is fixed-point and therefore doesn't get the hf
> benefit.
You need to link against libtremor to get integer ogg en/decoding and
few apps do, so I'd expect it to be fp too. But without the details of
what was tested we can't tell from here.
Woo
ive-build :-) there are an awful lot
fewer things to go wrong and the tools are much more mature. There is
plenty of work going on at the moment to improve the situation, and at
least your source package is farily well-behaved (many aren't). It
does look like it needs a couple of f
urrent
> problems. If it's just too much of a pain, I'll have to give wheezy a try, but
> I don't think it'll be as easy to get wheezy up and running on the
> pandaboard.
This thread suggests it's perfectly do-able:
http://groups.google.com/group/pandaboard/browse_thread
accounts.
I always knew this cloud thing was a bad plan...
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
+++ Christian Robottom Reis [2011-08-25 12:00 -0300]:
> On Thu, Aug 25, 2011 at 03:43:50PM +0100, Wookey wrote:
> > Peter Pearse collected all his ALIP cross-build status work in a
> > google doc spreasheet using his @linaro.org login:
> > PPearses ALIP build status google
vg is >50 on this
> package, hm, forget about this, I'll just probably file a BR on the
> package)
> rawtherapee
> rosegarden
heh - only the easy stuff :-)
useful list of things to test though. cheers.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
ltiarching system libraries isn't going to
help much.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
g-query -l multiarch-support
That's not the package that's complaining.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
> * Ethernet
>
> Was buggered, is fixed now :-)
When did it become un-buggered? Tim Klein here is trying to get said
machine to boot over TFTP with NFS root and it just hangs at init.
Which rootfs version and kernel are known to work?
Wookey
--
Principal hats
rted packages, and
this HOWTO makes it easy to set up a consistent build environment, so
do give it a try and get stuck in if you'd like to see this working
fully sooner rather than later.
Reports of success, breakage, miserable failure, or how this
almost-but-doesn't-quite address your u
+++ Michael Hope [2011-10-12 09:17 +1300]:
> On Wed, Oct 12, 2011 at 1:23 AM, Wookey wrote:
> > One output from the 11.09 release was a reasonably painless way of
> > cross-building whole images against an archive, which also forms the
> > basis for an auto-crossbuilder
+++ Zach Pfeffer [2011-11-08 12:06 -0500]:
> (How cool is that date?)
11/11/11 has been declared 'Spinal Tap day'.
A moment's thought will explain why :-)
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
h
re not being
(unduly) left in the lurch?
Do we have our 'end-of-support' criteria written down somewhere? I think they
should contain something more than 'member says so', which seems to be
where we are currently at. But if in fact that really is how it's
going to work then
disclaimer: I know nothing at all about this except what I
just read in that thread. Please refer to the thread for details.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
__
are at least 5 different graphics
cores available, and 3 or 4 of them have RE projects to free them up,
but it'll be a while before any are in useful shape.
If you have any relevant expertise (or would like to aquire some) you
will be exceedingly welcome to help out.
http://limadriver.org/
h
bly an autoreconf.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
4' and get a working cross-build environment.
The repo is here:
http://people.debian.org/~wookey/bootstrap.html
That should be useable for both dpkg-cross style bulding or
multiarch-style bulding.
The repo also contains updated dpkg-cross, multiarch python, multiarch
perl, updated dpkg wi
opic)?
Arguments about the admin load of moderation, or the difficulties of
spam-filtering accurately on an open list, I can understand; but the
idea that this list should be restricted to only suitably enlightened
people by default seems wrong to me. It should be as open as we can
practically make it,
--host arm64 '.
The current bootstrap packageset status is here:
http://people.linaro.org/~wookey/buildd/raring-arm64/status-bootstrap.html
There is no armv8 (arm64/aarch64) hardware available yet, so this image can
currently only
be run in a model. ARM provide a free-beer prorietary 'Foun
+++ Ian Campbell [2013-02-27 12:00 +]:
> On Wed, 2013-02-27 at 02:10 +0000, Wookey wrote:
> >
> > Setting up an arm64 build environment is very simple. Use
> > sbuild-createchroot or mk-sbuild
> > and point at the bootstrap repo, with a bit of config and some updat
+++ Wookey [2013-02-27 02:10 +]:
> State of the Debian/Ubuntu arm64 port
> =
>
> *** Arm64 lives! ***
>
> Executive summary
> -
>
> * There is now a bootable (raring) image to download and run
> * A bit m
cross anyway so some hacking will be needed)
It also need multiarch python, which is not in quantal. You can add my
quantal-bootstrap repo which has a suitable python in it:
--- /etc/apt/sources.list.d/quantal-bootstrap.list
deb [arch=armhf] http://people.debian.org/~wookey/bootstrap/ubunture
gmodule-no-export-2.0 gobject-2.0`
> debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libgstreamer-1.0.so
> -Idebian/tmp/usr/include/gstreamer-1.0
> perldoc -o man debian/dh_gstscancodecs >
> debian/tmp/usr/share/man/man1/dh_gstscancodecs.1
This is wrong. It should be:
$(DEB_HOST_GNU_TY
t the usual way of working...
Yes, the debian/ubuntu default is to build natively, which avoids the
problems of cross-tools and cross-dependencies. The catch is that,
whilst it gets faster by the day, it's still generally slower than
crossbuilding on a fast x86 box. A chromebook or arndale boar
dd to recommend this one unless someone says 'I
have to have really cheap, but need full linux, I need easy IO Pins and
really don't care about freeness'. Or possibly 'I am clueless noob and
heard there is an RPi club near here'. Otherwise I'd suggest any
nu
nd
for running a POS system, and I'm not aware of any of them being aimed
at low-volume manufacturers who aren't wanting to lay out their own
boards (which sounds like where you are coming from).
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware
orking out how the Jenkins part of it works
and implementing faster ubuntu kernel builds (by crossing them instead
of native-building on canonical PPAs) (I'm still kicking this, but I
hope it'll be running any day now), but there is piles of other
stuff that only Fathi and the Lava pe
dency and the following pages are linked
> to this issue (directly or indirectly) and I have tried all of them
> without any success:
> https://bugs.launchpad.net/linaro-oe/+bug/1097561
> http://people.debian.org/~wookey/bootstrap.html
> http://wiki.xen.org/wiki/Xen_ARM_wit
h crossbuilding' is woefully out of date.
If I was being snarky I might point out that this would already have
been working and up-to-date when you wanted to use it if people hadn't
insisted that this work was not wanted and I should stop. Still, it
didn't take long to get going, a
> On 05/17/2013 07:16 PM, Wookey wrote:
+++ Mian M. Hamayun [2013-05-20 20:13 +0200]:
> Hi,
>
> First of all, many thanks for your kind support. I have been able to
> setup a crossbuild chroot environment for aarch64. I can now
> configure and compile qemu using this envir
concept of making existing
linux-arm cross-compilers, with M0 and M3 support included, and using
spec-file jiggery-pokery to get them to DTRT for M* targets. This
should be possible, but advice from anyone who's every actually tried
on the gotchas would be good.
cheers
Wookey
--
Principal hats: L
+++ Matthew Gretton-Dann [2013-08-19 16:58 +0100]:
> On 19 August 2013 15:04, Wookey wrote:
> > Debconf13 (last week) considered the matter of bare-metal
> > cross-toolchains in Debian.
> > The linaro embedded toolchains
> > (https://launchpad.net/gcc-arm-embedded/
y difficult for many
years. Solutions are coming (debile and pybit are current contenders),
but sadly it's not easy, and nor is it documented. I really hope this
will finally get fixed soon - some progress was made at debconf and I
hope to try it (and document it if it works) soonish.
Wookey
-
+++ Matthias Klose [2013-08-21 22:31 +0200]:
> Today the debian-cr...@lists.debian.org ML was created.
> Please subscribe to this list if you are interested in cross build issues.
Here: https://lists.debian.org/debian-cross/
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloo
ds
SIP/XMPP accounts for everyone, and we'd be smart to run our own turn
server.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.li
And Ubuntu Saucy now has lots of arm64 packages you can use:
http://ports.ubuntu.com/dists/saucy/main/binary-arm64/
So you should be able to debootstrap an arm64 image and add armhf binaries to
it, or vice versa.
I've not actually tried that so I don't know how well it works. There may sti
think of good reasons why it could
go either way. Does anyone else know for sure?
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
gt;linux)?
Maybe. Not sure what a coreisbr-unknown-linux-gnu is.
Here is a build log from an (ubuntu) gmp cross-build which might give some
clues:
http://people.linaro.org/~wookey/buildd/quantal-arm64/sbuild-ma/gmp_2:5.0.2+dfsg-2ubuntu2arm64-quantal-bootstrap-arm64-20121117-234708.6930.log
line (which of course
the axf wrapper makes awkward - see below).
Here is an ubuntu arm64 rootfs + suitable kernel images
http://people.debian.org/~wookey/bootstrap/rootfs/
(and a debian one as of last week)
https://wiki.debian.org/Arm64Port#Pre-built_Rootfs
They also work (a whole lot faster) with
+++ Christopher Covington [2013-11-27 11:17 -0500]:
> Hi Wookey,
>
> > There is a wiki page somewhere for wrapping your own kernel with
> > bootwrapper foo, but I found it much easier to use a handy internal tool
> > which
> > rewrites the kernel command line inside
at,
but it looks like we have at least two issues..
So this mail is really to ask what the best fix is and thus who will
deal with it? Do I need to file a bug or a card somewhere?
Possibly more to follow when I work out what else is wrong...
Wookey
--
Principal hats: Linaro, Em
+++ Arnd Bergmann [2014-01-29 18:14 +0100]:
> On Wednesday 29 January 2014 16:36:49 Wookey wrote:
> > Running 32-bit binaries is quite seriously broken until this is fixed. I
> > presume this currently isn't on anyone's list to fix? I'm not sure who's
> > l
Hangout audio and video is regularly broken for people which causes
general aggravation for people in meetings. Could we have a
'test/corridor/watercooler/coffeemachine' hangout somewhere for people
to test if it's working for them today?
Maybe there is one already?
Wookey
--
+++ Nicolas Dechesne [2014-02-11 09:24 -0700]:
>Le 11 f�vr. 2014 09:18, "Wookey" <[1]woo...@wookware.org> a �crit :
>>
>> Hangout audio and video is regularly broken for people which causes
>> general aggravation for people in meetings.
+++ Wookey [2014-01-29 16:36 +]:
> Someone asked if this worked, and I thought 'that's trivial to test with
> multiarch' so I did.
> On Saucy (where there is no multiarch version skew issue between binary
> versions of packages) the
> dpkg --add-architecutre ar
keys
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Issues ==
* Too many packages are buildable but not rebuildable.
* Having to build NMUs twice in slightly different formats for
debian-ports unreleased and debian proper bug/upload is a pain.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http
(DEVPLAT-221: 10%)
* Worked on arm64 NMU process with Chen (DEVPLAT-221: 5%)
* Some bootstrap sprint organising (5%)
== Plans ==
* Fix/Build soprano (DEVPLAT-217)
* NMU pile of packages
* Test Arm64 rootfs on ARM hardware
== Issues ==
Wookey
--
Principal hats: Linaro, Emdebian, Wookware
-217: 5%)
* Tried to port emacs23 as it's causing many build failures. Failed so
far (hangs during build): #752031 (DEVPLAT-221: 10%)
* Rebuilt packages for colord transition: (DEVPLAT-221: 5%)
* Set up sortblockers script: (DEVPLAT-221: 10%)
http://people.debian.org/~wookey/boot
eakage (10%)
* GSOC midterm evaluation (15%
== Plans ==
* Finish/test/upload openjdk/zookeeper
* Fix/NMU remaining packages in SCC
http://people.debian.org/~wookey/bootstrap/blockerlist
* Investigate PDF build errors.
* Mail release team about arm64 prospects
== Issues ==
NMUing gets tediou
-binutils package (now in Archive) (DEVPLAT-220) (5%)
* Finalised Bootstrap/crossbuild sprint for Paris/August (20%)
* Extended sortblockers script to generate outofdate list:
http://people.debian.org/~wookey/bootstrap/outofdatelist (2%)
* Investigated crappy connection to china (losing 60% of my packets
packages (10%)
* Bootstrap/crossbuild sprint travel booked
* Bootstrap/crossbuild sprint cat-herding (5%)
* Updated cross-binutils build for latest binutils - uploaded (5%)
== Plans ==
* Fix/NMU remaining packages in SCC
http://people.debian.org/~wookey/bootstrap/blockerlist
* Investigate PDF build
(DEVPLAT-220: 5%)
* Worked on breakage in current cross-gcc packages for upcoming sprint:
(DEVPLAT-220: 5%)
== Plans ==
* Get cross-toolchain packages into buildable state
* Add multiarch builds to sbuild
* Fix/NMU remaining packages in SCC
http://people.debian.org/~wookey/bootstrap
oad that would be helpful (now that no-one actually _does_ releases
anymore and you just have to know when a 'good' git commit point
happens :-)
That should propogate to ubuntu too, but doesn't seem to have done so
yet, and they just froze imports to utopic, so $someone should poke
$som
(DEVPLAT-220: 5%)
* Worked on breakage in current cross-gcc packages for upcoming sprint:
(DEVPLAT-220: 5%)
== Plans ==
* Get cross-toolchain packages into buildable state
* Add multiarch builds to sbuild
* Fix/NMU remaining packages in SCC
http://people.debian.org/~wookey/bootstrap/blockerlist
r britney cross-arch processing discussed (DEVPLAT-220 3%)
debile (buildd) cross-support designed with developer
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@l
)
== Plans ==
* Get cross-toolchain packages into testing before freeze
* Upload multiarch-ready sbuild
* Enable new buildd hardware
== Issues ==
Shortage of hours in day.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org
on turfan (APM
machine)(CARD-1586: 20%)
== Plans ==
* Get cross-toolchain packages into testing before freeze
* Upload sbuild with profile support
* Enable new buildd hardware
== Issues ==
Shortage of hours in day before freeze
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloon
into testing before freeze
* Enable new buildd hardware
== Issues ==
Shortage of hours in day.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http
s)
* built and uploaded cross-binutils-0.13 (DEVPLAT-220: 10%)
== Plans ==
* Get cross-toolchain packages into testing before freeze (looking iffy)
== Issues ==
Shortage of hours in day.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wo
FTPmasters
(DEVPLAT-220: 20%)
== Plans ==
* Fix more arm64 build failures
* Build within-arch crosstoolchains to break impasse
== Issues ==
Gcc maintainer has torpedoed multiarch-built cross-toolchains in Jessie. (
DebianBug: 766619)
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard
%)
* Wrote and Presented ARM in Debian, Debian in arm:
wookware.org/talks/debianinarm/reveal 20%
* Admin catchup on 3 months of expenses 10%
= Plans ==
get standalone builds working
== Issues ==
Cross-toolchain build-method disagreements
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
porterbox configured
* Investigated gccxml (hard to backport - ancient gcc ver): 15%
= Plans ==
get standalone builds working
== Issues ==
Cross-toolchain build-method disagreements
Looks like cross-toolchain packages won't make Jessie
Wookey
--
Principal hats: Linaro, Emdebian, Woo
== Progress ==
* Updated xbuilder to 1.1. Uploaded to Debian (NEW)
* Ran cross-build tests on Jessie with new toolchains:
https://people.linaro.org/~wookey/buildd/testing/sbuild/latest/status.html
* Set up new emdebian server after crack.
* Cross-toolchain design work with team - udated wiki
affected arm64 packages
* Upgraded desktop to jessie
= Plans ==
get standalone builds working
== Issues ==
Cross-toolchain build-method disagreements
Wookey
--
Principal hats: Linaro, Wookware, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro
-toolchain build methods at
https://wiki.debian.org/ToolChain/Cross
= Plans ==
get multilib cross-gcc builds working
== Issues ==
Cross-toolchain build-method disagreements
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org
lans ==
== Issues ==
Breakage from Jessie upgrade (no printing, schroots bunged up, 30G of logs
filled /)
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
with jessie arm64 qemu setup for students (25%)
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
JTAG is always cranky in my
experience with tedious wrinkles about different dongles, interface
boards and strange effects of other devices if, for example, the JTAG
pins on the CPLD get re-used.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
__
v4t-nothumb-novfp
maximum-compatibilty flavour: http://emdebian.org/crosstools.html
('binary toolcahins' link).
This issue is a useful subject for UDS discussion, I believe.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
__
+++ Andrew Stubbs [2010-10-07 12:46 +0100]:
> On 07/10/10 12:03, Wookey wrote:
> A possible solution to the problem would be to include the sources to
> libgcc.a in the installation, and teach gcc to compile it on-the-fly, as
> necessary.
If it was possible to separate-out libgcc
y. I'll have a look later. Is any of this stuff available/in maverick yet
so I can try to reproduce?
I suggest you file a bug too.
Are you using xdeb 0.6.3?
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
d idea. I've been planning to send a 'the state of cross building
at the end of this cycle' mail very soon (once specs are done with),
to say what we have so far, what works and what doesn't. (before we
mess with things again :-)
> On Wed, 2010-11-10 at 21:30 +, Wookey wrote:
ood overview. That has a currently more-or-less empty 'Rebuilding
everything for a new ABI/flavour section. I'll fill that out now.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
quite sure what is was you wanted to do. Ask again if I haven't helped.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Does anyone disgree with the above conclusions? And do people agree
that policy 8.2 could be clearer on this point?
I've filed a bug containing some of the above discussion and a patch
for tcl8.5. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611650
Wookey
--
Principal hats: Linaro,
;s actually correct. Its policy of only crossing arch-dependent
files is the right one, I believe. (It does allow symlinks within
/usr/src which presumably has/had a good reason.)
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
__
+++ Loïc Minier [2011-02-01 12:50 +0100]:
> On Tue, Feb 01, 2011, Wookey wrote:
> > But if something is looking for arch-independent stuff in /lib then in
> > general that's wrong, and I'm not aware of any examples of
> > correctly-packaged packages that need t
before
installing it
make[4]: *** [install-libLTLIBRARIES] Error 1
I note that when doing this libtool --config shows that it does have
an idea of where the right place is:
maverick)wookey@kh:~/ubuntu/maverick/build/pcre3$ ./libtool --config | grep
sys_lib
sys_lib_search_path_spec="/usr/lib/
st fit on and there is no room to generate an apt-cache?
One thing that has been missing from apt for a long time is ability to
split upgrades into coherent chunks so an upgrade requiring downloads
larger than the space available can proceed.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, B
it with
> the emdebian folks-- there's a risk of reinventing what they do; plus
> they certainly have tools which are useful for this.
Indeed.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
using apt and dpkg for resolving and
installing). It's probably a better tool for making nano images than
debootstrap, which has a more conventional focus. Certainly worth
looking into.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
_
1 - 100 of 144 matches
Mail list logo
