On Aug 12, 2004, at 6:52 AM, Jeff Squyres wrote:
> On Aug 11, 2004, at 10:39 AM, Jack Howarth wrote:
>
>> Is there any reason why this mixed set of
>> shared and static libs are being produced by a simple ./configure
>> on lam 7.0.6?
>
> Yes, there actually is a deep, dark reason for this.
>
> We do some funny linker tricks to build the lamd; on OS X we *have* to
> build static libraries so that dynlib will resolve things properly.
> It's a long gruesome story, and we're not proud of it. ;-)
>
> In fact, if you try to build --enable-shared --disable-static, you'll
> find that you'll get an error message from configure and it will
> abort.
>
>> I have resolved it locally by appending --enable-shared to
>> the ./configure options. When the build is done that way the
>> resulting libraries produced include both the shared and static
>> versions. Such a build allows a shared lib version of gromacs-mpi
>> to link properly. Thanks in advance for any information on this.
>
>
Is there a way to get both shared and static libraries for OS X? I
really had to use a hammer to get the static libraries to play nice
with dynamically loaded code and it would be nice to have both around.
Thanks
Marc
|
