help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sudo fink install octave-atlas still running after 24 hours


From: Alexander Hansen
Subject: Re: sudo fink install octave-atlas still running after 24 hours
Date: Sun, 06 Jan 2013 17:16:35 -0700
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0

On 1/6/13 10:55 AM, Benjamin Abbott wrote:
> On Jan 6, 2013, at 10:21 AM, Richard Shinn <address@hidden> wrote:
> 
>> Hello,
>>
>> I'm trying to install octave on Mountain Lion on an Intel Core 2 Duo MacBook 
>> Pro . I  followed the instructions on this page. web page:
>>
>> www.finkproject.org/download/srcdist.php
>>
>> After doing the following and entering the last command to install, my 
>> machine was still, apparently installing (at 100% CPU capacity) 24 hours 
>> later. I finally killed the install. Can you help me figure out what when 
>> wrong? I can't believe the install could possibly take that long, even on my 
>> old Core Duo.
>>
>> $ xcode-select -switch /Applications/Xcode.app/Contents/Developer
>> $ sudo xcodebuild -license
>> $ cd $HOME/Downloads
>> # Downloaded the tar ball
>> $ tar -xvf fink-0.34-4.tar.gz
>> $ cd fink-0.34.4
>> $ ./bootstrap
>> $ /sw/bin/pathsetup.sh
>> $ fink selfupdate-rsync
>> $ fink index -f
>> # This command was still running 24 hours later at full CPU capacity
>> $ sudo fink install octave-atlas
>>
>> Thanks very much.
>>
>> Rich Shinn
> 
> Fink displays a lot info to keep the user informed as it is doing its work.  
> What was being displayed when you killed it?
> 
> Ben
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
> 

100% CPU capacity per CPU is the norm when building packages.  You can
reconfigure fink to use fewer CPUs, though this will slow down your builds.

And 24 hours is not unheard of to build Octave and all of its
dependencies.  GCC takes several hours on my not-so-old 4 core machine.
 ATLAS takes hours, too.

Basically, if the output that you see in the terminal keeps updating,
there should be no reason to suspect that anything is wrong.  When you
stop the build, that just means that you're going to have to start
whatever package was being built over again from the beginning--there is
no provision to resume builds.  Any other packages that were already
built are unaffected.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]