Skip to content

generated angstrom-eglibc-x86_64-cortexa8hf-vfp-neon-v2013.06-toolchain.sh doesn't install dependancies. #24

Open

Description

@ilovetogetspamed

$ arm-angstrom-linux-gnueabi-gcc --version
arm-angstrom-linux-gnueabi-gcc: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument

I used MACHINE=beaglebone ./oebb.sh bitbake meta-toolchain to build the tool chain and use the generated sh script from the SDK to install it.
The generated shell script was named "angstrom-eglibc-x86_64-cortexa8hf-vfp-neon-v2013.06-toolchain.sh"

My development machine is x86_64 Ubuntu 12.04.2
and I did "$ source /usr/local/oecore-x86_64/environment-setup-cortexa8hf-vfp-neon-angstrom-linux-gnueabi" prior to trying the arm-angstrom-linux-gnueabi-gcc --version
Any insights to what I'm doing wrong would be greatly appreciated. Thanks

Activity

  1. Lusus commented on Nov 18, 2013

    @Lusus

    A workaround I have found for this issue, is to delete /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/lib/libc.so.6, which is a symlink to libc-2.17.so. Then Ubuntu uses its own libc (version 2.15).

    I suspect eglibc-2.17 is the problem. The equivalent toolchain generated by the danny release, supplied libc-2.16 works fine on the same machine.

  2. downwith commented on Jan 13, 2014

    @downwith

    I see the same issue on 64-bit Debian 7.3.0. Why don't the normal image builds (systemd-image, etc) have the same problem when executing the cross compiler? Don't those builds use the same eglibc-2.17 version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions