This is the mail archive of the
mailing list for the binutils project.
Re: problems with statically linked zlib
- From: ÐÐÐÑÑ ÐÐÑÐÐ <pashev dot igor at gmail dot com>
- To: "Simonov, Vladimir" <Vladimir dot Simonov at acronis dot com>
- Cc: "binutils at sourceware dot org" <binutils at sourceware dot org>
- Date: Tue, 7 May 2013 20:28:59 +0400
- Subject: Re: problems with statically linked zlib
- References: <F0AD13EFC234B549BBA4FCA20755EB24BF7A0EBE at Rus-mbx-1 dot ru dot corp dot acronis dot com>
2013/5/7 Simonov, Vladimir <Vladimir.Simonov@acronis.com>:
> Hi all,
> Environment: host - x86_64-unknown-linux-gnu, target - x86_64-unknown-linux-gnu,
> gcc - 4.7.2, binutils-2.23.2.
> I'd like to build ld and gold with statically linked zlib. libz.a is built in
> advance and placed in some directory ($TOOLS_DIR/lib).
> The only way I see -
> export CPPFLAGS="-I$TOOLS_DIR/include"
> export LDFLAGS="-L$TOOLS_DIR/lib"
> and run configure and build. Without above either system zlib.so is used or gold
> sources can't find zlib.h.
> What is correct way to configure binutils to get zlib linked-in statically?
This is exaclty the way GNU autotools work.