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/ > > > > > see > > > > > 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 . /opt/rh/devtoolset-9/enable before cd mozilla instead `source scl_source enable devtoolset-9` > -- 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
