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/libtool

which glibtool
/sw/bin/glibtool

So I ran:
make clean
sudo mv /usr/bin/libtool /usr/bin/libtool-old
sudo ln -s /sw/bin/glibtool /usr/bin/libtool
./configure
<<Then I edited makefile and compile.mk>>
make

Then I get errors from ranlib that:
ranlib: unrecognized option `-f'
Try `ranlib --help' for more information.
ar: internal ranlib command failed

So I'm guessing glibtool isn't what is needed.

I've got fairly recent dev-tools (from Apple) (2.2), but just incase, I'm downloading 2.2.1 now incase libtool has been updated/changed. This is the only thing that I can think of atm.

Tom


On 4 May 2006, at 16:39, Jérôme Gagnon-Voyer wrote:

And you did make clean? Try from the beginning
Le 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 of libtool your computer is running??
 
Tom

 
On 5/4/06, Jérôme Gagnon-Voyer <[EMAIL PROTECTED]> wrote:
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 (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 version of libtool as well, but in this output it is using the version that is installed by the devtools. (fink is like apt-get, but installs everything with --prefix=/sw, so that is how I know this is Apple's libtool).

 
The error means that the .so file is corrupt (I think) and aMSN doesn't load when i replace the .dylibs. I get the libtool error for both TkCximage, and Webcamsn.

 
Any ideas!?

 
Tom

 

 

On 3 May 2006, at 03:07, Youness Alaoui wrote:

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épendant" to me => be dependant on me.. OR depend on me..

 
gtg
KKRT

 
On Tue, 02 May 2006 21:05:47 -0400, Jérôme Gagnon-Voyer <[EMAIL PROTECTED]> wrote:

 
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.

 
Theses are the instructions for Tom Hennigan to compile Webcamsn and
TkCximage

 
Move all aMSN CVS stuff inside a TCL-TK package(the TCL-TK package
should be a package with TCL-TK frameworks included (embedded)).
Right Click
Show Packet Contents
Contents
Resources
Scripts

 
After, use the terminal and change directory to this "Scripts" directory

 
Example:
cd /Users/gagnonje/aMSN-build.app/Contents/Resources/Scripts/

 
Type that:
./configure
After, you modify the file compile.mk

 
you put # in front of theses 2 lines
#compile_c = $(CC) $(CFLAGS)  -c -o $@ $<
#compile_cc = $(CXX) $(CXXFLAGS)  -c -o $@ $<
replace them by
compile_c = $(CC) $(CFLAGS)  -fno-common -c -o $@ $<
compile_cc = $(CXX) $(CXXFLAGS) -fno-common -c -o $@ $<

 
Inside the makefile
Replice the lines TCL_INC_SPEC, TCL_STUB_LIB_SPEC TK_INC_SPEC and
TK_STUB_LIB_SPEC by theses lines

 
# Directories in which the Tcl core can be found
TCL_INC_SPEC    = -I../../Frameworks/Tcl.framework/Headers
TCL_STUB_LIB_SPEC = -L../../Frameworks/Tcl.framework -ltcl8.4

 
# Directories in which the Tk core can be found
TK_INC_SPEC    = -I../../Frameworks/Tk.framework/Headers
TK_STUB_LIB_SPEC = -L../../Frameworks/Tk.framework -ltk8.4

 
make

 
---If something doesn't work or you forget something. Start over
again with: Make clean

 
go to
utils/webcamsn
rename webcamsn.so to webcamsn.dylib
move it to
utils/macosx/webcamsn

 
go to
utils/tkcximage
rename TkCximage.so to TkCximage.dylib
move it to
utils/macosx/TkCximage

 
Youness and Phil: the steps to improve are the lines I have to change
inside compile.mk and makefile. Would be good also to not have to
rename tkcximage.so. Would be good to move the file automatically to
the right place but I don't know if it's possible so it's not necessary.

 
To compile aMSN on Mac OS X intel you probably need a TCL-TK Package
in Universal version to put the stuff inside. After you need to
compile webcamsn and tkcximage in universal. And you probably need an
Intel mac, in theory you can do that on a Mac PPC too but I already
tried and it doesn't work very well (at all).

 
The first time you ./configure inside amsn, you will probably need
some package on your computer that you don't have by default. I don't
remember witch one but the .configure script will tell you. I got
them with Fink and DarwinPorts. Of course you need the Developer
Tools installed.

 
So now all my knowledge about compiling aMSN is there, that shoudn't
be difficult like that so please try to improve that, that's not
normal that i'm the only one being able to compile it. I don't like
having a big project be "dépendant" to me, anybody should be able to
do that so if i'm not here anymore, it can continue to work.

 

 

 
-- 
KaKaRoTo

 

 
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
_______________________________________________
Amsn-devel mailing list

------------------------------------
Tom Hennigan


 

 



------------------------------------
Tom Hennigan


Reply via email to