[rtmpdump] PowerPC Build?

[Howard Chu]

Yansky . wrote:
> I seem to be having some problems with the compile. I'm using
> rtmpdump-2.2b and using these paramaters for make: make posix
> XCFLAGS="-arch ppc"

That will build a PPC-only binary. Don't you want to build a fat binary with 
support for both PCC and Intel?

Anyway, don't do it like that. Use
   make posix CC="gcc -arch ppc"

> I'm building it on an intel-based mac as I don't have access to a
> powerpc at the moment.
>
> Here is the full make log:
> Yanskopoliss-Mac-mini:rtmpdump-2.2b yansky$ make posix XCFLAGS="-arch ppc"
> gcc -Wall -arch ppc  -DRTMPDUMP_VERSION=\"v2.2b\" -O2   -c -o
> rtmpdump.o rtmpdump.c
> gcc -Wall -arch ppc  -DRTMPDUMP_VERSION="v2.2b" -O2   -c -o rtmp.o rtmp.c
> In file included from rtmp.c:123:
> handshake.h: In function ‘SHandShake’:
> handshake.h:743: warning: comparison is always false due to limited
> range of data type
> gcc -Wall -arch ppc  -DRTMPDUMP_VERSION="v2.2b" -O2   -c -o log.o log.c
> gcc -Wall -arch ppc  -DRTMPDUMP_VERSION="v2.2b" -O2   -c -o amf.o amf.c
> In file included from amf.c:31:
> bytes.h:73:2: warning: #warning "Float word order not defined,
> assuming the same as byte order!"
> gcc -Wall -arch ppc  -DRTMPDUMP_VERSION="v2.2b" -O2   -c -o hashswf.o hashswf.c
> gcc -Wall -arch ppc  -DRTMPDUMP_VERSION="v2.2b" -O2   -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 -Wall  rtmpdump.o librtmp/librtmp.a  -o rtmpdump -lssl -lcrypto -lz
> ld: warning: in rtmpdump.o, file is not of required architecture
> ld: warning: in librtmp/librtmp.a, file is not of required architecture
> Undefined symbols:
>    "_main", referenced from:
>        start in crt1.10.6.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [rtmpdump] Error 1
> make: *** [posix] Error 2
>
>
> On Tue, Apr 6, 2010 at 7:38 AM, Howard Chu<hyc at highlandsun.com>  wrote:
>> Yansky . wrote:
>>>
>>> Hi, Is it possible to compile the source to a build that will work on
>>> PowerPC CPU's?
>>>
>>> If so, could you give me some pointers on what make details I would need
>>> to use?
>>
>> Nothing special required. The code is portable and will compile on anything.
>>>
>>> Some users have requested PowerPC builds here:
>>> http://forums.whirlpool.net.au/forum-replies.cfm?t=1381760&p=19#r362