[GRADLE-3055] C native binaries are linked to C++ runtime. Created: 30/Mar/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


It seems that gcc is being used for compilation of object files and g++ for linking. This results in the C++ runtime library being linked in. You can verify this buy doing a build on Linux with gcc toolchain and run the ldd program on a compiled binary.

$ ldd build/install/mainExecutable/lib/main
linux-vdso.so.1 => (0x00007fff389c4000)
libstdc+.so.6 => /usr/lib/x86_64-linux-gnu/libstdc+.so.6 (0x00007fa938f53000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa938cd1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa938aba000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa938730000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa93926d000)

In the GCC universe, it is not normal to link the C++ runtime library (normally libstdc++) into a C program! The correct output would be more like this:

$ gcc -o main build/objectFiles/mainExecutable/mainC/hello_gradle.o
$ ldd main
linux-vdso.so.1 => (0x00007ffffe3ff000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f84af516000)
/lib64/ld-linux-x86-64.so.2 (0x00007f84af8b3000)

I've found this both in a [simple example C project]([1]https://github.com/Spidey01/HelloGrad...) and in more [complex C projects]([2]https://github.com/Spidey01/lua.gradle).

Note: This is all using Gradle 1.11 on Debian stable (amd64) and stock gcc (4.7.2).
[1] https://github.com/Spidey01/HelloGradle/tree/master/c
[2] https://github.com/Spidey01/lua.gradle

Comment by Gradle Forums [ 30/Mar/14 ]

Hello Terry,
thanks for this report. you're right, in gradle 1.11 g++ is used for linking c and cpp programms. You should be able to workaround this issue by verifying the linker used for the gcc toolchain:

model {

toolChains {


{ linker.executable = 'gcc' }




Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:38:40 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.