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: "Martin O'Riordan" <martin dot oriordan at movidius dot com>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: binutils at sourceware dot org
- Date: Thu, 4 May 2017 08:12:12 +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
- References: <firstname.lastname@example.org> <email@example.com> <CAESLzoNHJu0v1mtVtGf+Fj+SJVZ=cVE4O4mbifP1Syh_S4M8bw@mail.gmail.com>
On 4 May 2017 at 08:06, Martin O'Riordan <firstname.lastname@example.org> wrote:
> Thanks Nick,
> Good to know that I wasn't stumped over something simple that I should've
> spotted. My goal was to statically link the whole tool-chain, but reckoned
> I'd better get Binutils figured out before I tackled Gcc. I won't make and
> hand-written changes, as you say, this is not reliable or future proof.
> All the best,
> On 2 May 2017 at 16:51, Nick Clifton <email@example.com> wrote:
>> Hi Martin,
>> > 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
>> You can edit the makefiles too, but again this is not reliable in the long
>> Sorry - it looks like there is no easy solution to this problem.