# undefined reference to \`memcpy@GLIBC\_2.14'

**URL:** <https://forums.suse.com/t/undefined-reference-to-memcpy-glibc-2-14/25041>\
**Category:** SLES Configure-Administer\
**Created:** [January 27, 2014, 12:31pm UTC](https://forums.suse.com/t/undefined-reference-to-memcpy-glibc-2-14/25041 "2014-01-27T12:31:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GEKen](https://avatars.discourse-cdn.com/v4/letter/g/b5e925/32.png) [@GEKen](https://forums.suse.com/u/GEKen)\
**Post date:** [January 27, 2014, 12:31pm UTC](https://forums.suse.com/t/undefined-reference-to-memcpy-glibc-2-14/25041/1 "2014-01-27T12:31:38Z")

</div>

Hi all,

I am trying to build the driver below on SLES 11 SP1 x86-64 with patches “Linux.kernel.x86\_64.6230”.

[http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.1.12.tar.gz](http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.1.12.tar.gz)

When building I get:

make -B  
for n in BitMode EEPROM/erase EEPROM/read EEPROM/write EEPROM/user/read EEPROM/user/size EEPROM/user/write Events LargeRead MultiThread SetVIDPID Simple Timeouts ; do make -C $n || exit 1; done  
make[1]: Entering directory `me/ftdi/release/examples/BitMode' gcc main.c -o bitmode -Wall -Wextra -L. -lftd2xx -Wl,-rpath /usr/local/lib /usr/local/lib/libftd2xx.so: undefined reference to `memcpy@GLIBC\_2.14’  
collect2: ld returned 1 exit status  
make[1]: \*\*\* [bitmode] Error 1  
make[1]: Leaving directory `me/ftdi/release/examples/BitMode’  
make: \*\*\* [subdirs] Error 1

This is no doubt because the glibc on SLES is 2.11.1-0.17.4 i.e. too old.

Is there any way around this or will the driver manufacturer have to change something?

Many thanks!

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [January 27, 2014, 3:03pm UTC](https://forums.suse.com/t/undefined-reference-to-memcpy-glibc-2-14/25041/2 "2014-01-27T15:03:35Z")

</div>

Hi GEKen,

> Is there any way around this or will the driver manufacturer have to change something?

that’s the curse of binary driver distributions - have you seen the following information from their README ([http://www.ftdichip.com/Drivers/D2XX/Linux/ReadMe-linux.txt)?](http://www.ftdichip.com/Drivers/D2XX/Linux/ReadMe-linux.txt)

> [@](#):
>
> FTDI do not release the source code for libftd2xx. If you prefer to work with source code and are starting a project from scratch, consider using the open-source libFTDI.

In addition, you might want to ask the manufacturer to provide a binary of that lib precompiled for your SLES version.

Regards,  
Jens