Cross-Compilation of ROOT for ARM machine

Cross-Compilation of ROOT for ARM machine

[Brian Kelly]

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

Hello OpemEmbedded Community:

I am trying to compile the Root library (ver. 5.34.09) for an arm machine
(i.e. a gumstix verdex XL6P running the Angstrom linux distribution (a
computer-on-module)). I attempted native compilation but I kept getting an
internal error in the compiler program, which led to suspect that there was
not enough memory for the library to compile (this is most likely the case
since the library compiled fine on a debian arm emulation using qemu).

Now I am attempting to the bitbake software. I followed the instructions on
the website http://wiki.gumstix.org/index.php?title=Verdex_Git_Repository to
create a working bitbake environment and verdex image was created
successfully.


Now I am trying to create a recipe that will allow me to run Root.
Supposedly the libraries have been built successfully but the installation
on the gumstix fails (see attachment).

I have attached my work so far (my recipe, the terminal output from the
computer I am running bitbake on and the terminal output from my gumstix)
and, since I am quite inexperienced with bitbake, I would greatly appreciate
any constructive feedback that will help me get the Root library working on
the gumstix.

Thank you very much in for any help that you may provide.

Regards,
V. Satire Cat

[-- Attachment #2: root_5.34.9.bb.txt --]
[-- Type: text/plain, Size: 174 bytes --]

PR = "r0"
 
SRC_URI = "ftp://root.cern.ch/root/root_v5.34.09.source.tar.gz"

do_install(){
        install -m 0755 -d ${D}${bindir} ${D}${docdir}/root
 }
 
inherit autotools

[-- Attachment #3: gumstix_output.txt --]
[-- Type: text/plain, Size: 1265 bytes --]

[root@gumstix-verdex ~]
>opkg install root-dev_5.34.9-r0_armv5te.ipk
Installing root-dev (5.34.9-r0) to root...
Configuring debianutils.
update-alternatives: Linking //usr/sbin/add-shell to add-shell.debianutils
update-alternatives: Linking //usr/sbin/installkernel to installkernel.debianutils
update-alternatives: Linking //usr/sbin/mkboot to mkboot.debianutils
update-alternatives: Linking //usr/sbin/remove-shell to remove-shell.debianutils
update-alternatives: Linking //usr/bin/savelog to savelog.debianutils
update-alternatives: Linking //usr/bin/sensible-browser to sensible-browser.debianutils
update-alternatives: Linking //usr/bin/sensible-editor to sensible-editor.debianutils
update-alternatives: Linking //usr/bin/sensible-pager to sensible-pager.debianutils
update-alternatives: Linking //usr/bin/which to which.debianutils
update-alternatives: Linking //bin/run-parts to run-parts.debianutils
update-alternatives: Error: cannot register alternative tempfile to /bin/tempfile since it is already registered to /usr/bin/tempfile
Configuring root-dev.
Collected errors:
 * pkg_run_script: postinst script returned status 1.
 * opkg_configure: debianutils.postinst returned 1.
[root@gumstix-verdex ~]
>root
-bash: /bin/root: cannot execute binary file


[-- Attachment #4: bitbake_output.txt --]
[-- Type: text/plain, Size: 2997 bytes --]

user@computer:~/verdex-oe/org.openembedded.dev/recipes/root_5.34.9$ bitbake -b root_5.34.9.bb
NOTE: package root-5.34.9: started
NOTE: package root-5.34.9-r0: task do_fetch: started
NOTE: root-5.34.9: ftp://root.cern.ch/root/root_v5.34.09.source.tar.gz has no entry in conf/checksums.ini, not checking URI
NOTE: package root-5.34.9-r0: task do_fetch: completed
NOTE: package root-5.34.9-r0: task do_unpack: started
NOTE: Unpacking /usr/share/sources/root_v5.34.09.source.tar.gz to /home/user/gumstix/gumstix-oe/tmp/work/armv5te-angstrom-linux-gnueabi/root-5.34.9-r0/
NOTE: package root-5.34.9-r0: task do_unpack: completed
NOTE: package root-5.34.9-r0: task do_patch: started
NOTE: package root-5.34.9-r0: task do_patch: completed
NOTE: package root-5.34.9-r0: task do_configure: started
NOTE: package root-5.34.9-r0: task do_configure: completed
NOTE: package root-5.34.9-r0: task do_qa_configure: started
NOTE: Checking sanity of the config.log file
NOTE: package root-5.34.9-r0: task do_qa_configure: completed
NOTE: package root-5.34.9-r0: task do_compile: started
NOTE: package root-5.34.9-r0: task do_compile: completed
NOTE: package root-5.34.9-r0: task do_install: started
NOTE: package root-5.34.9-r0: task do_install: completed
NOTE: package root-5.34.9-r0: task do_package: started
NOTE: DO PACKAGE QA
NOTE: Checking Package: root-dbg
NOTE: Checking Package: root
NOTE: Checking Package: root-doc
NOTE: Checking Package: root-dev
NOTE: Checking Package: root-locale
NOTE: DONE with PACKAGE QA
NOTE: package root-5.34.9-r0: task do_package: completed
NOTE: package root-5.34.9-r0: task do_package_write_ipk: started
Packaged contents of root-dbg into /home/user/gumstix/gumstix-oe/tmp/deploy/glibc/ipk/armv5te/root-dbg_5.34.9-r0_armv5te.ipk
NOTE: Not creating empty archive for root-5.34.9-r0
NOTE: Not creating empty archive for root-doc-5.34.9-r0
Packaged contents of root-dev into /home/user/gumstix/gumstix-oe/tmp/deploy/glibc/ipk/armv5te/root-dev_5.34.9-r0_armv5te.ipk
NOTE: Not creating empty archive for root-locale-5.34.9-r0
NOTE: package root-5.34.9-r0: task do_package_write_ipk: completed
NOTE: package root-5.34.9-r0: task do_package_write: started
NOTE: package root-5.34.9-r0: task do_package_write: completed
NOTE: package root-5.34.9-r0: task do_populate_staging: started
NOTE: package root-5.34.9-r0: task do_populate_staging: completed
NOTE: package root-5.34.9-r0: task do_qa_staging: started
NOTE: QA checking staging
ERROR: QA issue: libmudflapth.la failed sanity test (reference to workdir or installed)
ERROR: QA issue: libstdc++.la failed sanity test (reference to workdir or installed)
ERROR: QA issue: libmudflap.la failed sanity test (reference to workdir or installed)
ERROR: QA issue: libsupc++.la failed sanity test (reference to workdir or installed)
NOTE: package root-5.34.9-r0: task do_qa_staging: completed
NOTE: package root-5.34.9-r0: task do_build: started
NOTE: package root-5.34.9-r0: task do_build: completed
NOTE: package root-5.34.9: completed

Re: Cross-Compilation of ROOT for ARM machine

[Nicolas Dechesne]

On Tue, Jul 16, 2013 at 7:37 PM, Brian Kelly <bak2132@columbia.edu> wrote:

>
> I am trying to compile the Root library (ver. 5.34.09) for an arm machine
> (i.e. a gumstix verdex XL6P running the Angstrom linux distribution (a
> computer-on-module)). I attempted native compilation but I kept getting an
> internal error in the compiler program, which led to suspect that there was
> not enough memory for the library to compile (this is most likely the case
> since the library compiled fine on a debian arm emulation using qemu).
>
> Now I am attempting to the bitbake software. I followed the instructions on
> the website http://wiki.gumstix.org/index.php?title=Verdex_Git_Repositoryto
> create a working bitbake environment and verdex image was created
> successfully.
>
>
> Now I am trying to create a recipe that will allow me to run Root.
> Supposedly the libraries have been built successfully but the installation
> on the gumstix fails (see attachment).
>
> I have attached my work so far (my recipe, the terminal output from the
> computer I am running bitbake on and the terminal output from my gumstix)
> and, since I am quite inexperienced with bitbake, I would greatly
> appreciate
> any constructive feedback that will help me get the Root library working on
> the gumstix.
>
> Thank you very much in for any help that you may provide.
>

hi. i am not sure exactly what you are trying to do here. but you seem to
be using quite old instructions that relate to 'OE classic'. The wiki you
mentioned hasn't got any update from more than 2 years.

many changes have happened in OE, i suggest you start with
http://openembedded.org/wiki/OpenEmbedded-Core

you recipe as it is written wouldn't work with the OE-core, and guidelines
to migrate recipes can be found here:
http://openembedded.org/wiki/Migrating_metadata_to_OE-Core

i am not familiar with gumtix, but you might check with that community if
they release an OE  SDK you could use for cross compilation. or you can at
least get more up to date information about how to add your recipe in their
builds.