+++ Marc-André Moreau [2011-06-26 10:41 -0400]:
Nothing wrong with this method, and it is reliable, but I find it quicker and easier to use multistrap and do: multistrap -fWill look into that, it could save me time
sorry that should read multistrap -f /usr/share/multistrap/ubuntu/armel.conf
but then I realised that it's not been updated for natty. I'll do an upload forthwith.
> xapt: > > The problem is then that xapt will fail to install the converted packages, > saying the package architecture is different from the current architecture, as > well as missing dependencies.
You are suffering from this problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629595 which is because we are in the middle of a transition to multiarch packages.
Ok, so I should assume that this stuff is broken for pretty much anyone using natty?
Essentially yes. I'll see if I can get an xapt (or dpkg-cross) update pushed in.
however there is then a link failure, when it tries to link the wrong arch of libpthread.so: /usr/lib/gcc/arm-linux-gnueabi/4.5.2/../../../../arm-linux-gnueabi/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libpthread.so when searching for -lpthread /usr/lib/x86_64-linux-gnu/libpthread.a: could not read symbols: File format not recognized collect2: ld returned 1 exit statusIf I understand correctly, xapt is broken on natty, so I could give this build of xapt a try, but then when trying to build FreeRDP I'll still have the problem described above?
Correct. I'll have a look at that to see what's going on there and what options we have to fix it. Something is pointing at the wrong-arch version.
> deb [arch=armel] http://ports.ubuntu.com/ natty main universe > deb-src [arch=armel] http://ports.ubuntu.com/ natty main universe That looks OK (except the last line should be: deb-src http://ports.ubuntu.com/ natty main universe (It doesn't actually break anything - just makes no sense - Have I left that in a doc somewhere?)Hum... not sure where I read that, are you referring to the [arch=armel] part? I read in certain places that it was something new that should be there, but it didn't change anything.
You need [arch=armel] for the binary line, but not the source line (where it is meaningless). Change it if you see it in docs.
So, the easiest way to get cross-building is to do it on a debian wheezy machine/chroot where the tools and build work OK. As you want to do neon dev then you may need to install a new-enough cross-toolchain, which probably means a linaro one.I see the linaro wiki and website refer to ubuntu a lot, and not necessarily debian. There is also much more support and documentation for ubuntu rather than debian for the pandaboard. I understand it would be much easier to get it to compile in the first place with debian wheezy, but I would prefer staying with ubuntu, if it is possible. I tried just tried xapt in oneiric, it doesn't seem to be fixed :( Besides xapt, what would be seriously broken in ubuntu natty? Maybe I could just compile the latest version of xapt myself on natty?
linaro does currently do much of its work in Ubuntu so you are likely to find latest stuff there. On the other hand Debian on panadaboard works fine too SFAIK, so they are probably both reasonable choices.
In general the cross-tools should work the same in both, but it's one area where some stuff happens first in Debian. I don't expect anything else to be seriously broken in natty, but then I don't expect different link behaviour for a given build on the two systems either, so you never know until you try.
So, is a wheezy-based build sufficient for you for the time being? Or do you have to have it building on natty to do useful dev?My main problem would be debian support on the pandaboard which is much less documented than ubuntu. I'd prefer working around the various issues found in natty and work with natty instead, if we can work around all the current 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/thread/94773021fbe2a...
but natty/onieric needs fixing anyway, so I'll do that, which will, as you say probably give you an easier life overall.
Wookey