You are not logged in.
Pages: 1
Topic closed
I've downloaded the AUR snapshot, and began to build the package. The system got slowed down, then, after two hours, it's hot stucked. not Freezed, just extremly slow for any reaction. I think it is not normal, do I? The hardware:
Processor : 2x Intel(R) Celeron(R) CPU G465 @ 1.90GHz
Memory : 3716MB
Offline
If it's anything like firefox then it will take a long time, more than 2 hours isn't uncommon - especially with a CPU like yours.
Where are you building it?
Offline
You would probably be better served by the palemoon-bin package on that hardware.
It takes about 30 minutes to compile on my i7.
Mod note: moving to AUR issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
As above, that doesn't seem that unusual. I've also never built palemoon, but I did try building firefox a couple years ago - and even then I think it might have required more than 4GB of build space: if you are building in ram (e.g. under /tmp) you will likely not have enough space.
If you don't have swap enabled, the build will just be killed. If you have swap enabled, your system will grind to a miserably slow crawl for an indefinite period.
If you do need to build such a big package, definitely don't do it in ram. But if you don't absolutely need to build it yourself, I'd not even try on that hardware - find a precompiled version. (Note I say this as someone who has more modest hardware than that - but there are some builds I just wouldn't think of doing).
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
As above, that doesn't seem that unusual. I've also never built palemoon, but I did try building firefox a couple years ago - and even then I think it might have required more than 4GB of build space: if you are building in ram (e.g. under /tmp) you will likely not have enough space.
This. Firefox (or Palemoon) takes a lot of memory to compile and link. It will definitely take more than two hours on your hardware, and it may fail during the later linking steps.
Why are you building from source? If you don't need to set (or unset) flags that are not used by the normal build, use the -bin package.
Last edited by 2ManyDogs (2017-04-25 00:28:17)
Offline
Hm, okay. I tried to build it in RAM, so next I build it on HDD. And my spiritual misery that I somehow don't like precompiled binaries, they are seems a bit dirty, and I try to avoid it. Thanks for help!
Offline
Hm, okay. I tried to build it in RAM, so next I build it on HDD. And my spiritual misery that I somehow don't like precompiled binaries, they are seems a bit dirty, and I try to avoid it. Thanks for help!
You may still run out of memory. But go ahead and try if you must.
You use a distro that is composed of precompiled binaries (unless you build everything yourself from ABS). Does that cause you the same sort of spiritual misery? Maybe you should use Gentoo or CRUX.
Last edited by 2ManyDogs (2017-04-25 19:57:03)
Offline
Just for the fun of it i did try to compile it on my old Dell laptop:
MODEL: Dell Latitude E4310
CPU: Intel Core i5-520M 2.40GHz (1st gen rev 2)
RAM: 3841 MB (no swap)
SSD: 120 GB SanDisk SDSSDHII
I took a little less than two hours on this hardware. So the RAM you have is sufficient to build palemoon (uses about 2.5 GB at the most). And 5 GB available space on your HDD should be enough.
Edit: The one I did try was:
https://aur.archlinux.org/packages/palemoon/
Last edited by olegabrielz (2017-04-25 22:12:39)
Be aware of my Newbie Powers
Offline
Build time not in tmpfs will differ *drastically* between and HDD and SDD.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Maybe start it up at bedtime then.
Edit:
I'll do a test. Swap the SSD with an old 80 GB 5400 RPM HDD and compile it again. It would be fun to see the difference.
Edit2:
The test is done. Surprisingly the difference between SSD and HDD was less than I had expected. It took just over two hours to compile with HDD. It was only ten minutes in difference between SSD and HDD.
Last edited by olegabrielz (2017-04-26 02:14:14)
Be aware of my Newbie Powers
Offline
Build time not in tmpfs will differ *drastically* between and HDD and SDD.
And olegabrielz was using a dual-core hyperthreaded i5 at 2.4 GHz, while the OP is using a single-core hyperthreaded Celeron at 1.9 Ghz. Big difference there too.
I used to run Gentoo on a single-core 32-bit Celeron, and as olegabrielz suggests, I often let compiles run overnight.
I guess the OP's original question has been answered -- more than 2 hours to compile Palemoon on his hardware is normal.
Offline
About 21 minutes with a FX-8350, 8GB RAM, HDD. The speed it compiles is part of the reason I use it. Chromium (Inox) is more like 1h 30m.
Offline
We really don't need everyone and their mother saying how long it takes to compile this on harware that is orders of magnitude more powerful than the OPs.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
@2ManyDogs: Not a bad idea - compiling from ABS as install a system. I'll do it with a new laptop, when I will got one.
Offline
So the RAM you have is sufficient to build palemoon (uses about 2.5 GB at the most).
Ah, that's it! I forgot not to run some other programs, so I was out of memory.
Offline
i may get scolded for my input but hey, why not use the palemoon installer script, it's what i use on my arch and works
http://linux.palemoon.org/download/installer/
Offline
Because you'll have files that aren't maintained by pacman flying around on the system, which might have undesirable side effects depending on how it sets itself up
Offline
And because the palemoon installer script installs the precompiled binaries, which the OP specifically said he didn't want to do.
Offline
We are done, now.
Closing
Offline
Pages: 1
Topic closed