difficulty cross-compiling on Leopard for Tiger

[Ryan Schmidt]

On Oct 21, 2008, at 19:18, Zach Fine wrote:

> Thanks for filing that ticket.
>
> It looks like it has yet to be resolved, and I'm once again looking  
> to put lighttpd and php on my apple TV.
>
> I'd be happy to help out if I knew how to add a universal variant  
> to cclient. Can anyone point me in the direction of relevant  
> information? I'm guessing there's some flag that must be inserted  
> into a file so that when +universal is selected the flag is added  
> to the commands that compile cclient, but I'm not sure how to go  
> about this.
>
> Thanks for any help or info.
>
> Zach Fine

I'm sorry Paul hasn't responded to that ticket. He must be busy with  
other things. Or he may have forgotten the ticket. You could email  
him and ask.

I also filed this ticket requesting cclient be updated to the current  
version:

http://trac.macports.org/ticket/16950

Software that's written in "the usual way" can be built universal  
without any special additions; just follow this document:

http://developer.apple.com/technotes/tn2005/tn2137.html

MacPorts internally uses the method described in "Configuring for  
universal binaries" to build universal ports. Some software can't be  
built universal using those steps. In that case, someone (e.g. the  
port maintainer, you, another volunteer) must figure out why and how  
to fix it. Maybe a file (e.g. configure script, Makefile, libtool)  
can be patched in some way to pass the correct parameters along. In  
other cases, the build must be repeated once for each architecture  
and the result glued together with the lipo program. See the openssl  
and cairo ports for examples of this. MacPorts has no support for  
this mechanism built in, so ports that need this mechanism get rather  
convoluted.