View previous topic :: View next topic |
Author |
Message |
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 2:42 pm Post subject: Issues compilling SDDM |
|
|
I'm currently trying to install SDDM (I'm currently using SLiM, but on my laptop I'm currently changing over to Wayland, which SLiM dosn't seem to support). However Portage gets stuck and says "Incompatible processor. This Qt build requires the following features: aes", I also tried installing qtwayland earlier which had the exact same issue. My laptops CPU is a Celeron N2940 which according to https://en.wikipedia.org/wiki/AES_instruction_set#Intel my CPU does support the instruction (it's a Silvermont CPU).
How should I try and fix this? I was thinking of somehow conving the software that my CPU is supported or somehow to force it to compile anyway, but I'm not really sure how to do either. |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30917 Location: here
|
Posted: Wed Jan 09, 2019 2:49 pm Post subject: |
|
|
You use -march=native? If yes what return command gcc -march=native -E -v - </dev/null 2>&1 | grep cc1? _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 3:04 pm Post subject: |
|
|
I'm using -march=silvermont because I also recently setup distcc with my desktop and laptop. I also stopped distccd so it's not an issue with distcc.
Heres the output from that command:
Code: | gcc -march=native -E -v - </dev/null 2>&1 | grep cc1
/usr/libexec/gcc/x86_64-pc-linux-gnu/7.3.0/cc1 -E -quiet -v - -march=silvermont -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -mno-sse4a -mcx16 -msahf -mmovbe -mno-aes -mno-sha -mpclmul -mpopcnt -mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-sgx -mno-bmi2 -mno-tbm -mno-avx -mno-avx2 -msse4.2 -msse4.1 -mno-lzcnt -mno-rtm -mno-hle -mrdrnd -mno-f16c -mno-fsgsbase -mno-rdseed -mprfchw -mno-adx -mfxsr -mno-xsave -mno-xsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb -mno-mwaitx -mno-clzero -mno-pku -mno-rdpid --param l1-cache-size=24 --param l1-cache-line-size=64 --param l2-cache-size=1024 -mtune=silvermont |
|
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30917 Location: here
|
Posted: Wed Jan 09, 2019 3:09 pm Post subject: |
|
|
Try to compile with -march=native I suspect that -march=silvermont add -maes and your cpu not support it _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 3:10 pm Post subject: |
|
|
Jaglover wrote: |
Is aes listed? |
Strangely no it isn't. Maybe that could indicate something is wrong with my kernel? |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 3:17 pm Post subject: |
|
|
Actually I made a mistake, just to be sure, I read up more on specifically the Silvermont Bay Trail-M and Trail-D processors and it turns out my CPU is a Tail-M CPU! So it dosn't actually support aes.
So, in that case, does anybody know how I would still install SDDM anyway? Or am I just out of luck? It's still a fairly recent CPU so I would think that the software should be able to compile without that instruction to support some of the older CPUs |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 3:19 pm Post subject: |
|
|
Jaglover wrote: | According to this new aes instruction set is not supported by this CPU. |
Yep you would be right. Sorry about my mistake.
Quote: | Try to compile with -march=native I suspect that -march=silvermont add -maes and your cpu not support it |
Alright, I'll try that. |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30917 Location: here
|
Posted: Wed Jan 09, 2019 3:21 pm Post subject: |
|
|
Sol33t303 wrote: | Quote: | Try to compile with -march=native I suspect that -march=silvermont add -maes and your cpu not support it |
Alright, I'll try that. |
Or with -march=silvermont -mno-aes -O2 -pipe _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 3:22 pm Post subject: |
|
|
Nope, it dosn't look like compilling with march=native worked. |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Wed Jan 09, 2019 3:24 pm Post subject: |
|
|
fedeliallalinea wrote: | Sol33t303 wrote: | Quote: | Try to compile with -march=native I suspect that -march=silvermont add -maes and your cpu not support it |
Alright, I'll try that. |
Or with -march=silvermont -mno-aes -O2 -pipe |
That didn't work either. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Thu Jan 10, 2019 2:33 am Post subject: |
|
|
Please post the exact emerge command you executed and the error output it produced. |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Thu Jan 10, 2019 3:32 am Post subject: |
|
|
Hu wrote: | Please post the exact emerge command you executed and the error output it produced. |
The exact command in running is "sudo emerge sddm"
Here is the exact output of the command https://pastebin.com/jUJsUjrb |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30917 Location: here
|
Posted: Thu Jan 10, 2019 7:18 am Post subject: |
|
|
The build.log output is truncated, you can post full build.log? _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Fri Jan 11, 2019 2:54 am Post subject: |
|
|
It looks like dev-qt/qtdbus owns the program that aborts. If you are sure that your CPU is supported, you should investigate that package to find why it disagrees with you. |
|
Back to top |
|
|
|