Bug 515155 - Avoid memcpy@GLIBC_2.14 for old Linux compatibility

GCC by default optimizes memmove() calls to use __builtin_memmove(),
which in turn uses memcpy() from the system GLIBC if source and target
regions are known to not overlap. When compiling on a modern Linux
host, this leads to pulling memcpy@GLIBC_2.14, which is not available
on older Linux hosts.

In order to be compatible with RHEL6/Centos6 level systems, we avoid
the memcpy@GLIBC_2.14 symbol by -fno-builtin-memmove when compiling.

This is only done for gtk2; we do not care about gtk3, since systems
that have gtk3 are supposed to also have memcpy@GLIBC_2.14.

Change-Id: I50fec4cbb7d662f27a28693543b2f2024a8ea375
Signed-off-by: Martin Oberhuber <martin.oberhuber@windriver.com>
1 file changed
tree: 15a6b4249f3e41861ec2e93bdb1950fb9c6d31bf
  1. bundles/
  2. examples/
  3. features/
  4. local-build/
  5. tests/
  6. .gitignore
  7. pom.xml
  8. README.md
README.md

Contributing to SWT

Thanks for your interest in this project.

Developer resources:

See the following description for how to contribute a feature or a bug fix to SWT.

Information regarding source code management, builds, coding standards, and more and be found under the following link.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!