devel June 2018

devel@lists.centos.org

35 participants
33 discussions

Untag golang-1.9.4 from Centos PaaS Sig 3.7 Candidate Repo
by Scott Dodson 04 Jun '18

04 Jun '18

Our CI team makes use of the centos paas sig repos and they've noticed that we've got golang-1.9 tagged into the 3.7 repo where as Origin 3.7 should be built with golang 1.8. Can we get golang-1.9.2-4.el7 untagged from paas7-openshift-origin37-candidate ?

1 0

docker and podman packages should be part of virt7-container-common-candidate or extra repos.
by Praveen Kumar 04 Jun '18

04 Jun '18

Hi, I can see docker packages are part of virt7-container-common-candidate[0] and also extra[1] repo same with podman but on the virt repo side docker packages are not updated to latest version and for podman extra repo doesn't have latest packages. It becomes really confusing what repo to chose when installing those packages and if we include both repos then there is conflict:( [0] https://cbs.centos.org/repos/virt7-container-common-candidate/x86_64/os/Pac… [1] http://mirror.centos.org/centos/7/extras/x86_64/Packages/ ``` Transaction couldn't start: 10:06:29 file /usr/libexec/cni/bridge conflicts between attempted installs of containernetworking-plugins-0.7.0-4.gitb51d327.el7.x86_64 and containernetworking-cni-0.6.0-4.el7.x86_64 10:06:29 file /usr/libexec/cni/dhcp conflicts between attempted installs of containernetworking-plugins-0.7.0-4.gitb51d327.el7.x86_64 and containernetworking-cni-0.6.0-4.el7.x86_64 ``` -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com

1 0

__gthrw___pthread_key_create in devtoolset-6
by dacav 01 Jun '18

01 Jun '18

Hello good people I'm packaging for CentOS 7 a piece of proprietary software. The software is written in C++14, so I need to use the devtoolset to run it. Unfortunately I'm having some issues with linking of pthreads. First off I'm getting this warning: In file included from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/x86_64-redhat-linux/bits/gthr.h:148:0, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/ext/atomicity.h:35, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/bits/ios_base.h:39, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/ios:42, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/ostream:38, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/iostream:39, from src/logd-main.cpp:23: /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/x86_64-redhat-linux/bits/gthr-default.h:236:10: warning: 'int __gthrw___pthread_key_create(pthread_key_t*, void (*)(void*)) throw ()' used but never defined __gthrw2(__gthrw_(__pthread_key_create), …Where the problematic line is a `#include <iostream>`. Then of course it gets problematic upon linking time objs/intel-debug/src/logd-main.o:(.rodata+0x8): undefined reference to `__gthrw___pthread_key_create(unsigned int*, void (*)(void*))' collect2: error: ld returned 1 exit status I searched around on the Web: the classic suggestion (from stackoverflow and such) will be to check for the `-pthread` flag to be present at compilation. This is of course tackled already. Since the compilation is working in other contexts, I started to wonder if this is some known problem in CentOS + Devtoolset: did someone have similar issues? Perhaps there's something wrong in how I do the build. Is there in CentOS some software which is using Devtoolset which I could take as example for my build? Thanks in advance for any suggestion :)

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2018