From: SourceForge.net <no...@so...> - 2004-02-20 23:38:55
|
Bugs item #895899, was opened at 2004-02-12 12:29 Message generated for change (Comment added) made by miketm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112997&aid=895899&group_id=12997 Category: 85. Unix Build Group: current: 8.4.5 Status: Open Resolution: None Priority: 5 Submitted By: Mikhail Terekhov (miketm) Assigned to: Reinhard Max (rmax) Summary: Search order for the tclConfig.sh Initial Comment: I'm having troubles when installing Tcl/Tk on Solaris into non-standard location. configure/build of the Tcl went fine but configure for the Tk fails whith "Use --with-tcl= option ...". The problem is that I have an old version installed in /usr/local. Last time I checked (8.3.*) Tk's configure used to check --prefix location first. It is not really a bug, but the old behaviour was much more convenient IMHO. ---------------------------------------------------------------------- >Comment By: Mikhail Terekhov (miketm) Date: 2004-02-20 18:30 Message: Logged In: YES user_id=596169 I've used only --prefix=... ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2004-02-20 18:19 Message: Logged In: YES user_id=80530 Are you in a configuration where ${prefix} and ${exec_prefix} have different values? ---------------------------------------------------------------------- Comment By: Mikhail Terekhov (miketm) Date: 2004-02-20 18:16 Message: Logged In: YES user_id=596169 Small correction: I've used ${prefix}/lib not ${exec_prefix}/lib. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2004-02-20 15:24 Message: Logged In: YES user_id=80530 sorry to belabor this, but I do not understand why Mikhail is having trouble. If using the value ${exec_prefix}/lib makes Mikhail happy, and if the default value of ${libdir} is ${exec_prefix}/lib , then why isn't Mikhail happy by default? ---------------------------------------------------------------------- Comment By: Reinhard Max (rmax) Date: 2004-02-19 03:06 Message: Logged In: YES user_id=124643 This whole search path is a cludge. I think it shouldn't do this wild guessing, that Tcl might be installed at /usr/local/lib, /usr/contrib/lib, or /usr/lib. Instead it should just look into ${libdir} which defaults to ${exec_prefix}/lib when no --libdir option is given to configure. So if Tk (or any other extension) is being configured with a different prefix or libdir than Tcl, would mean that one has to use --with-tcl to avoid undesired Tcl versions to be found by accident. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2004-02-18 17:30 Message: Logged In: YES user_id=80530 rmax, Mihhail is complaining about the effect of your 2002-06-25 change to unix/tcl.m4, forcing extensions to look under ${libdir} for tclConfig.sh instead of the former location ${exec_prefix}/lib Is there any reason not to add ${exec_prefix}/lib back to the search path? Does it matter whether it gets added before or after ${libdir} ? ---------------------------------------------------------------------- Comment By: Mikhail Terekhov (miketm) Date: 2004-02-18 17:18 Message: Logged In: YES user_id=596169 It works both ways for me ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2004-02-18 16:58 Message: Logged In: YES user_id=80530 I see. Did you need to change ${libdir} to ${prefix}/lib, or would it have good enough to add ${prefix}/lib to the search patch, perhaps after ${libdir} ? ---------------------------------------------------------------------- Comment By: Mikhail Terekhov (miketm) Date: 2004-02-18 14:45 Message: Logged In: YES user_id=596169 Changing ${libdir} to ${prefix}/lib on line 66 in the file unix/tcl.m4 (and autoconf after this) solved this problem. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2004-02-17 20:26 Message: Logged In: YES user_id=80530 I does look like Tk 8.4.5 is using the same search path as Tk 8.5a0. How does this bug report relate to Tk Bug 608698? Also, note that the error message from Tk's configure that includes "Use --with-tcl= option..." is an error indicating that the Tk you are trying to build is of a different version than the tclConfig.sh file that was found. That's a good error to be told about. It means Tk's configure found the wrong tclConfig.sh file. Can you tell us more about where the right tclConfig.sh file is that Tk's configure should find, where the wrong one is that it found instead, then we can look into why it's choosing the wrong one? ---------------------------------------------------------------------- Comment By: Donal K. Fellows (dkf) Date: 2004-02-17 18:04 Message: Logged In: YES user_id=79902 That's the CVS HEAD. 8.5a1 is supposed to be tagged sometime this month though, so you could wait for that if you prefer. ---------------------------------------------------------------------- Comment By: Mikhail Terekhov (miketm) Date: 2004-02-16 15:03 Message: Logged In: YES user_id=596169 Where to get Tcl 8.5a0? There is no such CVS tag or archive on SF. ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2004-02-16 14:34 Message: Logged In: YES user_id=80530 Is Tcl 8.5a0 any better? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112997&aid=895899&group_id=12997 |