libgcrypt and +universal variant

Ryan Schmidt ryandesign at
Wed Jun 6 12:02:48 PDT 2007

On Jun 6, 2007, at 11:43, Chris Pickel wrote:

> Near the end, it tries to extract files from the static lib, which  
> fails because the lib is built for multiple architectures. In other  
> words, the file format is correct insofar as it's being built  
> +universal, but the port expects otherwise.
> This seems to be because the library builds itself as separate  
> libraries, then takes them apart to build the single library.  
> Weird. Anyway, I got the port to build +universal by adding this  
> line to the Portfile (`port file libgcrypt`):
> variant universal { configure.args-append --disable-static }
> This disables the static libs that +universal is failing on, which  
> is not a great fix, but I don't know if it can be improved on  
> without a major patch. I also still can't guarantee that it will / 
> work/ with +universal, so I'd be interested in hearing results of  
> that too. (if it does, I'll commit that line to the official portfile)

Doesn't redefining "variant universal" like that _overwrite_ the  
default universal variant MacPorts provides, thereby making it no  
longer attempt to build anything universal?

More information about the macports-users mailing list