[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: HELP! What's up with OpenVDB?
From:       Sérgio Basto <sergio () serjux ! com>
Date:       2024-01-29 13:12:27
Message-ID: 8236deeede34dd898677f7bcb724a19b048f03c4.camel () serjux ! com
[Download RAW message or body]

On Sun, 2024-01-28 at 15:57 -0600, Richard Shaw wrote:
> On Sun, Jan 28, 2024 at 9:55 AM Ben Beasley <code@musicinmybrain.net>
> wrote:
> > Blender already excludes i686:
> > 
> > https://src.fedoraproject.org/rpms/blender/blob/8088da10c20e53ab0e1dd5de6fd3a2344bd288aa/f/blender.spec#_207
> >  
> > So does prusa-slicer:
> > 
> > https://src.fedoraproject.org/rpms/prusa-slicer/blob/44359e4b53c503cb61a60842abf991a01d1cb9db/f/prusa-slicer.spec#_68
> >  
> > Packages depending directly on openvdb are:
> > 
> > $ fedrq wrsrc -s openvdb
> > OpenImageIO-2.4.17.0-1.fc40.src
> > blender-1:4.0.2-1.fc40.src
> > luxcorerender-2.7-0.10.beta1.fc40.src
> > openvkl-2.0.0-5.fc40.src
> > prusa-slicer-2.4.2-13.fc40.src
> > usd-23.11-2.fc40.src
> > 
> > Of these, it looks like only OpenImageIO builds on i686. Packages 
> > depending on it are:
> > 
> > $ fedrq wrsrc -s OpenImageIO
> > OpenColorIO-2.2.1-6.fc40.src
> > blender-1:4.0.2-1.fc40.src
> > embree-4.3.0-2.fc40.src
> > luxcorerender-2.7-0.10.beta1.fc40.src
> > oidn-2.1.0-1.fc40.src
> > openshadinglanguage-1.12.14.0-9.fc40.src
> > usd-23.11-2.fc40.src
> > 
> > Of those, only OpenColorIO builds on i686. Packages depending on it
> > are:
> > 
> > $ fedrq wrsrc -s OpenColorIO
> > OpenImageIO-2.4.17.0-1.fc40.src
> > blender-1:4.0.2-1.fc40.src
> > calligra-3.2.1-25.fc39.src
> > krita-5.2.2-1.fc40.src
> > luxcorerender-2.7-0.10.beta1.fc40.src
> > usd-23.11-2.fc40.src
> > 
> > Of those, only calligra builds on i686, and it's a leaf package.
> > So, if 
> > I haven't missed anything, as long as i686 support is dropped from
> > all 
> > of calligra, OpenColorIO, OpenImageIO, and openvdb, then it should
> > be OK.
> > 
> 
> 
> Well I just re-tried openvdb with _smp_build_ncpus 1 and it still
> failed so I don't think we have a choice at this point. Perhaps it
> was hitting the 4GB max per process due to being 32bit?
> 

Have you try set  in build the ulimit [1] .
On copr, copr already set the max number of files already by default
[2] have you check if you can build it on copr ? 


[1]
%build 
ulimit -n 4096

[2]
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/copr/backend/files/provision/files/mock/site-defaults.cfg
 https://pagure.io/fedora-infra/ansible/blob/main/f/roles/copr/backend/files/provision/provision_builder_tasks.yml#_176-186



> Thanks,
> Richard
> --
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

-- 
Sérgio M. B.
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


[prev in list] [next in list] [prev in thread] [next in thread]