On 2012-08-29 20:34, Joshua Root wrote:
> On 2012-8-29 23:33 , Rainer Müller wrote:
>> Note that universal archives do not indicate which architectures they
>> include in the file name and thus, we could not distinguish different
>> architectures with the current code.
>
> Actually, they do and we
On Aug 29, 2012, at 06:49, Mojca Miklavec wrote:
> On Wed, Aug 29, 2012 at 5:19 AM, Ryan Stonecipher wrote:
>> Some ports have +universal as a default variant.
>> When such ports have "big" dependencies such as qt4-mac, gcc4x, or
>> atlas they take hours to build and install.
>> The buildbot make
On Aug 29, 2012, at 22:40, Ryan Stonecipher wrote:
> This appears to be the issue on my computer as well.
> Virtualbox builds a kernel module for architectures listed by running uname
> -m.
Right. Virtualbox is special in that it builds a kernel module so it needs to
build for the architectur
This appears to be the issue on my computer as well.
Virtualbox builds a kernel module for architectures listed by running uname
-m.
Is this something that should be handled differently in Virtualbox which
calls itself non-universal in its portfile?
Ryan Stonecipher
On Wednesday, August 29, 2012,
On 2012-8-29 23:33 , Rainer Müller wrote:
> Note that universal archives do not indicate which architectures they
> include in the file name and thus, we could not distinguish different
> architectures with the current code.
Actually, they do and we can. :-)
- Josh
___
On Aug 28, 2012, at 10:40 PM, Ryan Schmidt wrote:
>
> On Aug 28, 2012, at 22:19, Ryan Stonecipher wrote:
>
>> Some ports have +universal as a default variant.
>> When such ports have "big" dependencies such as qt4-mac, gcc4x, or
>> atlas they take hours to build and install.
>> The buildbot make
On 2012-08-29 13:49, Mojca Miklavec wrote:
> Or another buildbot which would try to build all the ports as universal ;)
> (or i386-only when 64-bit cannot be built ;)
The definition of +universal may vary from system to system since the
universal_archs config option can be changed in macports.conf
On Wed, Aug 29, 2012 at 5:19 AM, Ryan Stonecipher wrote:
> Some ports have +universal as a default variant.
> When such ports have "big" dependencies such as qt4-mac, gcc4x, or
> atlas they take hours to build and install.
> The buildbot makes installing default single-architecture binaries painles
On 2012-8-29 13:19 , Ryan Stonecipher wrote:
> Some ports have +universal as a default variant.
> When such ports have "big" dependencies such as qt4-mac, gcc4x, or
> atlas they take hours to build and install.
> The buildbot makes installing default single-architecture binaries painless.
> Could t
On Aug 28, 2012, at 22:19, Ryan Stonecipher wrote:
> Some ports have +universal as a default variant.
> When such ports have "big" dependencies such as qt4-mac, gcc4x, or
> atlas they take hours to build and install.
> The buildbot makes installing default single-architecture binaries painless.
>
Some ports have +universal as a default variant.
When such ports have "big" dependencies such as qt4-mac, gcc4x, or
atlas they take hours to build and install.
The buildbot makes installing default single-architecture binaries painless.
Could the buildbot be adapted to also provide +universal binar
11 matches
Mail list logo
