Re: building qt4 for arm
On Fri, 2013-02-15 at 10:00 +0100, Rieker Flaik wrote:
On Fri, 2013-02-15 at 07:27 +, Neil Williams wrote:
On Fri, 15 Feb 2013 00:10:49 +0100
Rieker Flaik rieker_fl...@arcor.de wrote:
On Tue, 2013-02-12 at 16:34 +, Neil Williams wrote:
On Tue, 12 Feb 2013 16:28:17 +0100
Rieker Flaik rieker_fl...@arcor.de wrote:
animation/qsequentialanimationgroup.cpp:467: warning: unused
variable ‘q’
../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:
Assembler messages:
../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131:
Error: no such instruction: `swpb %al,%bpl,[%rbx]'
../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131:
Error: no such instruction: `swpb %al,%bpl,[%rbx]'
Due to lack of cross-dependencies, the wrong headers got included. That
resulted in x86 assembly being included into the armel cross build, not
surprisingly, that doesn't work.
Have you installed all of the cross dependencies?
I hope so:
/foo/bar/qt4-x11-4.6.3$ sudo embuilddeps -n -a armel
Constraint 'libjpeg-dev' is not available, omitting. (This could be a
virtual package or a bug.)
Checking that build dependencies 'debhelper (= 7.4.13), quilt,
pkg-kde-tools (= 0.6.4), flex, sharutils, firebird2.1-dev [amd64 armel
i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 sparc],
libasound2-dev [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386],
libaudio-dev, libcups2-dev, libdbus-1-dev, libfreetype6-dev,
libgl1-mesa-dev | libgl-dev, libglib2.0-dev, libglu1-mesa-dev |
libglu-dev, libgtk2.0-dev, libice-dev, unixodbc-dev, libjpeg-dev,
libmng-dev, libmysqlclient-dev, libpam0g-dev, libpng12-dev, libpq-dev,
libreadline-dev, libsm-dev, libsqlite0-dev, libsqlite3-dev,
libtiff4-dev, libx11-dev, libxcursor-dev, libxext-dev, libxft-dev,
libxi-dev, libxinerama-dev, libxmu-dev, libxrandr-dev, libxrender-dev,
libxslt1-dev, libxt-dev, libxtst-dev, zlib1g-dev, freetds-dev' for
qt4-x11 are installed.
No build dependencies to install for qt4-x11
Constraint 'libjpeg-dev' is not available, omitting. (This could be a
virtual package or a bug.)
Checking that cross build dependencies 'debhelper (= 7.4.13), quilt,
pkg-kde-tools (= 0.6.4), flex, sharutils, firebird2.1-dev [amd64 armel
i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 sparc],
libasound2-dev [!kfreebsd-amd64 !kfreebsd-i386 !hurd-i386],
libaudio-dev, libcups2-dev, libdbus-1-dev, libfreetype6-dev,
libgl1-mesa-dev | libgl-dev, libglib2.0-dev, libglu1-mesa-dev |
libglu-dev, libgtk2.0-dev, libice-dev, unixodbc-dev, libjpeg-dev,
libmng-dev, libmysqlclient-dev, libpam0g-dev, libpng12-dev, libpq-dev,
libreadline-dev, libsm-dev, libsqlite0-dev, libsqlite3-dev,
libtiff4-dev, libx11-dev, libxcursor-dev, libxext-dev, libxft-dev,
libxi-dev, libxinerama-dev, libxmu-dev, libxrandr-dev, libxrender-dev,
libxslt1-dev, libxt-dev, libxtst-dev, zlib1g-dev, freetds-dev' for
qt4-x11 are installed.
'qt4-x11' needs 42 cross dependencies installed: libxinerama-dev
zlib1g-dev sharutils libaudio-dev libxi-dev libxmu-dev libgtk2.0-dev
libasound2-dev libdbus-1-dev libpq-dev libglib2.0-dev quilt libx11-dev
libxft-dev libxt-dev libice-dev freetds-dev libgl1-mesa-dev
libsqlite0-dev libfreetype6-dev unixodbc-dev libjpeg-dev firebird2.1-dev
libreadline-dev libcups2-dev libxrandr-dev libxext-dev libpam0g-dev
libmng-dev libxrender-dev flex libtiff4-dev debhelper libmysqlclient-dev
libpng12-dev libsqlite3-dev libglu1-mesa-dev libxtst-dev pkg-kde-tools
libxcursor-dev libsm-dev libxslt1-dev
Use of uninitialized value $multiarch in concatenation (.) or string
at /usr/sbin/embuilddeps line 296.
/usr/sbin/xapt -a armel debhelper firebird2.1-dev flex freetds-dev
libasound2-dev libaudio-dev libcups2-dev libdbus-1-dev libfreetype6-dev
libgl1-mesa-dev libglib2.0-dev libglu1-mesa-dev libgtk2.0-dev libice-dev
libjpeg-dev libmng-dev libmysqlclient-dev libpam0g-dev libpng12-dev
libpq-dev libreadline-dev libsm-dev libsqlite0-dev libsqlite3-dev
libtiff4-dev libx11-dev libxcursor-dev libxext-dev libxft-dev libxi-dev
libxinerama-dev libxmu-dev libxrandr-dev libxrender-dev libxslt1-dev
libxt-dev libxtst-dev pkg-kde-tools quilt sharutils unixodbc-dev
zlib1g-dev
You should have lots of packages installed with the suffix -armel-cross.
Yes I have:
$ dpkg -l | grep armel-cross | awk '{print $2}' | wc -l
258
dpkg -l |grep armel-cross
$ dpkg -l | grep armel-cross | awk '{print $2}' | xargs
base-files-armel-cross binutils-armel-cross bsdmainutils-armel-cross
bsdutils-armel-cross bzip2-armel-cross comerr-dev-armel-cross
coreutils-armel-cross debconf-armel-cross debconf-i18n-armel-cross
debhelper-armel-cross debianutils-armel-cross defoma-armel-cross
diffstat-armel-cross dpkg-armel-cross dpkg-dev-armel-cross
file-armel-cross firebird2.1-common-doc-armel-cross
firebird2.1-dev-armel-cross firebird2.5-common-armel-cross
Re: building qt4 for arm
peter green wrote (ao): Sander wrote: I believe the Armbrix Zero sells for $145 It has the same cpu and memory as the Arndale (Cortex-A15 1.7GHz dual core, 2GB 800MHz DDR3, and sata3), just a little less connectors: http://howchip.com/shop/item.php?it_id=BRIX5250 It's also on a three month lead time and has had virtually no documentation released. I'm not sure if any boards are actually in the wild or even if anyone has ever tried booting regular linux on it yet. Well, I have the Arndale, and it boots with these instructions: https://wiki.linaro.org/Boards/Arndale/Setup/EnterpriseUbuntuServer I can boot a selfconfigured vanilla kernel, but it seems usbsupport is not yet in 3.8-rc7. The kernel from the above instructions works just fine. I'm considering it as a potential buildd but i'm not yet happy enough with the state of the project to actually make a purchase. Right now i'd suggest the odriod U2 as the least bad build box option if you want to go the native route. Downsides are that storage and network end up on USB and you have to recompile the kernel to enable swap. Network on the Arndale/Armbrix is also usb, but it has native sata3, and usb3. The Odriod U2 and X2 seem nice little machines too, thanks for metioning them. Sander -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130213090747.GI31274@panda
Re: building qt4 for arm
2013/2/12 Neil Williams codeh...@debian.org: That doesn't help with the problem that the default Debian build only supports Xorg and most boards are actually going to require QtEmbedded and framebuffer support. If you've only got 256MB of RAM, Xorg is seriously painful. The Qt5 on Debian will btw build the framebuffer and EGL QPA plugins in addition to the XCB plugin. -Timo -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAJtFfx=y9c9colxy6pb0fbphomfc5afyk6qhgvj_dl95onq...@mail.gmail.com
building qt4 for arm
Hi all I'm running debian arm and need to rebuild libqt4 with an additional patch. What is the best and fastest way to rebuild that package? I also want to mention that I already tried several ways (cross-compile and qemu): 1. cross-compile: I have installed the emdebian toolchain by doing: aptitude install emdebian-archive-keyring echo deb http://www.emdebian.org/debian/ squeeze main /etc/apt/sources.list aptitude update aptitude install gcc-4.4-arm-linux-gnueabi cpp-4.4-arm-linux-gnueabi Then I did: apt-get source libqt4-dev dpkg-buildpackage -aarmel -j4 The build-process started but died after 3 minutes with messages like this: animation/qsequentialanimationgroup.cpp:467: warning: unused variable ‘q’ ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h: Assembler messages: ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131: Error: no such instruction: `swpb %al,%bpl,[%rbx]' ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131: Error: no such instruction: `swpb %al,%bpl,[%rbx]' 2. qemu: I pulled the last version of qemu and build it for arm-softmmu. Baked a kernel for machine realview-pbx-a9 so that SMP could be enabled for 4 CPUs. Qemu boots the kernel fine so that I was able to boot into a prior bootstrapped debian over NFS. Here I was able to start a dpkg-buildpackage -j4 for qt4: But it takes forever and only one Host-CPU is used. I'm still searching for a practicable way of rebuilding bigger debian packages. How do you do that? Any hints? Thanks in advance Rik -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1360682897.21620.48.camel@lovely
Re: building qt4 for arm
On 12 February 2013 16:28, Rieker Flaik rieker_fl...@arcor.de wrote: I'm running debian arm and need to rebuild libqt4 with an additional patch. What is the best and fastest way to rebuild that package? Build it on an ARM box, as Debian packages (in general) need to build on native hardware. I also want to mention that I already tried several ways (cross-compile and qemu): 1. cross-compile: I have installed the emdebian toolchain by doing: aptitude install emdebian-archive-keyring echo deb http://www.emdebian.org/debian/ squeeze main /etc/apt/sources.list aptitude update aptitude install gcc-4.4-arm-linux-gnueabi cpp-4.4-arm-linux-gnueabi Then I did: apt-get source libqt4-dev dpkg-buildpackage -aarmel -j4 The build-process started but died after 3 minutes with messages like this: animation/qsequentialanimationgroup.cpp:467: warning: unused variable ‘q’ ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h: Assembler messages: ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131: Error: no such instruction: `swpb %al,%bpl,[%rbx]' ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131: Error: no such instruction: `swpb %al,%bpl,[%rbx]' 2. qemu: takes forever and only one Host-CPU is used. QEMU runs at an equivalent of about 1/12th of the host CPU frequency, so a 2400MHz 386 emulates at about the speed of a 200MHz ARM CPU. I'm still searching for a practicable way of rebuilding bigger debian packages. There's a 500MHz 512MB Debian armel box here that you can use over SSH - write privately if that would be useful. Not that it won't still take forever... (where forever is defined as any time period longer than an hour :) For greater speed, you can buy/borrow/use something like a sheevaplug or whatever the cheap top-end ARM gadget is these days. M -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAL4-wQp8emz-7CCUY7BLdz1no-FU+evK3gGw1-POYjFhfj=n...@mail.gmail.com
Re: building qt4 for arm
Hello, I agree with Martin, it's better to compile Debian packages natively. I would suggest to get something more powerful though. A dual core board like a Pandaboard ES (1.2GHz) or a Snowball (1GHz) can come rather cheap (150-200euros) and are pretty decent for such a task. Ermis On Tue, Feb 12, 2013 at 5:06 PM, martinwguy martinw...@gmail.com wrote: On 12 February 2013 16:28, Rieker Flaik rieker_fl...@arcor.de wrote: I'm running debian arm and need to rebuild libqt4 with an additional patch. What is the best and fastest way to rebuild that package? Build it on an ARM box, as Debian packages (in general) need to build on native hardware. I also want to mention that I already tried several ways (cross-compile and qemu): 1. cross-compile: I have installed the emdebian toolchain by doing: aptitude install emdebian-archive-keyring echo deb http://www.emdebian.org/debian/ squeeze main /etc/apt/sources.list aptitude update aptitude install gcc-4.4-arm-linux-gnueabi cpp-4.4-arm-linux-gnueabi Then I did: apt-get source libqt4-dev dpkg-buildpackage -aarmel -j4 The build-process started but died after 3 minutes with messages like this: animation/qsequentialanimationgroup.cpp:467: warning: unused variable ‘q’ ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h: Assembler messages: ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131: Error: no such instruction: `swpb %al,%bpl,[%rbx]' ../../include/QtCore/../../src/corelib/arch/qatomic_arm.h:131: Error: no such instruction: `swpb %al,%bpl,[%rbx]' 2. qemu: takes forever and only one Host-CPU is used. QEMU runs at an equivalent of about 1/12th of the host CPU frequency, so a 2400MHz 386 emulates at about the speed of a 200MHz ARM CPU. I'm still searching for a practicable way of rebuilding bigger debian packages. There's a 500MHz 512MB Debian armel box here that you can use over SSH - write privately if that would be useful. Not that it won't still take forever... (where forever is defined as any time period longer than an hour :) For greater speed, you can buy/borrow/use something like a sheevaplug or whatever the cheap top-end ARM gadget is these days. M -- To UNSUBSCRIBE, email to debian-embedded-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cal4-wqp8emz-7ccuy7bldz1no-fu+evk3ggw1-poyjfhfj...@mail.gmail.com
Re: building qt4 for arm
On 12 February 2013 17:36, Sander san...@humilis.net wrote: Ermis Papastefanakis wrote (ao): I agree with Martin, it's better to compile Debian packages natively. I would suggest to get something more powerful though. A dual core board like a Pandaboard ES (1.2GHz) or a Snowball (1GHz) can come rather cheap (150-200euros) and are pretty decent for such a task. I believe the Armbrix Zero sells for $145 It has the same cpu and memory as the Arndale (Cortex-A15 1.7GHz dual core, 2GB 800MHz DDR3, and sata3), just a little less connectors: ...and if you need to compile still faster, you can use distcc and ccache on a farm of little ARM boards... though doing this on a heterogeneous network of 200MHz ARMs in 2006 to bootstrap the armel project was fairly excruciating, it should be less painful today. The hard limit is that, for big packages such as GCC, you need more than 256MB of RAM. M -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAL4-wQrnfch6yK_0ie-TtWF=mCSc=jxt2qa4frdguai3rjl...@mail.gmail.com
Re: building qt4 for arm
Ermis Papastefanakis wrote (ao): I agree with Martin, it's better to compile Debian packages natively. I would suggest to get something more powerful though. A dual core board like a Pandaboard ES (1.2GHz) or a Snowball (1GHz) can come rather cheap (150-200euros) and are pretty decent for such a task. I believe the Armbrix Zero sells for $145 It has the same cpu and memory as the Arndale (Cortex-A15 1.7GHz dual core, 2GB 800MHz DDR3, and sata3), just a little less connectors: http://howchip.com/shop/item.php?it_id=BRIX5250A Sander -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130212163607.GA19316@panda
Re: building qt4 for arm
On Tue, 12 Feb 2013 17:51:53 +0100 martinwguy martinw...@gmail.com wrote: On 12 February 2013 17:36, Sander san...@humilis.net wrote: Ermis Papastefanakis wrote (ao): I agree with Martin, it's better to compile Debian packages natively. I would suggest to get something more powerful though. A dual core board like a Pandaboard ES (1.2GHz) or a Snowball (1GHz) can come rather cheap (150-200euros) and are pretty decent for such a task. I believe the Armbrix Zero sells for $145 It has the same cpu and memory as the Arndale (Cortex-A15 1.7GHz dual core, 2GB 800MHz DDR3, and sata3), just a little less connectors: ...and if you need to compile still faster, you can use distcc and ccache on a farm of little ARM boards... though doing this on a heterogeneous network of 200MHz ARMs in 2006 to bootstrap the armel project was fairly excruciating, it should be less painful today. The hard limit is that, for big packages such as GCC, you need more than 256MB of RAM. That doesn't help with the problem that the default Debian build only supports Xorg and most boards are actually going to require QtEmbedded and framebuffer support. If you've only got 256MB of RAM, Xorg is seriously painful. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpwnij7HkxT9.pgp Description: PGP signature
Re: building qt4 for arm
Rieker Flaik wrote: How do you do that? Any hints? One option worth considering is running qemu in user mode though binfmt_support. This has lower overheads than full hardware emulation and will be able to use multiple host CPUs for paralell builds (since each process runs in a seperate emulator). To do this 1: install qemu-user-static and binfmt_support on your host box (I would suggest using the version of qemu-arm-static from wheezy whatever version of debian you are running, the package has no dependencies so installing it on a squeeze box shouldn't be a problem) 2: copy /usr/bin/qemu-arm-static from your host box to the same location in your arm rootfs 3: chroot into the arm rootfs. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/511a9b71.4070...@p10link.net
Re: building qt4 for arm
Sander wrote: I believe the Armbrix Zero sells for $145 It has the same cpu and memory as the Arndale (Cortex-A15 1.7GHz dual core, 2GB 800MHz DDR3, and sata3), just a little less connectors: http://howchip.com/shop/item.php?it_id=BRIX5250 It's also on a three month lead time and has had virtually no documentation released. I'm not sure if any boards are actually in the wild or even if anyone has ever tried booting regular linux on it yet. I'm considering it as a potential buildd but i'm not yet happy enough with the state of the project to actually make a purchase. Right now i'd suggest the odriod U2 as the least bad build box option if you want to go the native route. Downsides are that storage and network end up on USB and you have to recompile the kernel to enable swap. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/511a998f.9090...@p10link.net
