On Tue, 13 Jul 2004, Alasdair Allan wrote:
> > > This has to be a "just mac" problem though? Or nobody else would have
> > > been able to buidl CCDPACK (as itcl is a dependancy for CCDPACK)...
> >
> > Ah yes, of course. The shared-library/libtool support in there
> > probably predates OSX. And it's an old-style configure.in, isn't it,
> > which autoconf 2.59 won't grok. That possibly means either hacking it
> > so newer autoconf can cope with it, or remaking it with an old
> > autoconf. Oh dear.
> >
> > I'd offer to do it myself, but I'm only on about Thursday of my
> > post-CVS-week tasks (blasted 'make install').
>
> Right, okay. I'd not have a clue where to start mucking with the
> configure.in (or actually how to rebuild it). Which leaves updating
> itcl as my only other option.
No, don't do that.
Itcl appears to get the relevant definitions from tclConfig.sh, which it
should be finding in thirdparty/tclsys/tcl/unix/tclConfig.sh (check the
results of itcl's ./configure scripts to ensure that this is the case).
This script is created from thirdparty/tclsys/tcl/unix/tclConfig.sh.in.
The work for defining SHLIB_LD is done in thirdparty/tclsys/tcl/unix/tcl.m4
in the SC_CONFIG_CFLAGS definition (near lines 500-1000).
What I think you have to do is:
1. Work out what the value of $system is for OS X (`uname -s`-`uname -r`)
2. Add a suitable stanza for it in the case statement that starts at
tcl.m4 line 566
3. Re-run autoconf v2.13 (you'll have to acquire this up from somewhere
unless you happen to have it already installed) in tclsys/tcl/unix to
generate configure from configure.in
4. Re-run ./configure (and check that 'grep TCL_SHLIB_LD tclConfig.sh'
gives you something sensible)
5. Rebuild and install tclsys/tcl (possibly from scratch, if it looks
to be holding on to state somewhere obscure).
Then you can try rebuilding itcl. If this has worked, then remember to
check in the modified tclsys/tcl/unix/configure script as well as tcl.m4.
I appreciate that this setting configure variables by checking for
a system type by name is not a very autotools way to do things;
(a) blame Tcl, and (b) feel free to rewrite the configure scripts
using libtool (or whatever) should you feel inclined.
You can probably get some clues for the Mac-specific changes required
by looking at a tcl.m4 file from a more recent release of Tcl.
There may be other Mac-specific things missing from the existing tcl.m4 -
you might get away with dropping in a recent tcl.m4 wholesale,
but I'd give it a careful look before doing something that drastic.
I'd give it a go myself, but obviously I've got no way to test if it's
worked.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|