From: SourceForge.net <no...@so...> - 2007-10-01 16:39:35
|
Bugs item #1805763, was opened at 2007-10-01 11:07 Message generated for change (Comment added) made by gwlester You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1805763&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: 69. Other Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Make Install does not full work on OS X Initial Comment: When using the ActiveState distro and a prefix the make install does not install the package index and library in the correct spot. Please see attached console log. ---------------------------------------------------------------------- Comment By: Gerald W. Lester (gwlester) Date: 2007-10-01 11:39 Message: Logged In: YES user_id=121110 Originator: NO This is for TclOO -- sorry forgot to add it into the comments. (p.s. -- we need to add a TclOO category). ---------------------------------------------------------------------- Comment By: Andreas Kupries (andreas_kupries) Date: 2007-10-01 11:21 Message: Logged In: YES user_id=75003 Originator: NO This bug report is a bit unclear ... The ActiveState distribution does not have something to 'make install' ... Reading the attached log it seems you tried to self-compile ... dkf's oocore and pointed its configure to an installed ActiveTcl 8.5. Is that correct ? And it picks up incorrect paths from the tclConfig.sh ? ... Yes, it seems that TCL_(EXEC_)PREFIX contain paths to my buildsystem. This should be reported to ActiveState and not here. Because the problem is in ActiveState's OS X tclConfig.sh, not oocore's 'make install'. ... Having checked a bit further it seems that 'oocore' requires the Tcl internal headers (configure.in). That is actually something ActiveTcl is not supporting at all. Because using the internal headers also implies having access to the sources and buildsystem of Tcl, and that is something which is not provided by ActiveTcl. IOW, packages requiring internal headers of Tcl cannot be build against ActiveTcl. Still, the bogus paths in TCL_(EXEC_)PREFIX should be fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1805763&group_id=10894 |