On Sep 29, 2008, at 8:27 AM, Benoit St-Pierre wrote:

> To be sure, I modified this line :
>
> TCL_VERSION = 8.5
>
> And hard coded my PATH into /etc/profile :
>
> Macintosh:~ bstp$ echo $PATH
> /bin:/sbin:/usr/bin:/usr/sbin:/Library/Frameworks/Tcl.framework/ 
> Versions/8.5:Library/Frameworks/Tk.framework/Versions/8.5:/usr/local/ 
> bin:/usr/texbin
>
This is almost certainly harmless but it is not correct.  There is no  
need to add these directories to your path and even if there was, this  
is not the place to do it.  For most single user purposes, /etc/ 
profile need not be modified.  If you want to add directories to your  
path, do it in your .bashrc or .bash_profile

It was not clear from your previous emails that you were trying to  
build with tcl8.5.  This changes everything.  This is precisely the  
kind of dependency management nightmare that is going to crop up in  
moving to 8.5.   Because most OSs with a preinstalled tcl are on 8.4,  
including OS X.  At the very least, the move to 8.5 should be  
accompanied by a reworked configuration mechanism.

All those undeclared symbols in your configure output are from the X11  
libraries.  This is not what you want if you are trying to build a  
Scid application bundle, and it is not clear to me why it wants those  
symbols.  It will be hard to help you unless you provide more details  
about your tcl8.5 installation.  Where did you get it?  How did you  
install it?  Where did it put its libraries, headers and executables?   
This is complicated by the fact that you can do two types of tcl/tk  
install on OS X; one that uses X11 and one that used native widgets.

In looking at the configure script, I see that it looks for headers  
and libraries in /usr/include and /usr/lib first.  This is probably  
not optimal as it means that files installed in local directories will  
always be shadowed by the system ones, which seems backwards to me.   
So, no matter where your new installation puts its headers and  
libraries, the configure script will not spit out a correct makefile.   
It's probably easiest to just edit the makefile that is produced.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to