On Fri, Jul 30, 2010 at 4:45 PM, Vishwanath Sripathy vishwanath.sripathy@linaro.org wrote:
Amit, I tried to compile it for OMAP, but it failed to compile. Little digging showed that Make file does not seem to have entries for ARM tool chains. So I think you need to have a config file kind of thing to get powertop cross compiled for arm based platforms.
Yes, but it may not be as simple. PowerTOP uses libncursesw library to link with. Hence for cross compilation we need to make sure that this (or a non-wide char ncurses library, i.e. libncurses) should also be cross compiled for target ARM. And then we should have some option in Makefile (LIBPATH & INCPATH) to point to it.
Will it make sense to have a "readme.ARM" or some other file in powertop which describes this step ? Any suggestions on how best to do this ?
Thanks! -- Regards, Amit Arora
Vishwa
On 10 Jul 30, Amit Arora wrote:
On Fri, Jul 30, 2010 at 4:45 PM, Vishwanath Sripathy vishwanath.sripathy@linaro.org wrote:
Amit, I tried to compile it for OMAP, but it failed to compile. Little digging showed that Make file does not seem to have entries for ARM tool chains. So I think you need to have a config file kind of thing to get powertop cross compiled for arm based platforms.
Yes, but it may not be as simple. PowerTOP uses libncursesw library to link with. Hence for cross compilation we need to make sure that this (or a non-wide char ncurses library, i.e. libncurses) should also be cross compiled for target ARM. And then we should have some option in Makefile (LIBPATH & INCPATH) to point to it.
Will it make sense to have a "readme.ARM" or some other file in powertop which describes this step ? Any suggestions on how best to do this ?
Compiling natively (on target) or in a qemu-based armel environment on the desktop will be required.
I'm hoping our debian friends will suggest some nifty tricks to make this easy.
Regards, Amit
On Fri, Jul 30, 2010, Amit Kucheria wrote:
Will it make sense to have a "readme.ARM" or some other file in powertop which describes this step ? Any suggestions on how best to do this ?
Compiling natively (on target) or in a qemu-based armel environment on the desktop will be required. I'm hoping our debian friends will suggest some nifty tricks to make this easy.
xdeb cross-buildt it fine :-)
xdeb --apt-source -a armel powertop should cross-build the pre-dependencies and powertop itself and output powertop_1.11+git20091208-0ubuntu1_armel.deb which has an ARM ./usr/sbin/powertop
For this to work, you want: * a maverick install or chroot * hrw's cross-toolchain packages installed * xdeb and build-essential installed
I tried to install xdeb on my ubuntu PC (V 10.04), but faced some issues. Attached is the error log. Any inputs?
Thanks Vishwa
On Fri, Jul 30, 2010 at 5:48 PM, Loïc Minier loic.minier@linaro.org wrote:
On Fri, Jul 30, 2010, Amit Kucheria wrote:
Will it make sense to have a "readme.ARM" or some other file in powertop which describes this step ? Any suggestions on how best to do this ?
Compiling natively (on target) or in a qemu-based armel environment on
the
desktop will be required. I'm hoping our debian friends will suggest some nifty tricks to make this easy.
xdeb cross-buildt it fine :-)
xdeb --apt-source -a armel powertop should cross-build the pre-dependencies and powertop itself and output powertop_1.11+git20091208-0ubuntu1_armel.deb which has an ARM ./usr/sbin/powertop
For this to work, you want:
- a maverick install or chroot
- hrw's cross-toolchain packages installed
- xdeb and build-essential installed
-- Loïc Minier
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Mon, Aug 2, 2010 at 5:11 PM, Vishwanath Sripathy vishwanath.sripathy@linaro.org wrote:
I tried to install xdeb on my ubuntu PC (V 10.04), but faced some issues. Attached is the error log. Any inputs? Thanks Vishwa
I just updated the wiki to add a step to mount the proc filesystem
On Mon, Aug 02, 2010, Vishwanath Sripathy wrote:
I tried to install xdeb on my ubuntu PC (V 10.04), but faced some issues. Attached is the error log. Any inputs?
Hmm right, this is ugly; the story is as follows: * xdeb uses a script called "debuild" which wraps the usual "dpkg-buildpackage" providing some nice services (like keeping a build log) * devscripts depends on tons of stuff, including a MTA * the default MTA, Postfix, fails to install in the chroot
Workarounds: * mount /proc as amitk suggested, so that the MTA installs * install without recommends, this probably will avoid pulling a MTA * pull a small MTA explicitly, or a fake one like lsb-invalid-mta (apt-get install lsb-invalid-mta xdeb -- I didn't actually try this one)
Proper fix, not quite sure: * perhaps try removing the dep on devscripts by copying debuild in xdeb, or by replacing the functionality? * only use debuild if available? * provide better instructions on installing xdeb in a chroot (Amit did it I think!)
On Mon, Aug 02, 2010 at 11:58:52AM -0400, Loïc Minier wrote:
On Mon, Aug 02, 2010, Vishwanath Sripathy wrote:
I tried to install xdeb on my ubuntu PC (V 10.04), but faced some issues. Attached is the error log. Any inputs?
Hmm right, this is ugly; the story is as follows:
- xdeb uses a script called "debuild" which wraps the usual "dpkg-buildpackage" providing some nice services (like keeping a build log)
- devscripts depends on tons of stuff, including a MTA
- the default MTA, Postfix, fails to install in the chroot
Workarounds:
- mount /proc as amitk suggested, so that the MTA installs
- install without recommends, this probably will avoid pulling a MTA
- pull a small MTA explicitly, or a fake one like lsb-invalid-mta (apt-get install lsb-invalid-mta xdeb -- I didn't actually try this one)
Proper fix, not quite sure:
- perhaps try removing the dep on devscripts by copying debuild in xdeb, or by replacing the functionality?
- only use debuild if available?
- provide better instructions on installing xdeb in a chroot (Amit did it I think!)
For build environment correctness, it is definitely preferred to avoid following recommends at installation.
On Mon, Aug 02, 2010, Steve Langasek wrote:
For build environment correctness, it is definitely preferred to avoid following recommends at installation.
Yes, but xdeb is more an user frontend, and that's the one pulling devscripts with a depends (because it calls debuild); debuild has a chain of dependencies with recommends which will pull a MTA.
On Mon, Aug 02, 2010 at 03:49:56PM -0400, Loïc Minier wrote:
On Mon, Aug 02, 2010, Steve Langasek wrote:
For build environment correctness, it is definitely preferred to avoid following recommends at installation.
Yes, but xdeb is more an user frontend, and that's the one pulling devscripts with a depends (because it calls debuild); debuild has a chain of dependencies with recommends which will pull a MTA.
Ah - given the errors about missing /proc, I assumed this was all taking place in a build chroot. If this is happening during xdeb installation in a non-pristine chroot, then I'm ambivalent - you should have /proc mounted anyway, and I think worrying about Recommends in that context is splitting hairs. :)
On Mon, Aug 02, 2010, Steve Langasek wrote:
Ah - given the errors about missing /proc, I assumed this was all taking place in a build chroot. If this is happening during xdeb installation in a non-pristine chroot, then I'm ambivalent - you should have /proc mounted anyway, and I think worrying about Recommends in that context is splitting hairs. :)
It's happening during xdeb installation, which for various reasons makes sense to run in a chroot for some cases (it's maverick only, and -cross toolchain and packages will clutter the list of packages)
On 10 Jul 30, Loïc Minier wrote:
On Fri, Jul 30, 2010, Amit Kucheria wrote:
Will it make sense to have a "readme.ARM" or some other file in powertop which describes this step ? Any suggestions on how best to do this ?
Compiling natively (on target) or in a qemu-based armel environment on the desktop will be required. I'm hoping our debian friends will suggest some nifty tricks to make this easy.
xdeb cross-buildt it fine :-)
xdeb --apt-source -a armel powertop should cross-build the pre-dependencies and powertop itself and output powertop_1.11+git20091208-0ubuntu1_armel.deb which has an ARM ./usr/sbin/powertop
For this to work, you want:
- a maverick install or chroot
- hrw's cross-toolchain packages installed
- xdeb and build-essential installed
Got this setup and fixed the wiki documentation along the way.
All my xdeb builds crash and burn with the following error:
arm-linux-gnueabi-objdump: /lib/libm.so.6: File format not recognized dpkg-shlibdeps: error: arm-linux-gnueabi-objdump gave error exit status 1
I've tried grep, powertop and binutils.
I'm running this in a maverick chroot on Lucid (64-bit).
Any clues what might be going wrong?
/Amit
On Mon, Aug 02, 2010, Amit Kucheria wrote:
All my xdeb builds crash and burn with the following error: arm-linux-gnueabi-objdump: /lib/libm.so.6: File format not recognized dpkg-shlibdeps: error: arm-linux-gnueabi-objdump gave error exit status 1
I'm not quite sure; would you mind sharing the full log, and the command you used to build? There's probably a .build log in the dir.
It looks like you're missing the ARM cross libc, or that the build is not configured as a cross-build.
On Mon, Aug 2, 2010 at 7:00 PM, Loïc Minier loic.minier@linaro.org wrote:
On Mon, Aug 02, 2010, Amit Kucheria wrote:
All my xdeb builds crash and burn with the following error: arm-linux-gnueabi-objdump: /lib/libm.so.6: File format not recognized dpkg-shlibdeps: error: arm-linux-gnueabi-objdump gave error exit status 1
I'm not quite sure; would you mind sharing the full log, and the command you used to build? There's probably a .build log in the dir.
It looks like you're missing the ARM cross libc, or that the build is not configured as a cross-build.
Errr, looks like something else is wrong here :)
$ xdeb --apt-source -a armel grep /usr/bin/xdeb:15: DeprecationWarning: please use 'debian' instead of 'debian_bundle' from debian_bundle import deb822 Building source package cache ... Building working tree cache ... Build sequence: pcre3* grep* apt-get -d source pcre3=8.02-1 Reading package lists... Done Building dependency tree Reading state information... Done Need to get 1336kB of source archives. Get:1 http://archive.ubuntu.com/ubuntu/ maverick/main pcre3 8.02-1 (dsc) [994B] Get:2 http://archive.ubuntu.com/ubuntu/ maverick/main pcre3 8.02-1 (tar) [1248kB] Get:3 http://archive.ubuntu.com/ubuntu/ maverick/main pcre3 8.02-1 (diff) [87.5kB] Fetched 1336kB in 1s (994kB/s) Download complete and in download only mode dpkg-source -x pcre3_8.02-1.dsc pcre3 gpgv: Signature made Fri May 7 20:20:38 2010 UTC using DSA key ID 8B0D42F9 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./pcre3_8.02-1.dsc dpkg-source: info: extracting pcre3 in pcre3 dpkg-source: info: unpacking pcre3_8.02.orig.tar.gz dpkg-source: info: applying pcre3_8.02-1.diff.gz dpkg-source: info: upstream files that have been modified: pcre3/Makefile.am pcre3/Makefile.in pcre3/config.h.in pcre3/config.sub pcre3/configure pcre3/configure.ac pcre3/doc/pcre_version.3 pcre3/doc/pcreapi.3 pcre3/doc/pcregrep.1 pcre3/ltmain.sh pcre3/pcrecpp.cc
pcre3 does not show in 'apt-rdepends grep', so I am not sure what is going on here...
Dnia poniedziałek, 2 sierpnia 2010 o 18:54:11 Amit Kucheria napisał(a):
pcre3 does not show in 'apt-rdepends grep', so I am not sure what is going on here...
Thats other direction:
19:02 hrw@home:rules.d$ LC_ALL=C apt-cache showsrc grep Package: grep Binary: grep Version: 2.6.3-3 Priority: required Section: utils Maintainer: Anibal Monsalve Salazar anibal@debian.org Build-Depends: autotools-dev, debhelper (>= 7), gettext, libpcre3-dev (>= 7.7), quilt
Regards,
On 10 Aug 02, Marcin Juszkiewicz wrote:
Dnia poniedziałek, 2 sierpnia 2010 o 18:54:11 Amit Kucheria napisał(a):
pcre3 does not show in 'apt-rdepends grep', so I am not sure what is going on here...
Thats other direction:
19:02 hrw@home:rules.d$ LC_ALL=C apt-cache showsrc grep Package: grep Binary: grep Version: 2.6.3-3 Priority: required Section: utils Maintainer: Anibal Monsalve Salazar anibal@debian.org Build-Depends: autotools-dev, debhelper (>= 7), gettext, libpcre3-dev (>= 7.7), quilt
Ofcourse!
So the original problem still remains then.
On Mon, Aug 02, 2010 at 07:54:11PM +0300, Amit Kucheria wrote:
On Mon, Aug 2, 2010 at 7:00 PM, Loïc Minier loic.minier@linaro.org wrote:
On Mon, Aug 02, 2010, Amit Kucheria wrote:
All my xdeb builds crash and burn with the following error: arm-linux-gnueabi-objdump: /lib/libm.so.6: File format not recognized dpkg-shlibdeps: error: arm-linux-gnueabi-objdump gave error exit status 1
I'm not quite sure; would you mind sharing the full log, and the command you used to build? There's probably a .build log in the dir.
It looks like you're missing the ARM cross libc, or that the build is not configured as a cross-build.
Errr, looks like something else is wrong here :)
$ xdeb --apt-source -a armel grep
<snip>
dpkg-source -x pcre3_8.02-1.dsc pcre3
<snip>
pcre3 does not show in 'apt-rdepends grep',
But it does correctly show up in 'apt-cache showsrc grep | grep Build-Depends'. (grepgrep? grepgrep!) And also in the Suggests: field of grep. grep dynamically loads libpcre when invoked with the '-P' option; it's not an ELF library dependency in order to not encumber the set of Essential: yes packages with extra libraries.
On Mon, Aug 02, 2010, Amit Kucheria wrote:
arm-linux-gnueabi-objdump: /lib/libm.so.6: File format not recognized dpkg-shlibdeps: error: arm-linux-gnueabi-objdump gave error exit status 1
This is a very recent new bug, which appeared between my testing and yours in the form of a new dpkg-dev! 1.15.8 and later introduce this issue, see Debian #591522.
There would be some ugly workarounds, but these aren't practical right now.
+++ Amit Arora [2010-07-30 17:14 +0530]:
Your mailer is removing 'references' headers so your replies don't thread (in mutt at least).
Wookey
-
Amit Arora -
Amit Kucheria -
Loïc Minier -
Marcin Juszkiewicz -
Steve Langasek -
Vishwanath Sripathy -
Wookey