Libraries not being installed with +universal

[Ryan Schmidt]

On Sep 6, 2009, at 15:53, Michael_google gmail_Gersten wrote:

> Kleiman-ibook:~ michael$ port installed | grep -v universal
> The following ports are currently installed:
>  bzip2 @1.0.5_2+darwin (active)
>  db46 @4.6.21_5 (active)
>  gdbm @1.8.3_1 (active)
>  openssl @0.9.8k_0+darwin (active)
>  readline @6.0.000_1+darwin (active)
>  sqlite3 @3.6.17_0 (active)
>  tk @8.5.6_1+darwin (active)
>  xorg-libXScrnSaver @1.2.0_0 (active)
>  xorg-scrnsaverproto @1.2.0_0 (active)
>
> I think that's pretty clean.

Note that openssl and readline are pretty common dependencies. You  
should build them, and bzip2, db46 and sqlite3, as universal as well  
so you don't run into problems later.

> Compile:
>
> Kleiman-ibook:~ michael$ sudo port install gtk2 +universal
> Password:
> --->  Computing dependencies for gtk2
> --->  Fetching expat
> --->  Verifying checksum(s) for expat
> --->  Extracting expat
> --->  Configuring expat
> --->  Building expat
> --->  Staging expat into destroot
> --->  Installing expat @2.0.1_0+universal
> --->  Activating expat @2.0.1_0+universal
> --->  Cleaning expat
> --->  Fetching gperf
> --->  Verifying checksum(s) for gperf
> --->  Extracting gperf
> --->  Configuring gperf
> --->  Configuring gperf for architecture ppc
> ...
>
> Alright, it's compiling, but that first port -- expat -- going in as
> universal in only one form?

It looks like expat was successfully built universal. You should be  
able to verify this using the "file" or "lipo -info" commands, e.g. on  
my system:

$ lipo -info /opt/local/lib/libexpat.1.5.2.dylib
Architectures in the fat file: /opt/local/lib/libexpat.1.5.2.dylib  
are: x86_64 i386
$

If you base your "only one form" statement on the fact that the expat  
build did not include lines like "Configuring expat for architecture  
ppc", then that is only because the expat port does not use the  
muniversal portgroup which produces that output; expat uses the built- 
in universal variant that does all architectures all at once, so there  
are not separate stages for the separate architectures about which  
separate messages could be printed.