This is the mail archive of the
mailing list for the binutils project.
Re: How can I link the binutils using the static 'libc.a' instead of the dynamic 'libc.so'?
- From: Nick Clifton <nickc at redhat dot com>
- To: "Martin J. O'Riordan" <martin dot oriordan at movidius dot com>, binutils at sourceware dot org
- Date: Tue, 2 May 2017 16:51:37 +0100
- Subject: Re: How can I link the binutils using the static 'libc.a' instead of the dynamic 'libc.so'?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=nickc at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com BC3719D50A
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com BC3719D50A
- References: <firstname.lastname@example.org>
> How can I instruct 'configure' to do this? Is it even possible?
No! I was surprised to find this out, but it seems that the configure
and build system really does not want you to link with a static C library.
You can do it by hand of course, but that does not make for a reproducible build.
You can edit the makefiles too, but again this is not reliable in the long term.
Sorry - it looks like there is no easy solution to this problem.