How do you compile rtmpdump in Mac OS X 10.6?

[sofrench]

Hi

I downloaded the files but I don't know how to compil.
Mac OSX 10.6.2
I did open the READme file. But I don't know what to do next and what else I need -OpenSSL ?and zlib?.
Can someone give me some help or to point me a tuto


Thanks

[bricula]

Osx 10.5.8
xcode tools 3.0
rtmpdump 2.2d won't compile...
what does I need? please, it's been 2 days and I'm still here compiling and watching errors...
can someone write a step by step tutorial? the readme file says nothing... please, I'm running out of options....

[jcj2002]

Originally Posted by bricula

Osx 10.5.8
xcode tools 3.0
rtmpdump 2.2d won't compile...
what does I need? please, it's been 2 days and I'm still here compiling and watching errors...
can someone write a step by step tutorial? the readme file says nothing... please, I'm running out of options....

I have succesfully compiled with OSX 10.6, last version rtmpdump v.2.3, which needs openssl 0.9.8 (for this you must upgrade to Mac OSX 10.6.5). Read the readme file on the source, gives so many information.

I am not a computer expert, but I get succes after many hours of testings and google documentations.

For your help, a step-by-step EXCELLENT tutorial for compiling and using rtmpdump you can see is at:

http://trick77.com/2010/07/31/captur...dump-mac-os-x/

Note than you must change libraries before (-soname with -dylib_install_name in /rtmpdump-2.3/librtmp/makefile).

The only action you need is :

$ cd (to the path rtmpdump-2.3 is)
$ make SYS=posix (under a terminal session).

Note: posix is part of the OSX system.

Obviously, for compiling you need the developer tools of Mac OSX 10.6 (XCode 3.2).

Hope this helps.

[goka]

Couldn't anyone just post a compiled version of rtmpdump 2.3 if they have succeeded in compiling it? It would be greatly appreciated!

The only downloadable precompiled version I could find was 1.6. It does the job so far, but I guess I'll bump in to some problems sooner than later.

[Yansky]

Originally Posted by goka

Couldn't anyone just post a compiled version of rtmpdump 2.3 if they have succeeded in compiling it? It would be greatly appreciated!

The only downloadable precompiled version I could find was 1.6. It does the job so far, but I guess I'll bump in to some problems sooner than later.

Did you bother to read through the thread?
http://trick77.com/2010/07/31/captur...dump-mac-os-x/

[StrickenFromHistory]

I get this error on Mac Intel 10.6

sudo make SYS=mingw
gcc -shared -Wl,-soname,librtmp.dll -o librtmp.dll rtmp.o log.o amf.o hashswf.o parseurl.o -lssl -lcrypto -lz -lws2_32 -lwinmm -lgdi32
ld: unknown option: -soname
collect2: ld returned 1 exit status
make[1]: *** [librtmp.dll] Error 1
make: *** [librtmp/librtmp.a] Error 2

[Skeeve]

Hi!

Maybe someone can help me in a (as I think) very basic problem.

I use OS X 10.5.8 and the openssl there is too old (OpenSSL 0.9.7l 28 Sep 2006).

So I downloaded, compiled and installed OpenSSL 1.0.0a 1 Jun 2010 in /usr/local/openssl. The default (old one) is still in /usr/bin.

But when I try to compile the latest rtmpdump, checked out with svn, and try to "make", I still get

In file included from rtmp.c:126:
handshake.h:67:2: error: #error Your OpenSSL is too old, need 0.9.8 or newer with SHA256

I tried export LD_LIBRARY_PATH=/usr/local/openssl/lib/
but still get the message.

Can anyone please give me a hint how to get rtmpdump compiled?

[carmelo42]

I also have a problem compiling rtmpdump 2.3 from sources tarballs, with Mac OS X 10.6.4 :

macbook:rtmpdump-2.3 Carmelo$ make SYS=MacOSX
gcc -Wall   -DRTMPDUMP_VERSION=\"v2.3\" -DUSE_OPENSSL  -O2 -fPIC   -c -o rtmp.o rtmp.c
gcc -Wall   -DRTMPDUMP_VERSION=\"v2.3\" -DUSE_OPENSSL  -O2 -fPIC   -c -o log.o log.c
gcc -Wall   -DRTMPDUMP_VERSION=\"v2.3\" -DUSE_OPENSSL  -O2 -fPIC   -c -o amf.o amf.c
In file included from amf.c:33:
bytes.h:74:2: warning: #warning "Float word order not defined, assuming the same as byte order!"
gcc -Wall   -DRTMPDUMP_VERSION=\"v2.3\" -DUSE_OPENSSL  -O2 -fPIC   -c -o hashswf.o hashswf.c
gcc -Wall   -DRTMPDUMP_VERSION=\"v2.3\" -DUSE_OPENSSL  -O2 -fPIC   -c -o parseurl.o parseurl.c
ar rs librtmp.a rtmp.o log.o amf.o hashswf.o parseurl.o
ar: creating archive librtmp.a
gcc -shared -Wl,-soname,librtmp.  -o librtmp. rtmp.o log.o amf.o hashswf.o parseurl.o  -lssl -lcrypto -lz 
ld: unknown option: -soname
collect2: ld returned 1 exit status
make[1]: *** [librtmp.] Error 1
make: *** [librtmp/librtmp.a] Error 2

I also have tried with sudo :

macbook:rtmpdump-2.3 Carmelo$ sudo make SYS=MacOSX
Password:
gcc -shared -Wl,-soname,librtmp.  -o librtmp. rtmp.o log.o amf.o hashswf.o parseurl.o  -lssl -lcrypto -lz 
ld: unknown option: -soname
collect2: ld returned 1 exit status
make[1]: *** [librtmp.] Error 1
make: *** [librtmp/librtmp.a] Error 2
macbook:rtmpdump-2.3 Carmelo$

[hyc]

Originally Posted by DaveFlash

While looking for a solution to the same problem as you guys "handshake.h:67:2: error: #error Your OpenSSL is too old, need 0.9.8 or newer with SHA256" rtmpdump 2.3 apparently is not recognizing openssl1.0.0d as higher version than the minimum req. 0.9.8.

I'm have an iMac with OS X 10.5.8 and a Snow Leopard dualbooted macbookpro (both 10.6.6 [stable] + 10.6.7 [beta]), on both machine and all 3 OS versions I get the same error. The reason I specifically quoted the above was that I though trying the same edit on the makefile

LIB_OPENSSL=-lssl -lcrypto -ldl

would make the problem go away, but it didn't.

So any help will be appreciated. Also, even though you use Linux, it doesn't make a difference, because both linux and mac os ar based on Unix, which means the comandline/terminal is the same.

//Dave

No, unfortunately MacOSX is NOT the same as every other Unix system. That's why the README says to use "make SYS=darwin" on MacOSX.

You can't just go typing random stuff in here. If you don't know how to compile software on your OS, go learn how. MacOSX has no libdl, so of course randomly adding "-ldl" to a Makefile variable won't fix any of your problems. It would only cause more problems. If you don't understand what that sentence meant, you need to go learn more before you're ready to build this.

finally make the project

make INC=-I/usr/local/ssl/include/ LDFLAGS=-L/usr/local/ssl/lib

This is the key step. If you installed a private copy of OpenSSL, you have to tell where that copy resides, and this is how it's done. If you don't get these paths right, then the compiler will only find the old version of OpenSSL that's in your default system location, and that's why you still get the complaint that your OpenSSL is too old even though you installed a newer one.

[Yansky]

I always had trouble building with OpenSSL. I switched over to using PolarSSL and found it to be easier.