1 |
On Friday, 26 January 2018 13:20:04 GMT Walter Dnes wrote: |
2 |
> On Wed, Jan 24, 2018 at 11:43:31AM +0000, Peter Humphrey wrote |
3 |
> |
4 |
> > This is with gcc 4.9.4, and I get the same with gcc 6.4.0. I've only |
5 |
> > just noticed that about -fPIC; haven't all those problems been fixed |
6 |
> > by now? |
7 |
> |
8 |
> This may or may not be relavant. I build Pale Moon manually for my |
9 |
> home machines, using the Mozilla Firefox process. 64-bit builds worked |
10 |
> fine with GCC-6.4.0 on profile 13.0. Anything built with GCC-6.x under |
11 |
> profile 17.0 segfaults in 10-15 seconds after launching Pale Moon. A |
12 |
> custom-built GCC-5.4.0 builds a stable Pale Moon. |
13 |
|
14 |
I haven't yet managed to compile 27.7.1 at all with either GCC 6.4.0 or |
15 |
4.9.4, using the palemoon overlay via layman, on profile default/linux/ |
16 |
amd64/17.0/desktop/plasma. I get the loader errors I quoted on Wednesday. |
17 |
|
18 |
I wonder whether I should try the 17.1 profile... |
19 |
|
20 |
> I'm currently doing a test build with GCC-6.4.0 on my 32-bit desktop, |
21 |
> having just finished the migration to 17.0. Current ICEWM 1.4.2 (and |
22 |
> 1.4.0) crashes out of X to a text console when I click on the menu bar |
23 |
> at the bottom. I've dropped back to 1.3.12-r1 ...and copied the ebuild |
24 |
> over to a local overlay. I'm not liking profile 17.0 far. |
25 |
|
26 |
-- |
27 |
Regards, |
28 |
Peter. |