InsightToolKit did not build
Frank J. R. Hanstick
trog24 at comcast.net
Fri Jan 1 18:08:54 PST 2010
Hello,
It is not very encouraging that it took so long your system. I only
have a dual 1.73 GHz PowerPC G4 on a 133 MHz bus (I am assuming you
have a dual core intel with a faster bus) and 1 MB RAM. Disk space is
not a problem (165 GB available).
This is the fourth time that I hit the same error. I am wondering of
the problem is trying to build to a PPC G4. I am going to take a
quick look at the source code (downloaded itk via CVS from the site)
after filing a bug report.
On Jan 1, 2010, at 5:47 PM, Ryan Schmidt wrote:
>
> On Jan 1, 2010, at 19:21, Frank J. R. Hanstick wrote:
>
>> Updated to MacPorts 1.8.2, upgraded all the installed ports, and
>> then tried to install insighttoolkit. Installation failed and I
>> reran the installation with debug enabled and got the following:
>
> I saw your previous message on this topic on December 24, whereupon
> I tried to build InsightToolkit to see what happened for me. I did
> not realize how large this port is. With Snow Leopard on my 2.2 GHz
> MacBook Pro with build.jobs=1, I think it took over 12 hours and
> over 8 GB of disk space to build, after which it said it ran out of
> resources (I think it said memory -- this machine has 4 GB RAM and >
> 50GB free disk space). I simply re-ran the port install command and
> it completed successfully; it takes 1.6GB of disk space after
> installation.
>
> If retrying (multiple times if necessary) does not lead to a
> successful build for you, please file a ticket in the issue tracker,
> as always, with as much debug output and other information about
> your system as you can produce. Using build.jobs=1 will also help
> reduce confusion and aide in reading the log.
>
>
Frank J. R. Hanstick
trog24 at comcast.net
More information about the macports-users
mailing list