Re: Statically linked libraries...
Hi,
> I am preparing a package for the mira software, and encounter the
> following lintian error:
>
> The package installs a statically linked binary or object file.
>
> I miss the backgound in C programing to know where to start to takcle
> this problem. Can sombebody give me a hint? I have uploaded the package
> on mentors (this is still a preliminary package).
./configure output says:
> ----------------------------------------------------------------------------
> Summary of MIRA configuration
> ----------------------------------------------------------------------------
> We are building on ............................... Linux
> Can MIRA be build on this system? ................ yes
> CPU supports 64 bit? ......... ................... yes
> Do we compile in 64 bit? ......................... yes
> Building completely static? ...................... yes
> Compiler ......................................... x86_64-linux-gnu-gcc
and looking at the build log it says:
> x86_64-linux-gnu-g++ -DPUBLICQUIET -DAJ_Linux64 -O2 -L../../../io/ -L../../../util/ -L../../../errorhandling/ -L../../../mira -L../../../examine/ -L../../../EdIt/ -L../../../caf/ -L../../../knn_abi373 -L../../../knn_alf -Wl,-z,defs -static -o tstReadPool tstReadPool.o -lerrorhandling -lmira -lmsupport -ldptools -lutil -lfio -lexpat
So yes, you are building binaries static (you are giving '-static'
option to g++ ), and it looks like ./configure has a switch to toggle
the option.
A properly created ./configure script usually has a usable --help option.
> ./configure --help
gives:
> --enable-static builds static binaries, default is yes
Looking at the source (configure.ac) the upstream have customized it
such that --enable-static is the default, and adds '-static' to the
linking process.
I don't quite understand why they want to do that as default, but
--disable-static should disable static-linking.
regards,
junichi
--
dancer@{debian.org,netfort.gr.jp} Debian Project
Reply to: