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!
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 h...@home:rules.d$ LC_ALL=C apt-cache showsrc grep
>
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 worr
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
> d
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
cha
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 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 recogn
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 us
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 h...@home:rules.d$ LC_ALL=C apt-cache showsrc grep
Package: grep
Binary: grep
Version: 2.6.3-3
Priority: r
On Mon, Aug 2, 2010 at 7:00 PM, Loïc Minier 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 exi
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 t
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-buildpackag
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 e
On Mon, Aug 2, 2010 at 5:11 PM, 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?
> Thanks
> Vishwa
I just updated the wiki to add a step to mount the proc filesystem
___
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 wrote:
> On Fri, Jul 30, 2010, Amit Kucheria wrote:
> > > Will it make sense to have a "readme.ARM" or some other file in
>
+++ 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
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
___
linaro-dev mailing
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 require
On 10 Jul 30, Amit Arora wrote:
> On Fri, Jul 30, 2010 at 4:45 PM, Vishwanath Sripathy
> 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 conf
On Fri, Jul 30, 2010 at 4:45 PM, Vishwanath Sripathy
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
On Thu, Jul 29, 2010 at 7:56 PM, Marcin Juszkiewicz
wrote:
> Dnia czwartek, 29 lipca 2010 o 13:57:21 Amit Arora napisał(a):
>> I have tested this only on my desktop. I am yet to receive an ARM based
>> board, and hence couldn't test it there. So, any kind of testing and/or
>> feedback are most wel
On Thu, Jul 29, 2010 at 6:38 PM, Amit Kucheria wrote:
> On 10 Jul 29, Amit Arora wrote:
>>
>> Currently the PowerTOP tool is x86 centric and does not work on other
>> architectures, unless some changes are made.
>>
>> This patchset removes the hardcoded values for the P and C states. It does
>>
On Thu, Jul 29, 2010 at 5:42 PM, Amit Kucheria wrote:
> On 10 Jul 29, Amit Arora wrote:
>> Amit Arora (2):
>> Add OMAP3 support to PowerTOP
>> Remove hardcoded c and p states
>>
>> Makefile | 2 +-
>> cpufreqstats.c | 3 +-
>> display.c | 23 +-
>> gene
Dnia czwartek, 29 lipca 2010 o 13:57:21 Amit Arora napisał(a):
> I have tested this only on my desktop. I am yet to receive an ARM based
> board, and hence couldn't test it there. So, any kind of testing and/or
> feedback are most welcome! Thanks!
I fetched 9f4efd1c7cc0bc9a9078fa6b83a98763a7637e2f
Dnia czwartek, 29 lipca 2010 o 13:57:21 Amit Arora napisał(a):
> I have tested this only on my desktop. I am yet to receive an ARM based
> board, and hence couldn't test it there. So, any kind of testing and/or
> feedback are most welcome! Thanks!
I fetched 9f4efd1c7cc0bc9a9078fa6b83a98763a7637e2f
On 10 Jul 29, Amit Arora wrote:
>
> Currently the PowerTOP tool is x86 centric and does not work on other
> architectures, unless some changes are made.
>
> This patchset removes the hardcoded values for the P and C states. It does
> that in two steps
> 1) Implements the OMAP3 support in PowerT
On 10 Jul 29, Amit Arora wrote:
>
> Currently the PowerTOP tool is x86 centric and does not work on other
> architectures, unless some changes are made.
>
> This patchset removes the hardcoded values for the P and C states. It does
> that in two steps
> 1) Implements the OMAP3 support in PowerT
Currently the PowerTOP tool is x86 centric and does not work on other
architectures, unless some changes are made.
This patchset removes the hardcoded values for the P and C states. It does that
in two steps
1) Implements the OMAP3 support in PowerTOP.
2) Makes the code generic enough for all b
26 matches
Mail list logo