[Slackbuilds-users] Cant seem to build webkitgtk or webkitgtk3 on Slackware64-14.1

[Aaditya Bagga]

Aaditya Bagga wrote:
> Nick Warne wrote:
>> Hi Aaditya,
>>
>> Aaditya Bagga wrote, On 15/11/13 17:08:
>>> Nick Warne wrote:
>>>> Hi Aaditya,
>>>>
>>>> Aaditya Bagga wrote, On 15/11/13 16:52:
>>>>> Aaditya Bagga wrote:
>>>>>> Matteo Bernardini wrote:
>>>>>>> as those looks to me like just warnings, have you tried to let it
>>>>>>> finish and see if all goes fine?
>>>>>
>>>>>> Followed your suggestion, and it seems to be building for *more than
>>>>>> an hour *now! How long do you reckon it takes to build webkitgtk? 
>>>>>> All
>>>>>> packages I built previously took 1-2 minutes. And I have a 
>>>>>> reasonably
>>>>>> fast CPU, i5 3210m 2.5Ghz
>>>>>
>>>>> After an hour and about a quarter-hour, it finally seems to have 
>>>>> built!
>>>>
>>>> For advice, some things (even what seems a smaller source code) can
>>>> sometimes take longer.
>>>>
>>>> e.g. On my notebook (atom single core with HT @ 1.66), I can build a
>>>> custom kernel in 42 minutes.  My server amd64 can build a custom
>>>> kernel in 10 minutes.
>>>>
>>>> Yesterday I built Inkspot on my notebook - 4 hours nearly ;)
>>>>
>>>> So until you build, you just do not know - just don't stop it.
>>>>
>>>> Nick
>>> Thx for the info Nick :)
>>>
>>> Do you have some more tips for me..like if I can clear out my /tmp of
>>> all the stuff that gets created while building packages, and if I can
>>> change the default directory where the packages are built and where 
>>> they
>>> are moved to after being built.
>>
>>> Thx ;)
>>
>> I have this added to /etc/rc.d/rc.6 on all my Slack boxes - it clears 
>> /tmp/ out on each shutdown:
>>
>> # Clear /var/lock/subsys.
>> if [ -d /var/lock/subsys ]; then
>>   rm -f /var/lock/subsys/*
>> fi
>>
>> # Nick - 05/09/2013 - clear /tmp
>> echo "Clearing out /tmp/*."
>> if [ -d /tmp ]; then
>>   rm -rf /tmp/*
>> fi
>>
>> # Turn off swap:
>> echo "Turning off swap."
>> /sbin/swapoff -a
>> /bin/sync
>>
>> I have included the surrounding code so you can see where I put it - 
>> around line 207.
>>
>> Nick
> Ah, thanks :)
>
> That gives me an idea :)
>
> du -ch /tmp | grep total
>
> If its greater than a specified value, say 2gb, I would invoke your 
> function to clear the cache :)
> (Was surprised to see that it currently occupies 975M)
>
>
I also have one more idea :)

Before removing the cache, copy the built packages-

cp /tmp/*.txz /home/aaditya/packages