Re: Devtoolset for epel7 for build in Copr

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2022-02-25 at 02:43 +0300, Dmitry Butskoy wrote:
> Sérgio Basto wrote:
> > On Thu, 2022-02-24 at 21:20 +0300, Dmitry Butskoy wrote:
> > > Miroslav Suchý wrote:
> > > > > Second, the alternate Springdale Linux repo
> > > > > http://springdale.princeton.edu/data/springdale/SCL/7/x86_64/ s
> > > > > ee
> > > > > ms
> > > > > to have all the ones (which are provided in sources by RedHat),
> > > > > but
> > > > > cannot be used in Copr. Springdale provides devtoolset-3-
> > > > > elfutils
> > > > > there, and it in some strange way  badly correlates with the
> > > > > initial
> > > > > Copr build environment (even before the rpmbuild process
> > > > > starts).
> > > > > Some python2 module cannot find libelf.so.1 ...
> > > > 
> > > > That is because it is SCL package. It installs the library to
> > > > 
> > > > /opt/rh/devtoolset-3/root/usr/lib64/libelf.so.1
> > > > 
> > > > You have to run
> > > > 
> > > >    scl enable devtools-3 $COMMAND
> > > > 
> > > But where to run it exactly?
> > > 
> > yes is not easy find an example unfortunately , first line of %build
> 
> %build is in the .spec file. It is readed after the start of the build.
> The start of the build is performed after the "bootstrap" stage. At
> this 
> stage "yum install" creates an initial environment. Probably I'm wrong 
> -- 

Sorry this thread have different topics, after reading it . 

 libelf.so.1: cannot open shared object file: No such file , should we
a mixup of devtools set , you just can Buildrequires one devtool set 

Second llvm-toolset-11.0 is only available on RedHat EL 7 , that is why
koji builds seamonkey which uses RHEL 7 and copr  don't, it uses Centos
7

Third, search on goggle I found that is also available on Scientific
Linux 7
http://rpm.pbone.net/results_srodzaj_1_search_libLLVM-11.so%28%29%2864bit%29.html


> could you pls look at:
> > Start: yum install
> > There was a problem importing one of the Python modules
> > required to run yum. The error leading to this problem was:
> > 
> >     libelf.so.1: cannot open shared object file: No such file or
> > directory
> fragment in the correspond log: 
> https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-7-x86_64/03543870-seamonkey/builder-live.log.gz
>  
> ?
> 
> IOW: there is no "yum install" in the .spec file. So where to run 
> "scl-enable ..." to take it effect before that "yum install" ?
> 
> 
> ~buc
> 
> 
> 
> 
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

-- 
Sérgio M. B.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux