Jerome, I told you, it's the Framework/Tk file...
look at december 2004 log with me.. here's what I found :
ln -s /System/Library/Frameworks/Tk.framework/Versions/8.4/Tk
libtk8.4.dylib
the two files are symlinks to the Frameworks, which means these two files :
/Library/Frameworks/Tcl.framework
Here this is is a symlink for both..Le 6 mai 2006 à 02:46, Tom Hennigan a écrit :Sorry i only tested libtcl8.4.dylib (which is a file not a symlink), and that is a universal dylib, but it appears that libtk8.4.dylib is a symlinkOn 5 May 2006, at 22:21, Jérôme Gagnon-Voyer wrote:How could a siml
I tried to compile anyway with the simlinks instead of the real .dylib (that I din't find yet)/usr/bin/libtool: -static not specified, -s invalid/usr/bin/libtool: file: -ltcl8.4 is not an object file (not allowed in a library)/usr/bin/libtool: file: -ltk8.4 is not an object file (not allowed in a l
Sorry i only tested libtcl8.4.dylib (which is a file not a symlink), and that is a universal dylib, but it appears that libtk8.4.dylib is a symlinkOn 5 May 2006, at 22:21, Jérôme Gagnon-Voyer wrote:How could a simlink be a Universal Version? I really miss something here.Le 5 mai 2006 à 12:29, T
How could a simlink be a Universal Version? I really miss something here.Le 5 mai 2006 à 12:29, Tom Hennigan a écrit :Oh and they're universal versions as well from this location!! :D--I have it on mine here:/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtcl8.4.dylib/Developer/SDKs/MacOSX10.4u.sdk/usr/
Oh and they're universal versions as well from this location!! :D--I have it on mine here:/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtcl8.4.dylib/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtk8.4.dylibOn 5 May 2006, at 07:42, Jérôme Gagnon-Voyer wrote:Ok I found the problemOn my amsn package that wor
It could be a copy, not a symlink, so if you do a diff, it should tell you
if there is a difference, you do the diff between the libtcl8.4.dylib and
the 'Tcl' file in Framework/
On Fri, 05 May 2006 14:08:55 -0400, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
Not sure to understand, I d
On Fri, 05 May 2006 10:54:51 -0400, Vivia Nikolaidou
<[EMAIL PROTECTED]> wrote:
On Fri, 5 May 2006, Youness Alaoui wrote:
I had it run every day, so it's always up to date, but still it won't
find some files (normal filenames, no special char, simple a to z
ascii), I do a locate on something
Not sure to understand, I diff with what other file?
It's a real file, not a symbolic link. So it must come from
somewhere, but where?
Le 5 mai 2006 à 08:54, Youness Alaoui a écrit :
If I remember correctly it is a symbolic link (or a copy) of the
file Tk or Tcl.. try :
diff Framework/Tcl
I see symlinks at this place, not real file...Le 5 mai 2006 à 12:21, Tom Hennigan a écrit :I have it on mine here:/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtcl8.4.dylib/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtk8.4.dylibOn 5 May 2006, at 07:42, Jérôme Gagnon-Voyer wrote:Ok I found the problemOn
I have it on mine here:/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtcl8.4.dylib/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libtk8.4.dylibOn 5 May 2006, at 07:42, Jérôme Gagnon-Voyer wrote:Ok I found the problemOn my amsn package that works well to compile aMSN, there's a filelibtcl8.4.dylib inside tcl f
On Fri, 5 May 2006, Youness Alaoui wrote:
> I had it run every day, so it's always up to date, but still it won't
> find some files (normal filenames, no special char, simple a to z
> ascii), I do a locate on something, no result, do a find, find the file
> makes sure I had nothing wrong, do th
I had it run every day, so it's always up to date, but still it won't find
some files (normal filenames, no special char, simple a to z ascii), I do
a locate on something, no result, do a find, find the file makes sure I
had nothing wrong, do the locate again with part of the filename
exampl
On Fri, 5 May 2006, Youness Alaoui wrote:
> i always use :
> find | grep ...
> or
> find | grep -i ...
> (when locate doesn't work.. it doesn't always work, which is weird...)
it IS weird. here it always works, if i have run updatedb recently...
otherwise it warns anyway!
>
> KKRT
>
> On Fri,
i always use :
find | grep ...
or
find | grep -i ...
(when locate doesn't work.. it doesn't always work, which is weird...)
KKRT
On Fri, 05 May 2006 10:19:54 -0400, Benjamin <[EMAIL PROTECTED]> wrote:
if you use « locate » do a « updatedb » with root access before :)
if you use find, you can
if you use « locate » do a « updatedb » with root access before :)if you use find, you can use « find -iname » if you don't care about case !On 5/5/06,
Vivia Nikolaidou <[EMAIL PROTECTED]> wrote:
On Fri, 5 May 2006, Jérôme Gagnon-Voyer wrote:> What's the command to make a big search on all the har
If I remember correctly it is a symbolic link (or a copy) of the file Tk
or Tcl.. try :
diff Framework/Tcl Framework/libtcl8.4.dylib
if it says nothing, then the two files are the same and there you got your
library.
KKRT
On Fri, 05 May 2006 02:42:43 -0400, Jérôme Gagnon-Voyer
<[EMAIL PRO
On Fri, 5 May 2006, Jérôme Gagnon-Voyer wrote:
> What's the command to make a big search on all the hard drive via the
> terminal?
find / -name filename(slow but sure)
locate filename (faster)
at least these are on Linux:)
Ok I found the problemOn my amsn package that works well to compile aMSN, there's a filelibtcl8.4.dylib inside tcl framework folderandlibtk8.4.dylib inside tk.framework folderSo...last year...me or Youness...we put that file in that directory to make everything works. The big question is WHERE THAT
Yeah you're right. I tried the same th ing on a Intel Mac (Remote Desktop) and I get the same error as you. The only difference is that my aMSN package I use to compile on my normal mac is having more files. I think it's related to stub that are missing from the package and I will probably need hel
Okidoke, here's some output:gcc -g -O2 -O2 -w -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I../../Frameworks/Tcl.framework/Headers -I../../Frameworks/Tk.framework/Headers -I/usr/X11R6/include -I. -I./utils/linux/capture -I./utils/linux/capture/libng -I./utils/linux/capture/stru
Well I don't know why you should replace libtool by glibtool, the problem is elsewhere and you should probably keep the real libtool at the right place because this is what I use anyway.The static error you gave , I had it before, it's a problem somewhere inside aMSN compile files. Not inside libto
Hey,Here's what I've done. I re-downloaded aMSN 0.95 mac, replaced the 0.95 Scripts folder with the latest CVS. Then cd'd into the directory and ran these:which libtool/usr/bin/libtoolwhich glibtool/sw/bin/glibtoolSo I ran:make cleansudo mv /usr/bin/libtool /usr/bin/libtool-oldsudo ln -s /sw/bin/gl
And you did make clean? Try from the beginningLe 4 mai 2006 à 08:11, Tom Hennigan a écrit :Hey Jérôme, It still doesn't work even though I made sure that I'd ./configured, then modified the files, then done "make" on the file I still get errors. Can you run "which libtool", and see which version
Ordinateur-de-J-r-me-Gagnon-Voyer:/Applications/Utilities/amsn cvs-
true/msn/utils/macosx/tclAE2.0/Contents gagnonje$ which libtool
/usr/bin/libtool
Le 4 mai 2006 à 08:11, Tom Hennigan a écrit :
which libtool
---
Using Tomcat but need to
Hi Tom,
can't you do a 'whcih libtool' yourself, then see which one is used, and
move it to make sure the gnu libttol is used instead of apple's ?
just move it and make a symlink, or make sure the gnu libtool path appears
first in your $PATH
(example, if you have gnu libtool in /usr/bin and ap
Hey Jérôme,
It still doesn't work even though I made sure that I'd ./configured, then modified the files, then done "make" on the file I still get errors. Can you run "which libtool", and see which version of libtool your computer is running??
Tom
On 5/4/06, Jérôme Gagnon-Voyer <[EMAIL PROTEC
The error appear if you don't modify the file Compile.mk as I said. You run the configure FIRST. Then you modify the Compile.mk file THEN you type make.Le 3 mai 2006 à 17:55, Tom Hennigan a écrit :Hey,No problems putting aMSN into a binary for 0.96. I'm having a bit of trouble compiling aMSN though
Hey,No problems putting aMSN into a binary for 0.96. I'm having a bit of trouble compiling aMSN though (even using Jérôme's instructions)../configure works, and I don't get any errors from the compiling until I run make, I get:"/usr/bin/libtool: -static not specified, -s invalid"I have the fink ver
Hi J,
thanks for the commit and the explanation mail below...
I think what you're asking for is fairly easy... maybe not easily but at
least doable... If something comes up again, Tom will either ask or we'll
figure it out and we'll be able to fix the makefiles for everyone...
p.s.: be "dépe
Compiling aMSN on Mac OS X is a real disaster, Phil and/or Youness, can you make a small effort to improve it. That would HELP a lot to compile aMSN on Mac OS X-Intel. That's not normal that I'm the only one able to compile that. No one can guess theses steps without being a real expert in makefile
31 matches
Mail list logo