Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
> On 2018-09-19, at 17:54, Jack wrote: > > Unless I'm missing something, I'm surprised nobody has mentioned one > potential problem. Unless you are careful, code you compile for an AMD may > not run on an Intel. If you are just going to compile binary packages to > move and install, this might be OK (assuming you don't trip over trying to > run test during a build.) You should be able to come up with settings so > compiled code will run on either architecture, but I have no idea what the > side effects might be, such as larger and/or less efficient code. I almost > wonder if this doesn't count as cross-compiling, even though it is not a > totally incompatible architecture. Hopefully someone can either expand on > this, or tell me why I'm barking up the wrong tree. I've dealt with this problem before. The key is flags like -mtune=generic and not using -march=native. Optimisations should still be okay. Andrew
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
чт, 20 сент. 2018 г. в 0:56, Jack : > > On 9/19/18 5:45 PM, gevisz wrote: > > вт, 18 сент. 2018 г. в 22:44, George Kettleborough : > >> If you can run gcc on the new system first you can find out what flags > >> -march=native would produce and use those. See: > >> https://blogs.gentoo.org/mgorny/2014/06/23/inlining-marchnative-for-distcc/ > > Thank you for the link. > > > > It would be useful if I had an access to the target computer and decided > > to set up distcc. May be I would. In the future. However, currently, I don't > > have access to the target computer and hope to get without such an access. > > Just with the full name of the processor and the output of lspci command > > run on the target computer, which I got only a few minutes ago. > > The corresponding image is attached to this e-mail. > >> On Tue, 18 Sep 2018 at 08:24, gevisz wrote: > >>> Currently, I am prepairing to build Gentoo system on > >>> computer with AMD Athlon 64 X2 for computer with > >>> Intel Pentium Dual-Core E2160 SLA8Z Malay processor. > >>> > >>> What will be the correct march cflag for Intel Pentium > >>> Dual-Core E2160 SLA8Z Malay processor to set up in > >>> make.conf ? > >>> > >>> Am I right to use amd64 stage3 for Intel Pentium > >>> Dual-Core E2160 SLA8Z Malay processor? > >>> > >>> Thank you in advance. > > Unless I'm missing something, I'm surprised nobody has mentioned one > potential problem. Unless you are careful, code you compile for an AMD > may not run on an Intel. Thank you for your reply. I want to compile on AMD the code for Intel. If I did understand Gentoo manual correctly, it is possible if make.conf is set up correctly. > You should be able to come up with settings so compiled code will run > on either architecture No, I want to get Gentoo system optimized for the said Intel processor only.
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
ср, 19 сент. 2018 г. в 11:38, Walter Dnes : > > On Tue, Sep 18, 2018 at 10:22:30AM +0300, gevisz wrote > > > What will be the correct march cflag for Intel Pentium > > Dual-Core E2160 SLA8Z Malay processor to set up in > > make.conf ? > > If you have gcc *ON THE TARGET MACHINE*, execute the command... > > gcc -c -Q -march=native --help=target | grep march= > > ...to find out what "-march=native" yields. Unfortunately, currently, I don't have an access to the target computer. Can I use the output of lspci instead of the command above? I have just got it by e-mail and attached the corresponding image to one of my previous replies in this thread. > According to > http://www.cpu-world.com/sspec/SL/SLA8Z.html it has... > > MMX SSE SSE2 SSE3 SSSE3 Do you mean that it would be enough to set CFLAGS="-O2 -pipe mmx sse sse2 sse3 ssse3" without setting the march cflag at all? > > Am I right to use amd64 stage3 for Intel Pentium > > Dual-Core E2160 SLA8Z Malay processor? > > Yes... assuming you want 64-bit mode. Ok. Thank you for your reply.
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
On 9/19/18 5:45 PM, gevisz wrote: вт, 18 сент. 2018 г. в 22:44, George Kettleborough : If you can run gcc on the new system first you can find out what flags -march=native would produce and use those. See: https://blogs.gentoo.org/mgorny/2014/06/23/inlining-marchnative-for-distcc/ Thank you for the link. It would be useful if I had an access to the target computer and decided to set up distcc. May be I would. In the future. However, currently, I don't have access to the target computer and hope to get without such an access. Just with the full name of the processor and the output of lspci command run on the target computer, which I got only a few minutes ago. The corresponding image is attached to this e-mail. On Tue, 18 Sep 2018 at 08:24, gevisz wrote: Currently, I am prepairing to build Gentoo system on computer with AMD Athlon 64 X2 for computer with Intel Pentium Dual-Core E2160 SLA8Z Malay processor. What will be the correct march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor to set up in make.conf ? Am I right to use amd64 stage3 for Intel Pentium Dual-Core E2160 SLA8Z Malay processor? Thank you in advance. Unless I'm missing something, I'm surprised nobody has mentioned one potential problem. Unless you are careful, code you compile for an AMD may not run on an Intel. If you are just going to compile binary packages to move and install, this might be OK (assuming you don't trip over trying to run test during a build.) You should be able to come up with settings so compiled code will run on either architecture, but I have no idea what the side effects might be, such as larger and/or less efficient code. I almost wonder if this doesn't count as cross-compiling, even though it is not a totally incompatible architecture. Hopefully someone can either expand on this, or tell me why I'm barking up the wrong tree. Jack
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
ср, 19 сент. 2018 г. в 0:53, james : > > On 9/18/18 3:22 AM, gevisz wrote: > > Currently, I am prepairing to build Gentoo system on > > computer with AMD Athlon 64 X2 for computer with > > Intel Pentium Dual-Core E2160 SLA8Z Malay processor. > > > > What will be the correct march cflag for Intel Pentium > > Dual-Core E2160 SLA8Z Malay processor to set up in > > make.conf ? > > > > Am I right to use amd64 stage3 for Intel Pentium > > Dual-Core E2160 SLA8Z Malay processor? > > Once the system is 'boostrapped', you can run cpuinfo > and look at the flags listed therein. There are way less > gentoo flags one can set for a CPU, than what cpuinfo reveals. > Also some might not be a good idea to set; you have to ferret > out those details per your cpu(s). Thank you for your reply. Unfortunately, currently, I don't have an access to the target computer. Can I use the output of lspci instead of cpuinfo? I have just got it by e-mail and attached the corresponding image to my previous reply in this thread.
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
вт, 18 сент. 2018 г. в 22:44, George Kettleborough : > > If you can run gcc on the new system first you can find out what flags > -march=native would produce and use those. See: > https://blogs.gentoo.org/mgorny/2014/06/23/inlining-marchnative-for-distcc/ Thank you for the link. It would be useful if I had an access to the target computer and decided to set up distcc. May be I would. In the future. However, currently, I don't have access to the target computer and hope to get without such an access. Just with the full name of the processor and the output of lspci command run on the target computer, which I got only a few minutes ago. The corresponding image is attached to this e-mail. > On Tue, 18 Sep 2018 at 08:24, gevisz wrote: > > > > Currently, I am prepairing to build Gentoo system on > > computer with AMD Athlon 64 X2 for computer with > > Intel Pentium Dual-Core E2160 SLA8Z Malay processor. > > > > What will be the correct march cflag for Intel Pentium > > Dual-Core E2160 SLA8Z Malay processor to set up in > > make.conf ? > > > > Am I right to use amd64 stage3 for Intel Pentium > > Dual-Core E2160 SLA8Z Malay processor? > > > > Thank you in advance. > > >
Re: [gentoo-user] ACCESS DENIED
Ühel kenal päeval, K, 19.09.2018 kell 16:35, kirjutas Helmut Jarausch: > Hi, > I wonder what I am doing wrong. > For several packages, e.g. x11-terms/kitty-0.12.1 > I get access violations like > > * ACCESS DENIED: mkdir:/root/.config/kitty > > The cause of this is clear: emerge is running as user/group > 'portage' > but > ls -ld /root/.config > gives > drwx-- 15 root portage 4096 Sep 19 14:20 /root/.config > > One could change the permission of this folder, but there are > several applications which use this folder. > > What am I missing? kitty ebuild is missing a call to gnome_environment_reset, or at least xdg_environment_reset. If that is not done (and the ebuild isn't EAPI7 and something in the build ends up using XDG standards), then you could hit issues like this. Most often when you become root in a way that keeps user settings. To avoid this, you should consider using "su -" instead of "su" to become root; or the equivalent in case of other methods (though sudo by default does this and needs an extra argument to keep the env vars). However this is also technicall a bug in the ebuild, as discussed above, and such things should be tracked on bugzilla, if a particular packages case already isn't. Mart signature.asc Description: This is a digitally signed message part
[gentoo-user] ACCESS DENIED
Hi, I wonder what I am doing wrong. For several packages, e.g. x11-terms/kitty-0.12.1 I get access violations like * ACCESS DENIED: mkdir:/root/.config/kitty The cause of this is clear: emerge is running as user/group 'portage' but ls -ld /root/.config gives drwx-- 15 root portage 4096 Sep 19 14:20 /root/.config One could change the permission of this folder, but there are several applications which use this folder. What am I missing? Many thanks for a hint, Helmut
Re: [gentoo-user] wxPython/wxWidgets release number mismatch
Ühel kenal päeval, K, 19.09.2018 kell 08:58, kirjutas David Haller: > Hello, > > On Wed, 19 Sep 2018, Andrew Udvare wrote: > > Curiosity: what is the reason for wxGTK:3.0 and wxGTK:3.0-gtk3 ? > > wxGTK:3.0 uses gtk+-2 and wxGTK:3.0-gtk3 uses gtk+-3. That, and we couldn't do it with just flipping it to gtk3 in 3.0 SLOT, because some wxWidgets apps could be doing conditional direct GTK+ code as well, to go above the lowest common denominator toolkit support that wxWidgets provides. Or some might just be wrongly linking directly to gtk2 explicitly. Or had too much trouble with gtk3 in the less used parts of wxGTK while wxGTK gtk3 support hadn't quite matured yet. You can't have a program load in (link to) both gtk2 and gtk3 - it will abort to not go completely runtime crazy and crash due to same function names. Kind of like wxWidgets itself aborts if the library and app are using different C++ ABI (however that's less of a problem with todays relevant C++ ABI updates, unlike the gcc4 to 5 days). Therefore it was just a separate parallel installable SLOT with which we could move things over gradually and have the more maintained apps benefit before everything is working with it. Mart signature.asc Description: This is a digitally signed message part
Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
On Tue, Sep 18, 2018 at 10:22:30AM +0300, gevisz wrote > What will be the correct march cflag for Intel Pentium > Dual-Core E2160 SLA8Z Malay processor to set up in > make.conf ? If you have gcc *ON THE TARGET MACHINE*, execute the command... gcc -c -Q -march=native --help=target | grep march= ...to find out what "-march=native" yields. According to http://www.cpu-world.com/sspec/SL/SLA8Z.html it has... MMX SSE SSE2 SSE3 SSSE3 > Am I right to use amd64 stage3 for Intel Pentium > Dual-Core E2160 SLA8Z Malay processor? Yes... assuming you want 64-bit mode. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] wxPython/wxWidgets release number mismatch
Hello, On Wed, 19 Sep 2018, Andrew Udvare wrote: >Curiosity: what is the reason for wxGTK:3.0 and wxGTK:3.0-gtk3 ? wxGTK:3.0 uses gtk+-2 and wxGTK:3.0-gtk3 uses gtk+-3. HTH, -dnh -- The only "intuitive" interface is the nipple. After that, it's all learned. -- Bruce Ediger, bedi...@teal.csn.org, on X interfaces