MacPorts and OpenMP---or how to build "everything" with MacPorts GCC?

[Dominik Reichardt]

Universal builds are needed because not everything runs as 64bit build which is native to current OS X machines. Examples are Wine and DOSBox.

Am 21.06.2013 um 12:54 schrieb Hans Ekkehard Plesser <hans.ekkehard.plesser at umb.no>:

> 
> Dear all!
> 
> Thank you very much for your comprehensive answers! I will give the default_compilers switch a shot.
> 
> I realize that Clang has many advantages compared to GCC, it is just unfortunate that it lags behind on OpenMP. Let's hope that OpenMP will make it into Clang soon (and into the version Apple ships with OSX ...)!
> 
>> This is true, but only for single-architecture builds. FSF GCC still cannot create universal binaries, so switching configure.compiler to macports-gcc* or macports-dragonegg* instantly breaks universal builds for every port that doesn't use the muniversal PortGroup (and possibly some that do).
> 
> Just out of curiosity: Why are universal builds important for MacPorts? Since one builds everything on one's own machine anyways, wouldn't it suffice to compile just for that architecture?  I don't know how much build-bot power you require (and how you pay for it) to provide the binaries that you now provide, but providing both 32 and 64 bit binaries would at most require twice as much.
> 
> Best regards,
> Hans
> 
> --
> 
> Dr. Hans Ekkehard Plesser, Associate Professor
> Head, Basic Science Section
> 
> Dept. of Mathematical Sciences and Technology
> Norwegian University of Life Sciences
> PO Box 5003, 1432 Aas, Norway
> 
> Phone +47 6496 5467
> Fax   +47 6496 5401
> Email hans.ekkehard.plesser at umb.no
> Home  http://arken.umb.no/~plesser
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users