opensubscriber
   Find in this group all groups
 
Unknown more information…

f : fink-users@lists.sourceforge.net 19 September 2009 • 5:41AM -0400

Re: [Fink-users] Problem building tclx package
by Kurt Schwehr

REPLY TO AUTHOR
 
REPLY TO GROUP




Hi John,

I just tried rebuilding tclx9 on 10.5 and it works for me.  Perhaps there is something on 10.6?  You didn't say which verion of MacOSX you are running.


I am short on time till Nov.  Perhaps someone on fink-users or the fink IRC channel can help.

Sorry,
-kurt




----- Original Message ----
From: John Peterson <jwpeterson@gmai...>
To: fink-users@list...
Cc: goatbar@user...
Sent: Friday, September 18, 2009 5:23:14 PM
Subject: Problem building tclx package

Hi,

I think something may be wrong with the tclx package.  I get the
following error:

fink install tclx9
...
Installing ./doc/TclX.n
cp .libs/libtclx.8.0.4.dylib
/sw/src/fink.build/root-tclx9-8.4.0-2/sw/lib/libtclx.8.4.0.dylib
cp: .libs/libtclx.8.0.4.dylib: No such file or directory
### execution of cp failed, exit code 1
Removing runtime build-lock...
Removing build-lock package...
/sw/bin/dpkg-lockwait -r fink-buildlock-tclx9-8.4.0-2
(Reading database ... 153184 files and directories currently installed.)
Removing fink-buildlock-tclx9-8.4.0-2 ...
Failed: phase installing: tclx9-8.4.0-2 failed


Thanks for any advice you can provide!

--
John



      

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Fink-users mailing list
Fink-users@list...
https://lists.sourceforge.net/lists/listinfo/fink-users

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.