[parsec-users] compiling statically linked vips binary

Kshitij Sudan kshitij at cs.utah.edu
Wed Apr 30 19:33:51 EDT 2008

Is there a way to pass -all-static flag to the linker using parsecmgmt
tool? I tried compiling vips on it's own without using parsecmgmt, but
I am unable to include the correct path for libs provided with parsec.

configure script dies reporting the following message:

checking pkg-config is at least version 0.9.0... yes
checking for REQUIRED... configure: error: Package requirements
(glib-2.0 >= 2.6 gmodule-2.0 >= 2.4 libxml-2.0 gobject-2.0) were not

No package 'glib-2.0' found
No package 'gmodule-2.0' found
No package 'gobject-2.0' found


On Wed, Apr 30, 2008 at 4:34 AM,  <jcupitt at gmail.com> wrote:
> 2008/4/30 Kshitij Sudan <kshitij at cs.utah.edu>:
> >  I am trying to compile vips for Linux, such that it's statically
>  >  linked. I edited gcc.bldconf in $PARSEC/config and also vips specific
>  >  gcc.bldconf file by adding  -static and -static-libgcc to CCFLAGS,
>  >  CXXFLAG, and LDFLAGS. Still at the end of compilation, it produces a
>  >  dynamically linked executable. I am building it using "parsecmgmt"
>  >  tool.
>  vips is linked with libtool which (strangely) has it's own
>  interpretation of these flags. libtool -static means link the object
>  against the static versions of any uninstalled libtool libraries, but
>  link dynamically otherwise. -static-all means link against the static
>  versions of all libraries, including libtool, native, installed and
>  uninstalled. At least that's my understanding.
>  Unfortunately, you can't pass -all-static to configure, because then
>  the compiler sees it (since configure is not using libtool) and
>  breaks. Instead you have to do:
>   ./configure
>   make LDFLAGS=-all-static
>  John
>  _______________________________________________
>  parsec-users mailing list
>  parsec-users at lists.cs.princeton.edu
>  https://lists.cs.princeton.edu/mailman/listinfo/parsec-users

More information about the parsec-users mailing list