Re: 'memcpy@GLIBC_2.4' error while jogl compilation
Posted by Sven Gothel on Aug 07, 2015; 10:42pm
URL: https://forum.jogamp.org/memcpy-GLIBC-2-4-error-while-jogl-compilation-tp4035047p4035054.html
On 08/07/2015 02:12 PM, iNik [via jogamp] wrote:
> Hello!
>
> I am trying to build Gluegen and Jogl at my i.mx6 armv6hf platform, as Sven
> Gothel recommended at the end of this post
> <http://forum.jogamp.org/OneTriangleAWT-crashes-with-quot-glGetString-quot-message-td4035015.html>,
> but facing with 'memcpy@GLIBC_2.4' issue.
>
> I digged a forum and found a couple of treads with the same issue, like this
> <http://forum.jogamp.org/unsolved-memcpy-GLIBC-2-4-No-symbol-version-section-td4033903.html#a4033939> and
> this <http://forum.jogamp.org/JOGL-2-3-1-on-armv6hf-td4034766.html>, but there
> are no solution.
>
> There was a link to toolchain in one of those posts, but I couldn't figure out
> how to use it. I put "armhf-unknown-linux-gnueabi" directory to / and set
> TARGET_PLATFORM_LIBS=/armhf-unknown-linux-gnueabi/lib/gcc/armhf-unknown-linux-gnueabi,
> but got same "GLIBC2.4" error.You have to setup a custom toolchain for our builds as follows:
PATH=$TOOLCHAIN_SYMLINKS/toolchain/armsf-linux-gnueabi/bin:$PATH
export PATH
ls -la $TOOLCHAIN_SYMLINKS/toolchain/armsf-linux-gnueabi/bin
c++ -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-c++
cc -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-cc
g++ -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-g++
gcc -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-gcc
ld -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-ld
objdump -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-objdump
strip -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-strip
The toolchain above is available here, check for x-tools*:
<http://jogamp.org/files/toolchain/>
Above setup is documented in our jogamp-scripting repo,
which contains all startup/config files for our jenkins
build system and more:
- Above symlinks
<http://jogamp.org/git/?p=jogamp-scripting.git;a=tree;f=jenkins-server-slave-setup/nodes/sgothel-linux64-amd58xx-001_002.linuxARMv7l-030.androidARMv7l-040/toolchain/armhf-linux-gnueabi/bin;h=52bc4cdde35265283a76c8b8c314bd35fe35317e;hb=HEAD>
- The nodes startup etc:
<http://jogamp.org/git/?p=jogamp-scripting.git;a=tree;f=jenkins-server-slave-setup/nodes/sgothel-linux64-amd58xx-001_002.linuxARMv7l-030.androidARMv7l-040;hb=HEAD>
>
> So, the question is how to build jogl with my existing toolchain:
> gcc version 4.9.2 (GCC).
> GNU C Library (GNU libc) stable release version 2.21.
Yes we should accommodate newer toolchains.
Please file a new bug report - thank you.
- Add all info above into it, thx alot!
- It will be one of the next work items.
Until then .. you may try the above description
of using our toolchain.
>
> Thank you.
Thank you.
~Sven
URL: https://forum.jogamp.org/memcpy-GLIBC-2-4-error-while-jogl-compilation-tp4035047p4035054.html
On 08/07/2015 02:12 PM, iNik [via jogamp] wrote:
> Hello!
>
> I am trying to build Gluegen and Jogl at my i.mx6 armv6hf platform, as Sven
> Gothel recommended at the end of this post
> <http://forum.jogamp.org/OneTriangleAWT-crashes-with-quot-glGetString-quot-message-td4035015.html>,
> but facing with 'memcpy@GLIBC_2.4' issue.
>
> I digged a forum and found a couple of treads with the same issue, like this
> <http://forum.jogamp.org/unsolved-memcpy-GLIBC-2-4-No-symbol-version-section-td4033903.html#a4033939> and
> this <http://forum.jogamp.org/JOGL-2-3-1-on-armv6hf-td4034766.html>, but there
> are no solution.
>
> There was a link to toolchain in one of those posts, but I couldn't figure out
> how to use it. I put "armhf-unknown-linux-gnueabi" directory to / and set
> TARGET_PLATFORM_LIBS=/armhf-unknown-linux-gnueabi/lib/gcc/armhf-unknown-linux-gnueabi,
> but got same "GLIBC2.4" error.
PATH=$TOOLCHAIN_SYMLINKS/toolchain/armsf-linux-gnueabi/bin:$PATH
export PATH
ls -la $TOOLCHAIN_SYMLINKS/toolchain/armsf-linux-gnueabi/bin
c++ -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-c++
cc -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-cc
g++ -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-g++
gcc -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-gcc
ld -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-ld
objdump -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-objdump
strip -> /usr/local/x-tools/armhf-unknown-linux-gnueabi/bin/armhf-unknown-linux-gnueabi-strip
The toolchain above is available here, check for x-tools*:
<http://jogamp.org/files/toolchain/>
Above setup is documented in our jogamp-scripting repo,
which contains all startup/config files for our jenkins
build system and more:
- Above symlinks
<http://jogamp.org/git/?p=jogamp-scripting.git;a=tree;f=jenkins-server-slave-setup/nodes/sgothel-linux64-amd58xx-001_002.linuxARMv7l-030.androidARMv7l-040/toolchain/armhf-linux-gnueabi/bin;h=52bc4cdde35265283a76c8b8c314bd35fe35317e;hb=HEAD>
- The nodes startup etc:
<http://jogamp.org/git/?p=jogamp-scripting.git;a=tree;f=jenkins-server-slave-setup/nodes/sgothel-linux64-amd58xx-001_002.linuxARMv7l-030.androidARMv7l-040;hb=HEAD>
>
> So, the question is how to build jogl with my existing toolchain:
> gcc version 4.9.2 (GCC).
> GNU C Library (GNU libc) stable release version 2.21.
Yes we should accommodate newer toolchains.
Please file a new bug report - thank you.
- Add all info above into it, thx alot!
- It will be one of the next work items.
Until then .. you may try the above description
of using our toolchain.
>
> Thank you.
Thank you.
~Sven
signature.asc (828 bytes) | Free forum by Nabble | Edit this page |