[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sudo fink install octave-atlas still running after 24 hours
From: |
Sergei Steshenko |
Subject: |
Re: sudo fink install octave-atlas still running after 24 hours |
Date: |
Mon, 7 Jan 2013 20:52:55 -0800 (PST) |
----- Original Message -----
> From: Ben Abbott <address@hidden>
> To: Richard Shinn <address@hidden>
> Cc: "address@hidden Help" <address@hidden>
> Sent: Tuesday, January 8, 2013 6:13 AM
> Subject: Re: sudo fink install octave-atlas still running after 24 hours
>
>
> On Jan 7, 2013, at 11:02 PM, Richard Shinn wrote:
>> On Jan 6, 2013, at 9:55 AM, Benjamin Abbott <address@hidden> 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
>>
>> Ben,
>>
>> I've attached a sample of the output. Just reams and reams of what
> looks to me like "typical" build output. It literally ran at 100% cpu
> capacity for well over 25 hours. Is it conceivable it could take that long?
> I'm thinking it got into some kind of loop in the build script that just
> kept trying to build it over and over again instead of erroring out properly.
>>
>> Thanks very much for any help you can provide. I'd very much like to
> get this working.
>>
>> Rich Shinn
>
> I don't see anything unusual there. I had a mac mini with a Intel Core 2
> Duo, but it died last week. So, I'm not able to check.
>
> I recommend you try again. What you showed me doesn't look to have gotten
> to Octave yet. The good news is that many dependencies have probably already
> been built, so the build you terminated isn't a total waste.
>
> Ben
>
Shouldn't there be some logs somewhere ?
Regards,
Sergei.