Arve Barsnes wrote: > On Sun, 13 Feb 2022 at 09:43, Dale <rdalek1...@gmail.com> wrote: >> The following USE changes are necessary to proceed: >> (see "package.use" in the portage(5) man page for more details) >> # required by sci-libs/vtk-9.0.3-r4::gentoo[video_cards_nvidia] >> # required by sci-libs/opencascade-7.5.2-r5::gentoo[vtk] >> # required by sci-electronics/kicad-5.1.12-r2::gentoo[occ] >> # required by sci-electronics/kicad-packages3d-5.1.12-r1::gentoo >> # required by sci-electronics/kicad-meta-5.1.12::gentoo[-minimal] >> # required by @selected >> # required by @world (argument) >>> =x11-drivers/nvidia-drivers-470.103.01 static-libs >> Would you like to add these changes to your config files? [Yes/No] >> >> >> I'm not sure if the boost output is related or not. I did read >> somewhere that opencascade is replacing oce. From the above, I suspect >> vtk and/or opencascade is causing this. That may be related but dang if >> I can figure out a way around this. Anyone else run into this and find >> a fix or see something I'm missing? > I don't know how this would impact functionality, but it looks like > you could avoid this by setting USE on sci-libs/vtk to > "-video_cards_nvidia". The cuda USE flag requires this, but that is > already disabled for you. > > Regards, > Arve > >
Oh thank you for that hint. I thought that was coming from make.conf that I had a nvidia video card as opposed to a ATI or something. No idea I could disable it since it was just a USE flag. Changing that got me out of the static-libs USE flag demand. Now I'm having issues with hdf5 and flann. I think this is like the harfbuzz circle people run into. I ended up removing packages that are not absolutely needed in order to get it to give me a clean path. I plan to add those packages back to the world file once this emerge is done and see if it emerges those back without problems. In case someone else runs into this problem, even tho this thread wasn't exactly about this, this is what I had to remove from the world file. dev-libs/boost sci-electronics/kicad-meta media-gfx/digikam I suspect Kicad is not used by most but removing digikam seemed to be the one that opened the door to a clear path for emerge. That package is commonly used. So, that info may help if a person runs into this. I'm not sure what if any effect boost had. It may be worth not removing it unless others fail to give a clear path. Thanks again for the help. I saw it but didn't realize its meaning. You did. Dale :-) :-)