Yes that was it, I had built it previously & forgot. Forcing it fixes it.
Thanks! Cheers -- Ian On 14 March 2015 at 18:00, Marcin Wojdyr <marcin.woj...@diamond.ac.uk> wrote: > Dear Ian, > > Hard to tell without more details. What options are passed to the > configure scripts in mmdb2 and libccp4? (you can find it in the output) > The options include either "--disable-shared --enable-static" or the > other way around. > > Maybe you built it before setting BUILD_STATIC, and then when you > tried to build it again you got message: > *** Skipping [module] (package and dependencies not updated) *** > In such case either remove the install directory or do: > > ./build --force libccp4 > > Cheers > Marcin > > On Sat, Mar 14, 2015 at 12:17:16PM +0000, Ian Tickle wrote: > > Hello All > > > > I want to build static libs (libccp4.a etc.), basically to avoid hassle > > when deploying executables of my own programs to other machines that are > > not on my LAN and don't have up-to-date compilers or system libraries. > > > > I downloaded the CCP4 sources & followed instructions in the README, > > basically AFAICS just 'setenv BUILD_STATIC 1' (tcsh) and './build libccp4 > > etc.' which claimed to be successful. But I can't find libccp4*.a > > anywhere. In fact 'find' says that the only .a files are in the > > cmake-3.0.2 directory and are called 'libtest*.a'. I found > > 'libccp4c.so.0.0.0' in builddir/libccp4/ccp4/.libs so it seems to be > > building the dynamic libs. I also tried 'setenv STATIC 1' but got the > same > > result. > > > > What am I doing wrong? > > > > Cheers > > > > -- Ian > > -- > This e-mail and any attachments may contain confidential, copyright and or > privileged material, and are for the use of the intended addressee only. If > you are not the intended addressee or an authorised recipient of the > addressee please notify us of receipt by returning the e-mail and do not > use, copy, retain, distribute or disclose the information in or attached to > the e-mail. > Any opinions expressed within this e-mail are those of the individual and > not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any > attachments are free from viruses and we cannot accept liability for any > damage which you may sustain as a result of software viruses which may be > transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in England > and Wales with its registered office at Diamond House, Harwell Science and > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom >
