devel

devel@lists.centos.org

10 participants
4617 discussions

GCC 4.8 vs -fsanitize
by Fred Smith 04 Aug '14

04 Aug '14

I've been anxiously awaiting a system containing GCC 4.8.x so I could try the new -fsanitize=address and -fsanitize=thread tools on my project. imagine my dismay when I finally have time to try it on C7 and find that it rejects the -fsanitize option. It doesn't appear to have been enabled when the shipped GCC was built. :( Do I have any choices other than compiling my own GCC ?? Thanks! -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

2 3

don't use centos 7 as a developer workstation
by Farkas Levente 04 Aug '14

04 Aug '14

Hi, May be it's not clear to everyone.. so this's just a quick notice to everyone. Don't use CentOS 7 as a developer workstation since currently there is not included any developer IDE. As eclipse was pulled out from the main distro and put into Red Hat Developer Toolset (which is imho a good idea not to use a 7 years old IDE). But Red Hat Developer Toolset is still not supported on rhel7 this means currently you have to install eclipse and all other packages from RHDT. Anyway RH said it will be supported... Regards. -- Levente "Si vis pacem para bellum!"

6 6

RFC: Alternative Desktop SIG
by Stephen John Smoogen 01 Aug '14

01 Aug '14

I would like to put together an alternative desktop sig which will build, qa, and support desktops which are not the Enterprise Linux primary or secondary desktops (GNOME and KDE). There are a couple of ground rules I would like to propose: 1) Any desktop system needs to have 3 sponsors who are people willing to do the work of building RPMS, coordinating user bugs with upstream, and fixing packages. The reason for 3 is a) that this SIG isn't a dumping ground for here is ABC-DE compiled, goodbye. b) that disagreements between sponsors should be deadlock free. c) that when people take vacations, etc there is continuity of operation. 2) Desktops do not keep to Enterprise lifetimes, but major version changes to the desktop need to be announced, tested and released to a schedule. Desktops which don't want to do that will not be part of the SIG. [A schedule does not need to be super detailed, but just alleviate surprise.] 3) Desktops can and will be removed from the SIG if there isn't an interest in keeping them up. This is mainly to cover that if ABC-DE desktop no longer has sponsors, other members of the SIG aren't obliged to support ABC-DE if they don't want to. 4) Some level of governance needs to be established so that there is a committee that can make sure that a desktop has 'sponsors', that it is not just code thrown over a wall and left, and that users are not left surprised when updates to the desktop occur. They may also make up packaging rules and guidelines as needed to alleviate problems that come up. As this is an RFC, these are just proposed rules to be solidified when the CentOS board considers the SIG. -- Stephen J Smoogen.

9 27

Cannot recompile CentOS 7 perl srpms from Vault because built files end up in unexpected dirs
by Lars Holowko 01 Aug '14

01 Aug '14

Hi there, I am trying to recompile http://vault.centos.org/7.0.1406/os/Source/SPackages/rrdtool-1.4.8-8.el7.sr… to also get the rrdtool-perl sub package for which there are no binaries provided. But when it tries to build the perl sub module it fails with: writing /root/rpmbuild/BUILDROOT/rrdtool-1.4.8-8.el7.centos.x86_64/usr/lib64/python2.7/site-packages/py_rrdtool-0.2.2-py2.7.egg-info make[3]: Leaving directory `/root/rpmbuild/BUILD/rrdtool-1.4.8/bindings' make[2]: Leaving directory `/root/rpmbuild/BUILD/rrdtool-1.4.8/bindings' make[1]: Leaving directory `/root/rpmbuild/BUILD/rrdtool-1.4.8/bindings' make[1]: Entering directory `/root/rpmbuild/BUILD/rrdtool-1.4.8' make[2]: Entering directory `/root/rpmbuild/BUILD/rrdtool-1.4.8' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/rpmbuild/BUILD/rrdtool-1.4.8' make[1]: Leaving directory `/root/rpmbuild/BUILD/rrdtool-1.4.8' + /usr/bin/install -D -m0755 php4/modules/rrdtool.so /root/rpmbuild/BUILDROOT/rrdtool-1.4.8-8.el7.centos.x86_64/usr/lib64/php/modules/rrdtool.so + /usr/bin/rm -rf php4/examples/.svn + /usr/bin/mkdir -p /root/rpmbuild/BUILDROOT/rrdtool-1.4.8-8.el7.centos.x86_64/etc/php.d + /usr/bin/cat + /usr/bin/mv /root/rpmbuild/BUILDROOT/rrdtool-1.4.8-8.el7.centos.x86_64/usr/share/perl5/vendor_perl/RRDp.pm /root/rpmbuild/BUILDROOT/rrdtool-1.4.8-8.el7.centos.x86_64/usr/lib64/perl5/vendor_perl/ /usr/bin/mv: cannot stat ‘/root/rpmbuild/BUILDROOT/rrdtool-1.4.8-8.el7.centos.x86_64/usr/share/perl5/vendor_perl/RRDp.pm’: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.t4Flhd (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.t4Flhd (%install) [root@larsbuild7 ~]# I get the similar errors (files getting copied in the wrong directories during build time) with other perl srpms. e.g. http://vault.centos.org/7.0.1406/os/Source/SPackages/perl-Data-Dumper-2.145… rpmbuild -ba rpm/SPECS/perl-Data-Dumper.spec Executing(%prep): /bin/sh -e /home/lars/rpm/tmp/rpm-tmp.pLTYSe + umask 022 + cd /home/lars/rpm/BUILD + cd /home/lars/rpm/BUILD + rm -rf Data-Dumper-2.145 + /usr/bin/gzip -dc /home/lars/rpm/SOURCES/Data-Dumper-2.145.tar.gz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd Data-Dumper-2.145 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + sed -i /MAN3PODS/d Makefile.PL + exit 0 Executing(%build): /bin/sh -e /home/lars/rpm/tmp/rpm-tmp.66tgMG + umask 022 + cd /home/lars/rpm/BUILD + cd Data-Dumper-2.145 + perl Makefile.PL INSTALLDIRS=vendor 'OPTIMIZE=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' Checking if your kit is complete... Looks good Writing Makefile for Data::Dumper Writing MYMETA.yml and MYMETA.json + make -j12 /usr/bin/perl /usr/share/perl5/vendor_perl/ExtUtils/xsubpp -typemap /usr/share/perl5/ExtUtils/typemap Dumper.xs > Dumper.xsc && mv Dumper.xsc Dumper.c Running Mkbootstrap for Data::Dumper () chmod 644 Dumper.bs cp Dumper.bs blib/arch/auto/Data/Dumper/Dumper.bs chmod 644 blib/arch/auto/Data/Dumper/Dumper.bs cp Dumper.pm blib/lib/Data/Dumper.pm gcc -c -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -DVERSION=\"2.145\" -DXS_VERSION=\"2.145\" -fPIC "-I/usr/lib64/perl5/CORE" -DUSE_PPPORT_H Dumper.c rm -f blib/arch/auto/Data/Dumper/Dumper.so gcc -shared -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -Wl,-z,relro Dumper.o -o blib/arch/auto/Data/Dumper/Dumper.so \ \ chmod 755 blib/arch/auto/Data/Dumper/Dumper.so Manifying blib/man3/Data::Dumper.3pm + exit 0 Executing(%install): /bin/sh -e /home/lars/rpm/tmp/rpm-tmp.Ltvukd + umask 022 + cd /home/lars/rpm/BUILD + '[' /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 '!=' / ']' + rm -rf /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 ++ dirname /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 + mkdir -p /home/lars/rpm/BUILDROOT + mkdir /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 + cd Data-Dumper-2.145 + make pure_install DESTDIR=/home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/home/lars/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Data/Dumper/Dumper.bs Installing /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/home/lars/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Data/Dumper/Dumper.so Installing /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/home/lars/perl5/lib/perl5/x86_64-linux-thread-multi/Data/Dumper.pm Installing /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/home/lars/perl5/man/man3/Data::Dumper.3pm + find /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 -type f -name .packlist -exec rm -f '{}' ';' + find /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64 -type f -name '*.bs' -size 0 -exec rm -f '{}' ';' + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/home + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /home/lars/rpm/BUILD/Data-Dumper-2.145 extracting debug info from /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/home/lars/perl5/lib/perl5/x86_64-linux-thread-multi/auto/Data/Dumper/Dumper.so dwz: Too few files for multifile optimization /usr/lib/rpm/sepdebugcrcfix: Updated 1 CRC32s, 0 CRC32s did match. 161 blocks + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Executing(%check): /bin/sh -e /home/lars/rpm/tmp/rpm-tmp.mwbkfM + umask 022 + cd /home/lars/rpm/BUILD + cd Data-Dumper-2.145 + make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/bless.t ..................... ok t/bless_var_method.t .......... ok t/bugs.t ...................... ok t/deparse.t ................... ok t/dumper.t .................... ok t/dumpperl.t .................. ok t/freezer.t ................... ok t/freezer_useperl.t ........... ok t/indent.t .................... ok t/misc.t ...................... ok t/names.t ..................... ok t/overload.t .................. ok t/pair.t ...................... ok t/perl-74170.t ................ ok t/purity_deepcopy_maxdepth.t .. ok t/qr.t ........................ ok t/quotekeys.t ................. ok t/seen.t ...................... ok t/sortkeys.t .................. ok t/sparseseen.t ................ ok t/terse.t ..................... ok t/toaster.t ................... ok t/values.t .................... ok All tests successful. Files=23, Tests=647, 1 wallclock secs ( 0.12 usr 0.02 sys + 0.76 cusr 0.08 csys = 0.98 CPU) Result: PASS + exit 0 Processing files: perl-Data-Dumper-2.145-3.el7.centos.x86_64 error: File not found by glob: /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/lib64/perl5/vendor_perl/auto/* error: File not found by glob: /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/lib64/perl5/vendor_perl/Data* error: File not found by glob: /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/share/man/man3/* Executing(%doc): /bin/sh -e /home/lars/rpm/tmp/rpm-tmp.TkASco + umask 022 + cd /home/lars/rpm/BUILD + cd Data-Dumper-2.145 + DOCDIR=/home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/share/doc/perl-Data-Dumper-2.145 + export DOCDIR + /usr/bin/mkdir -p /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/share/doc/perl-Data-Dumper-2.145 + cp -pr Changes /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/share/doc/perl-Data-Dumper-2.145 + cp -pr Todo /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/share/doc/perl-Data-Dumper-2.145 + exit 0 RPM build errors: File not found by glob: /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/lib64/perl5/vendor_perl/auto/* File not found by glob: /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/lib64/perl5/vendor_perl/Data* File not found by glob: /home/lars/rpm/BUILDROOT/perl-Data-Dumper-2.145-3.el7.centos.x86_64/usr/share/man/man3/* [lars@larsbuild7 ~]$ My root user has no .rpmmacros file at all, the lars user has a trivial one: [lars@larsbuild7 ~]$ cat .rpmmacros %_topdir /home/lars/rpm %_tmppath /home/lars/rpm/tmp %_rpmlock_path /home/lars/rpm/locks/transaction %_signature gpg %define debug_package %{nil} %define __os_install_post %{nil} %_rpmlock_path /home/lars/.mk-externals.tmp/transaction [lars@larsbuild7 ~] I assume I have to set some rpm variables like %perlvendor%, %perlarch% or so. Any hint? Thanks a lot, Lars

3 3

Koji workflow / git branches
by Thomas Oulevey 30 Jul '14

30 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folks, Few questions/points about the Koji git workflow. * We have different way to build RPMs in Koji 1/ From source rpm ; you can build any source RPM you submit to the system. e.g: koji build storage7-el7 myNVR.src.rpm 2/ From git ; you send koji an URL + #commit e.g: koji build storage7-el7 "git+https://git.centos.org/git/rpms/tzdata.git?#e24d98" (For that I need to patch kojid so it supports git.c.o schema i.e not having a .spec file directly at / in git) The proposal is to have both solutions supported but : - - Building from src.rpm will be only trigger by git.c.o and will require special permission. - - SIG users can build their packages but the code need to be in git.c.o (traceability). What do you think ? Is there a use case where building from src.rpm would be required ? * Now speaking about the SIG what is the plan for the branches naming ? c${MAJOR}-${SIGNAME} ? I will need to generate this string to checkout the correct branch in git. Thanks to Fabian the koji installation is being puppetized, and we hope to have some SIG beta-users on board soon. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT15qzAAoJEH2Wn86OP8NiPGEH/1GF+kjYMl82cfBljKY6bUcC omwb487THg1uVFMhHA0TqL4lQ0IZphBp1TLiqNWmnI742r497s1BnQJQWKTWD4M2 l2EZ6QulB9NV9os8idfFbfCrW5KuxT7J++Olg+49ARPrnlE8v5qOJkBY5DdjvCh5 tXP5HwrIUnroDFECSY0GiWa5pPAztjVS1pQUFOhE4MG0A+f9ZaJ0lMOi4Pkbnd7n nmml5Et0zozHeSDK7L+gwDaEtutro9hjE580nV0PxjGmIeIlDlT2WSDOtCJ8YcfX MBiXK5P7payoeYSTmzsw7QhcAjnqIQH+PRavus6oodlR9+bsUlALjz3kh42q6Po= =PKiV -----END PGP SIGNATURE-----

3 3

Brightbox CentOS 7 cloud kickstart
by Neil Wilson 29 Jul '14

29 Jul '14

Hi all, Brightbox has announced the availability of public CentOS 7 cloud images today including cloud-init, etc [1] As part of that I’ve pushed the kickstart files and build scripts to the Brightbox Bootstaller archive [2]. These as the files that are used to build the public images. They are as good as they are because of the valued work of the people around here and at Fedora. Any errors are mine alone. I hope you find them useful. [1] http://brightbox.com/blog/2014/07/29/centos-7-cloud-images/ [2] https://github.com/brightbox/bootstaller — Neil Wilson

1 0

Centos6.4 ISO: extract, modify files and rebuild
by Raghuv Adhepalli 28 Jul '14

28 Jul '14

Hi, When I was looking inside the centos6.4 iso, I found a file kickstart.py that interests me and would like to hack around a bit. So far I have been able to mount the centos iso and the image file "install.img" (present inside the iso) as loop devices. I was able to copy all contents of install.img to another directory(as the loop device is a read-only filesystem) and make changes to the kickstart.py file Now I am not sure how to rebuild the img file and then the iso. Is there any documentation in the community for this very purpose of extracting, making changes and rebuilding the centos iso? Thanks, Raghuv Adhepalli.

1 0

Centos6.4 ISO: extract, modify files and rebuild
by Raghuv Adhepalli 28 Jul '14

28 Jul '14

1 0

CentOS 7 cloud image with cloud-init
by Tim Bell 28 Jul '14

28 Jul '14

Looking at http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7.0-1406-x86_64-E…, is there a cloud image later than June 2014 ? With the release in July, it would be great to test out a cloud-init enabled image on CentOS 7. Thanks Tim

1 0

CentOS Atomic Host SIG Proposal
by Joe Brockmeier 28 Jul '14

28 Jul '14

Hi all, Please see the proposal below and let me know if you have any suggestions, are interested in being involved, or any other comments, thoughts, or flames. ================================================================ Atomic Host SIG The CentOS Atomic Host SIG will work on a CentOS-based Atomic Host image that provides a minimal image using rpm-ostree, as well as tools and documentation for users to create their own CentOS/Atomic images with custom package sets. ## Goals * Ship a minimal CentOS Atomic Host that focuses on running Docker containers in production. * Provide ISO images installable with Anacona, and images suited for OpenStack, CloudStack, Amazon Web Services/Eucalyptus, and Google Compute Engine. * Provide tools and documentation that can be used to spin custom images from CentOS packages to be deployed with Atomic (rpm-ostree) tools. * Provide regular releases as underlying tools (e.g. rpm-ostree) advance, while maintaining stability for in-place upgrades. * Establish a time-based release cadence. * All code included in the Atomic image will be under an OSI-approved license. * Unless differentation is absolutely necessary, all packages common to CentOS core and CentOS Atomic will be identical. ## Mailing List and Communication Work for the CentOS Atomic image relevant to CentOS build systems, etc. will take place on centos-devel. Work related to upstream Atomic will take place on the Atomic mailing lists. Note that the Atomic community comprises efforts underway with CentOS, Fedora, and Red Hat Enterprise Linux, as well as upstreams like Docker and OpenShift (GearD) so discussions may span several communities and mailing lists. ## SIG Membership The Atomic Host SIG will have a steering committee and committers. The steering committee will consist initially of Joe Brockmeier, Jason Brooks, Jim Perrin, Brian Proffitt, Greg DeKoenigsberg, and _________ (?). New committers and steering committee members are appointed by the steering committee. Committer privileges, once earned, do not expire unless revoked by the steering committee. The steering committee will appoint a chair to interface with the CentOS Board. ## Meetings The CentOS Atomic SIG will initially meet weekly until all pieces are in place for regular releases, then as needed. ## Roadmap and (Action) TODO List * Define package set * Establish builds for target environments (cloud deployments and bare metal) * Define orchestration tool(s) for CentOS Atomic * Establish test / QA processes * Set long-term release cadence, upgrade policies ## Further Info * Project Atomic (http://projectatomic.io) * Fedora Atomic Initiative (http://rpm-ostree.cloud.fedoraproject.org/#/) ================================================================ Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

4 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel