Help compiling Valgrind

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Help compiling Valgrind

8,973 Views
timothybean
Contributor IV

Hello,

Can anyone help as to the error being provided by LTIB on i.MX6:

checking for gdb... /usr/bin/gdb

checking for a supported version of gcc... ok (arm-none-linux-gnueabi-gcc (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/10 09:20) 4.6.2 20110630 (prerelease))

checking build system type... i686-pc-linux-gnu

checking host system type... arm-unknown-linux

checking for a supported CPU... no (arm)

configure: error: Unsupported host architecture. Sorry

error: Bad exit status from /home/tim/imx/ltib/ltib/tmp/rpm-tmp.10702 (%build)

Thanks

Tim


Labels (2)
12 Replies

4,035 Views
timothybean
Contributor IV

I ran into the same problem. I WAS able to get it built, but had to get the latest version (at that time) of valgrind to get it to compile. I am not near it now but I can send version and my spec file if you would like. This was on LTIB-1.1.0 release.

I was able to get it to compile and run properly as far as I can tell.

Tim

0 Kudos
Reply

4,035 Views
ieio
Contributor IV

Hi Timothy,

I would be great to have version and spec file.

Many thanks,

i.

0 Kudos
Reply

4,035 Views
LeonardoSandova
Specialist I

In case you don’t mind the building system, try compiling a image with yocto, and choose 'fsl-image-gui-sdk' image, it is the most complete and has all dev tools, including valgrind.

Leo

4,035 Views
synthnassizer
Contributor III

Hi there,

I too am interested in building -sdk & -dev for an imx6q sabrelite .

So far I only new of the existence of fsl-image-test & fsl-image-gui.

Now you mention fsl-image-gui-sdk. How can I verify if I have this recipy, because I am running:

find . -type d -name fsl-image-gui-sdk

but I get no results back.

Is this image equivalent to the images I mentioned before with the addition of

EXTRA_IMAGE_FEATURES = "dbg-pkgs dev-pkgs tools-debug tools-profile tools-sdk debug-tweaks" in build/conf/local.conf ?

0 Kudos
Reply

4,035 Views
LeonardoSandova
Specialist I

It is on this path:

    meta-fsl-demos/recipes-fsl/images/fsl-image-gui-sdk.bb

And it contains fsl-image-gui and extra image features as seen below:

$ cat meta-fsl-demos/recipes-fsl/images/fsl-image-gui-sdk.bb

include recipes-fsl/images/fsl-image-gui.bb

IMAGE_FEATURES += " \

    dev-pkgs \

    tools-sdk \

"

EXTRA_IMAGE_FEATURES += " \

    tools-debug \

    tools-profile \

    tools-testapps \

    debug-tweaks \

"

export IMAGE_BASENAME = "fsl-image-gui-sdk"


0 Kudos
Reply

4,035 Views
Tarek
Senior Contributor I

I had to modify the configure script by replacing "armv7*" with "arm*".


T

0 Kudos
Reply

4,035 Views
jimmychan
NXP TechSupport
NXP TechSupport

In the LTIB, the version of Valgrind is 3.3.1. The problem may due to the Valgrind version is too old. please try the latest version of Valgrind  (download from http://valgrind.org/)

Once you downloaded the latest source code from Valgrind, please save the source code package file in /opt/freescale/pkgs/.

Then modify the ltib/dist/lfs-5.1/valgrind/valgrind.spec.

Change the version number and comment out the patches for 3.3.1.

Then use the following ltib commands to build the Valgrind again.

./ltib -p valgrind -m prep            (extract the source code to rpm/BUILD/)

./ltib -p valgrind -m scbuild        (build the source code)

./ltib -p valgrind -m scdeploy     (install to rootfs)


0 Kudos
Reply

4,035 Views
Tarek
Senior Contributor I

Yes I know that spec files is old. That's why I downloaded V3.8.1.

Same problem .....!

0 Kudos
Reply

4,035 Views
jimmychan
NXP TechSupport
NXP TechSupport

I search around in google. I found someone can build it.

http://blog.galemin.com/2010/10/how-to-build-valgrind-3-6-0-for-beagleboard-xm-on-ubuntu/

the name of arm used is "host=armv7-none-linux-gnueabi". seems it work, the configure can pass. Please try it.

0 Kudos
Reply

4,035 Views
SantiagoVillafu
Contributor II

Hi jimmychan,
I followed the instructions in the link you provided. I added a case with "arm*" in the configure file in "/LTIB/rpm/BUILD/valgrind-3.12.0/configure". I left "armv7*" in place.

arm*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: ok (${host_cpu})" >&5
$as_echo "ok (${host_cpu})" >&6; }
ARCH_MAX="arm"
;;

The compilation succeeded. I still have to test it in my iMX25. Thanks.

Maximum build arch: arm
Primary build arch: arm
Secondary build arch:
Build OS: linux
Primary build target: ARM_LINUX
Secondary build target:
Platform variant: vanilla
Primary -DVGPV string: -DVGPV_arm_linux_vanilla=1
Default supp files: exp-sgcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp

+ exit 0
Build time for valgrind: 18 seconds

EDIT: The binary does not work. When it's run it says: "Illegal instruction". :smileyconfused:

EDIT2: It looks like I cannot run valgrind on my iMX25 as it has no support for ARMv7 instructions:
embedded linux - Valgrind cross compilation for ARMv5tel - Stack Overflow 

:smileycry:

0 Kudos
Reply

4,035 Views
jimmychan
NXP TechSupport
NXP TechSupport

would you tell me which BSP are you using? which board are you using? and how to reproduce the issue? Thanks.


0 Kudos
Reply

4,035 Views
Tarek
Senior Contributor I

BSP: Linux 4.0.0

Board: Saberlite i.MXQ6

To reproduce the problem:

./ltib -p valgrind

Valgrind supports Arm starting from version 3.x why is it not building on ltib?

0 Kudos
Reply