From: SourceForge.net <no...@so...> - 2008-11-04 22:06:46
|
Bugs item #1777301, was opened at 2007-08-19 13:26 Message generated for change (Settings changed) made by hobbs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1777301&group_id=10894 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 85. tclconfig Group: None >Status: Pending >Resolution: Works For Me Priority: 5 Private: No Submitted By: Rolf Ade (pointsman) Assigned to: Jeffrey Hobbs (hobbs) Summary: TEA: --exec-prefix not set from --prefix Initial Comment: A typical TEA 3.6 configure --help claims, that the default of --exec-prefix is set from prefix. Or at least, that is, how I understand it (reformated Installation directories: --prefix=PREFIX install architecture-independent files in PREFIX [/usr/local] --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX [PREFIX] But, if --prefix=/some/path is given to configure, the generated Makefile has: ... prefix = /some/path exec_prefix = /usr/local ... It seems, that exec_prefix is always set to the prefix default; there's code in TEA_INIT, which seems to do this. Note, that there is no real problem. Using both --prefix and --exec-prefix works. Just make the software do, what the doc (--help) say, or make the doc say, what the software really does. ---------------------------------------------------------------------- Comment By: Jeffrey Hobbs (hobbs) Date: 2008-11-04 14:06 Message: Actually Tcl's TEA_PREFIX does set exec_prefix to prefix, but it may be that autoconf (which handles this at a meta level) does it's own magic. A patch for what you intend against TEA_PREFIX would be good. Otherwise it is working as expected. ---------------------------------------------------------------------- Comment By: Rolf Ade (pointsman) Date: 2007-09-08 17:29 Message: Logged In: YES user_id=13222 Originator: YES No, --prefix and --exec_prefix are not superfluous at all for a Tcl extension. I love it, that I have the freedom, to compile my extenstion against a certain tcl installation (given by --with-tcl) and to install the result in a place of my choice, other than $(pkglibdir). Yes, I handle the auto_path manipulation, to get the extension version, I want, don't care about that. That is currently possible, and that's fine. In case of an extension with binary code, the user just has to provide both, --prefix and --exec-prefix. Although the help suggests, that the --exec-prefix default is set from the --prefix value. With isn't true. Nitpik. ---------------------------------------------------------------------- Comment By: Joe English (jenglish) Date: 2007-09-06 20:51 Message: Logged In: YES user_id=68433 Originator: NO Probably can't change the help text; you get that for free from autoconf whether you want it or not. However, for Tcl extensions, --prefix, --exec_prefix, and all of the subsidiary install directories are superfluous: the only installation directory TEA uses is $(pkglibdir). $(pkglibdir) is normally specified as a subdirectory of $(libdir) in Makefile.in; $(libdir) in turn defaults to ${exec_prefix}/lib; and ${exec_prefix} is set to ${TCL_EXEC_PREFIX} by the TEA_PREFIX autoconf macro. (The value of TCL_EXEC_PREFIX is found in tclConfig.sh; it's set to the value of @exec_prefix@ used when configuring Tcl.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1777301&group_id=10894 |