Re: gsl on macos x

Re: gsl on macos x

[Brian Gough]

Jeff Whitaker writes:
 > That said, even dyld is able to handle some conflicts. Otherwise it
 > wouldn't be possible to link a program against libncurses, for
 > example. Since the libraries are (hopefully) loaded in a
 > deterministic order, this at least doesn't produce "heisenbugs". With
 > dynamic loading the checks have to be more strict as the load order
 > may differ from one program run to another. dyld also doesn't allow
 > duplicate symbols when generating a shared library that depends on
 > other shared libraries; this is again related to load order (I think).

The only thing I can suggest is, using the CVS version, to try
rearranging the order of SUBLIBS libraries in the top-level
Makefile.am

Currently they are in alphabetical order(!), so putting them in load
order might help.  For example, libgslblock should be after
libgslvector in load order.  You could try putting libgslblock after
libgslvector and see if that reduces the number of errors.

However, the log shows that the linker also complains about functions
like gsl_ran_bernoulli, which is not used anywhere else in the library
so this might not help because load order should not be an issue
there.  

gsl on macos x

[Jeff Whitaker]

Trying to build gsl on MacOS X - I get all the way to the end, then the
dynamlic linker (DYLD) complains about multiply defined symbols when
building libgsl.dylib.  I get about a 100 lines of messages like this:

ld: multiple definitions of symbol _gsl_block_alloc
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_alloc in
section (__TEXT,__text)
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_alloc in
section (__TEXT,__text)
ld: multiple definitions of symbol _gsl_block_calloc
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_calloc in
section (__TEXT,__text)
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_calloc in
section (__TEXT,__text)
ld: multiple definitions of symbol _gsl_block_char_alloc
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_char_alloc in
section (__TEXT,__text)
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_char_alloc in
section (__TEXT,__text)
ld: multiple definitions of symbol _gsl_block_char_calloc
block/.libs/libgslblock.al(init.lo) definition of _gsl_block_char_calloc
in section (__TEXT,__text)
...
ld: multiple definitions of symbol _gsl_vector_view_array_with_stride
vector/.libs/libgslvector.al(view.lo) definition of
_gsl_vector_view_array_with_stride in section (__TEXT,__text)
vector/.libs/libgslvector.al(view.lo) definition of
_gsl_vector_view_array_with_stride in section (__TEXT,__text)
/usr/bin/libtool: internal link edit command failed
make[2]: *** [libgsl.la] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2
### make failed, exit code 2


I know DYLD is very picky about multiple symbol definitions - unlike ld on
most unices.  Does anyone know if there is any solution to this problem?

-Jeff

-- 
Jeffrey S. Whitaker         Phone  : (303)497-6313
Meteorologist               FAX    : (303)497-6449
NOAA/OAR/CDC  R/CDC1        Email  : jsw@cdc.noaa.gov
325 Broadway                Web    : www.cdc.noaa.gov/~jsw
Boulder, CO, USA 80303-3328 Office : Skaggs Research Cntr 1D-124

Re: gsl on macos x

[Brian Gough]

Jeff Whitaker writes:
 > Trying to build gsl on MacOS X - I get all the way to the end, then the
 > dynamlic linker (DYLD) complains about multiply defined symbols when
 > building libgsl.dylib.  I get about a 100 lines of messages like this:
 > 
 > ld: multiple definitions of symbol _gsl_block_alloc
 > block/.libs/libgslblock.al(init.lo) definition of _gsl_block_alloc in
 > section (__TEXT,__text)
 >
 > I know DYLD is very picky about multiple symbol definitions - unlike ld on
 > most unices.  Does anyone know if there is any solution to this problem?

Thanks for reporting that.  I don't know what the problem is, but you
could try compiling with

  ./configure --disable-shared

to see if it only affects shared libraries.  Could you send me the
complete list of errors so I can see if there is anything different
about the functions with errors (or does it occur for every function?).

regards
Brian Gough

Re: GSL on MacOS X.

[Brian Gough]

ecarter@mindspring.com writes:
 >  I thought I'd document some success I've had with getting GSL
 > shared libraries built on MacOS X(10.1.4).
 >  1. Get fink(http://fink.sourceforge.net) 2, Install fink's
 > libtool14, automake,autoconf25.  3. Regenerate GSL's config tools
 > using ./autogen.sh in the top level directory.
 > 4. ./configure, make, so forth.
 >  Perhaps this hint could be added to the INSTALL notes.

Now added, thanks.

GSL on MacOS X.

[ecarter]

Greetings,

I thought I'd document some success I've had with getting GSL
shared libraries built on MacOS X(10.1.4).

1. Get fink(http://fink.sourceforge.net)
2, Install fink's libtool14, automake,autoconf25.
3. Regenerate GSL's config tools  using ./autogen.sh
   in the top level directory.
4. ./configure, make, so forth.

Perhaps this hint could be added to the INSTALL notes.

Gene Carter
NAMOT guy