July 2017 - Dev - Clearlinux.Org

by Sven Hartrumpf

Hi all. Does Clear Linux support running binaries for the x32 ABI? If I look at the following line # CONFIG_X86_X32 is not set in https://github.com/clearlinux-pkgs/linux-lts/blob/master/config , it seems to be disabled. For many applications, x32 clearly outperforms i386 and x86-64, e.g. (for functional programming): https://lists.gnu.org/archive/html/chicken-users/2015-09/msg00000.html https://sympa.inria.fr/sympa/arc/bigloo/2016-12/msg00015.html In the long run, also compiling x32 binaries could be an important performance option for Clear Linux. Ciao Sven

3 years

3
8
0 / 0

[PATCH clr-bundles] c-basic: handle library rename libgmpxx4 -> gmp-gmpxx

by Simental Magana, Marcos

on package gmp commit 0c79b74eaf426a036f899d8437fbfb896261d872, the subpackage libgmpxx4 was renamed to gmp-gmpxx, but change was not reflected in bundle definition in c-basic. This commit fixes the rename on the bundle side. Signed-off-by: Simental Magana, Marcos <marcos.simental.magana(a)intel.com> --- bundles/c-basic | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bundles/c-basic b/bundles/c-basic index 9b422ca..c6bb1d8 100644 --- a/bundles/c-basic +++ b/bundles/c-basic @@ -20,10 +20,10 @@ gcc-dev glibc-utils gmp-dev gmp-doc +gmp-gmpxx gmp-lib libc6-dev libc6-locale -libgmpxx4 libstdc++ libtool libtool-dev -- 2.13.3

4 years, 5 months

4
5
0 / 0

[PATCH clr-bundles] desktop: add the gkbd-keyboard-display utility.

by Simental Magana, Marcos

This commit enables the desktop to show the current keyboard layout by using gkbd-keyboard-display command. Signed-off-by: Simental Magana, Marcos <marcos.simental.magana(a)intel.com> --- When a user clicks the 'show keyboard layout' option, a pop-up notification shows an d error saying gkbd-keyboard-display command is unavailable. This patch fixes that, successfully showing a preview of the selected keyboard layout. bundles/desktop | 1 + 1 file changed, 1 insertion(+) diff --git a/bundles/desktop b/bundles/desktop index ff26085..4f2c16a 100644 --- a/bundles/desktop +++ b/bundles/desktop @@ -31,6 +31,7 @@ gtk3 ibus iso-codes json-glib +libgnomekbd libgweather libnotify librsvg -- 2.13.3

4 years, 6 months

1
1
0 / 0

Re: [Clr-dev] Clear containers and kubernetes guide

by Orozco, Geronimo

Hi Natalia, Could you try with the scenario posted in the guide (kubernetes 1.6) ? - Regards. On 7/6/17, 5:58 PM, "Dev on behalf of Marin Perez, Natalia" <dev-bounces(a)lists.clearlinux.org on behalf of natalia.marin.perez(a)intel.com> wrote: Hi guys, I'm currently trying the guide that you posted here: https://github.com/01org/cc-oci-runtime/wiki/Clear-Containers-and-Kuberne... and I'm having this error. root@ip-172-31-39-225:~/go/src/github.com/kubernetes-incubator/cri-o# make && make install go build -o crio \ -tags "selinux seccomp libdm_no_deferred_remove" \ github.com/kubernetes-incubator/cri-o/cmd/crio # github.com/kubernetes-incubator/cri-o/cmd/crio /usr/lib/go-1.8/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory Makefile:72: recipe for target 'crio' failed make: *** [crio] Error 2 Not sure if it's because I'm using Kubernetes version 1.7 instead of the 1.6 version that is being used in the guide or if it may probably be something else in my server configuration. Could you please provide some guidance on this? Thank you ! Best regards, Natalia Marín _______________________________________________ Dev mailing list Dev(a)lists.clearlinux.org https://lists.clearlinux.org/mailman/listinfo/dev

4 years, 6 months

2
1
0 / 0

Clear containers and kubernetes guide

by Marin Perez, Natalia

Hi guys, I'm currently trying the guide that you posted here: https://github.com/01org/cc-oci-runtime/wiki/Clear-Containers-and-Kuberne... and I'm having this error. root@ip-172-31-39-225:~/go/src/github.com/kubernetes-incubator/cri-o# make && make install go build -o crio \ -tags "selinux seccomp libdm_no_deferred_remove" \ github.com/kubernetes-incubator/cri-o/cmd/crio # github.com/kubernetes-incubator/cri-o/cmd/crio /usr/lib/go-1.8/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory Makefile:72: recipe for target 'crio' failed make: *** [crio] Error 2 Not sure if it's because I'm using Kubernetes version 1.7 instead of the 1.6 version that is being used in the guide or if it may probably be something else in my server configuration. Could you please provide some guidance on this? Thank you ! Best regards, Natalia Marín

4 years, 6 months

2
1
0 / 0

stateless + nsswitch.conf -> segfault

by Patrick Ohly

Hello! There's this patch for glibc in Clear Linux: https://raw.githubusercontent.com/clearlinux-pkgs/glibc/e54b638ef6b5f838e... It makes it possible to selectively override individual entries of the system default /usr/share/defaults/etc/nsswitch.conf in the (normally missing) /etc/nsswitch.conf. While testing the stateless patches I ran into a segfault related to nsswitch.conf. This can be reproduced like this: $ start_qemu.sh clear-16280-kvm.img ... root@clr-e2025fd6e74646a2a5101fda26464c73 ~ # touch /etc/nsswitch.conf root@clr-e2025fd6e74646a2a5101fda26464c73 ~ # id Segmentation fault (core dumped) strace shows that it aborts directly after reading nsswitch.conf: root@clr-e2025fd6e74646a2a5101fda26464c73 ~ # strace -e trace=open id open("/var/cache/ldconfig/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3</var/cache/ldconfig/ld.so.cache> ... open("/usr/share/locale/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3</etc/nsswitch.conf> open("/usr/share/defaults/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3</usr/share/defaults/etc/nsswitch.conf> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} --- +++ killed by SIGSEGV (core dumped) +++ Segmentation fault (core dumped) -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

4 years, 6 months

2
2
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

Dev July 2017