Print

Print


Editing the config files should always be a last resort! They're automatically generated by the distributor of the code (who tends to know what they're on about).

Wayne mentioned yast - that's the Suse update and install program. I recommend digging that out and getting it to install and configure Tcl/Tk for you - most versions 8.3 / 8.4 should work. Look out for the -devel packages as you'll need them for the compilation of the c code in the package.

Dan

On 18 Aug 2006, at 15:29, Jonathan Rapley wrote:

Hi,

The surrounding lines say.

# The following target is configured by autoconf to generate either
# a shared library or non-shared library for Tcl.
${TCL_LIB_FILE}: ${OBJS} ${STUB_LIB_FILE}
rm -f ${TCL_LIB_FILE}
${STLIB_LD} $@ ${OBJS}
if test "x" = "xtclLoadAout.o"; then \
$(RANLIB) ${TCL_LIB_FILE}; \
fi

${STUB_LIB_FILE}: ${STUB_LIB_OBJS}
rm -f ${STUB_LIB_FILE}
${STLIB_LD} $@ ${STUB_LIB_OBJS}
$(RANLIB) ${STUB_LIB_FILE}

Is there any way to get around the issue of editing the ./config?

Thanks

Jon

Daniel O'Donovan CCPN PhD Student
Dept. of Biochemistry
University of Cambridge
+44 1223 766 018