Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 676884 - Cannot emerge mesa with VIDEO_CARDS="r100"
Summary: Cannot emerge mesa with VIDEO_CARDS="r100"
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-30 02:37 UTC by Laszlo
Modified: 2019-01-31 20:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info output (emergeinfo.txt,5.72 KB, text/plain)
2019-01-30 02:37 UTC, Laszlo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Laszlo 2019-01-30 02:37:14 UTC
Created attachment 563254 [details]
emerge --info output

Emerging mesa with VIDEO_CARDS="r100" produces the portage error message:

!!! Problem resolving dependencies for media-libs/mesa
... done!

!!! The ebuild selected to satisfy "mesa" has unmet requirements.
- media-libs/mesa-18.2.8::gentoo USE="classic d3d9 dri3 egl gallium gbm -debug -gles1 -gles2 -llvm -lm_sensors -opencl -osmesa -pax_kernel -pic (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan -wayland -xa -xvmc" VIDEO_CARDS="r100 (-freedreno) -i915 -i965 (-imx) -intel -nouveau -r200 -r300 -r600 -radeon -radeonsi (-vc4) -virgl (-vivante) -vmware"

  The following REQUIRED_USE flag constraints are unsatisfied:
    d3d9? ( any-of ( video_cards_r300 video_cards_r600 video_cards_radeonsi video_cards_nouveau video_cards_vmware ) )

  The above constraints are a subset of the following complete expression:
    d3d9? ( dri3 any-of ( video_cards_r300 video_cards_r600 video_cards_radeonsi video_cards_nouveau video_cards_vmware ) ) gles1? ( egl ) gles2? ( egl ) vulkan? ( dri3 any-of ( video_cards_i965 video_cards_radeonsi ) video_cards_radeonsi? ( llvm ) ) wayland? ( egl gbm ) video_cards_freedreno? ( gallium ) video_cards_intel? ( classic ) video_cards_i915? ( any-of ( classic gallium ) ) video_cards_i965? ( classic ) video_cards_imx? ( gallium video_cards_vivante ) video_cards_nouveau? ( any-of ( classic gallium ) ) video_cards_radeon? ( any-of ( classic gallium ) gallium? ( x86? ( llvm ) amd64? ( llvm ) ) ) video_cards_r100? ( classic ) video_cards_r200? ( classic ) video_cards_r300? ( gallium x86? ( llvm ) amd64? ( llvm ) ) video_cards_r600? ( gallium ) video_cards_radeonsi? ( gallium llvm ) video_cards_vc4? ( gallium ) video_cards_virgl? ( gallium ) video_cards_vivante? ( gallium gbm ) video_cards_vmware? ( gallium )
Comment 1 Brian Evans (RETIRED) gentoo-dev 2019-01-30 02:43:53 UTC
(In reply to laszlo.erdoes from comment #0)
> Created attachment 563254 [details]
> emerge --info output
> 
> Emerging mesa with VIDEO_CARDS="r100" produces the portage error message:
> 
> !!! Problem resolving dependencies for media-libs/mesa
> ... done!
> 
> !!! The ebuild selected to satisfy "mesa" has unmet requirements.
> - media-libs/mesa-18.2.8::gentoo USE="classic d3d9 dri3 egl gallium gbm
> -debug -gles1 -gles2 -llvm -lm_sensors -opencl -osmesa -pax_kernel -pic
> (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan -wayland -xa -xvmc"
> VIDEO_CARDS="r100 (-freedreno) -i915 -i965 (-imx) -intel -nouveau -r200
> -r300 -r600 -radeon -radeonsi (-vc4) -virgl (-vivante) -vmware"
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     d3d9? ( any-of ( video_cards_r300 video_cards_r600 video_cards_radeonsi
> video_cards_nouveau video_cards_vmware ) )

This says if the d3d9 USE is enabled, one of the other listed video_cards flags must also be enabled.  So if you just have r100, you'll have to disable d3d9
Comment 2 Laszlo 2019-01-30 03:23:25 UTC
(In reply to Brian Evans from comment #1)

> This says if the d3d9 USE is enabled, one of the other listed video_cards
> flags must also be enabled.  So if you just have r100, you'll have to
> disable d3d9

I tried disabling d3d9 using use flags for mesa, but it doesn't seem to work - it still tries to build with that flag enabled. I'm not sure why.
Could it be because I also have wine installed on the system?
Comment 3 Matt Turner gentoo-dev 2019-01-30 07:06:41 UTC
(In reply to laszlo.erdoes from comment #2)
> (In reply to Brian Evans from comment #1)
> 
> > This says if the d3d9 USE is enabled, one of the other listed video_cards
> > flags must also be enabled.  So if you just have r100, you'll have to
> > disable d3d9
> 
> I tried disabling d3d9 using use flags for mesa, but it doesn't seem to work
> - it still tries to build with that flag enabled. I'm not sure why.
> Could it be because I also have wine installed on the system?

No, it doesn't have anything to do with wine being installed on your systme. d3d9 is not enabled by default, so you must have enabled it. Also r100 is not a gallium driver, so you can save yourself some time by disabling that as well.
Comment 4 Laszlo 2019-01-30 22:25:38 UTC
I made a file:
/etc/portage/package.use/mesa
With this content:
media-libs/mesa -egl -dri3 -gbm -llvm -d3d9

Even after this, the d3d9 use flag stays enabled when I try to emerge the mesa package (and it fails with the same error as before).
Comment 5 Brian Evans (RETIRED) gentoo-dev 2019-01-30 23:22:22 UTC
(In reply to laszlo.erdoes from comment #4)
> I made a file:
> /etc/portage/package.use/mesa
> With this content:
> media-libs/mesa -egl -dri3 -gbm -llvm -d3d9
> 
> Even after this, the d3d9 use flag stays enabled when I try to emerge the
> mesa package (and it fails with the same error as before).

You should look through *all* files in /etc/portage/package.use .  A file that comes after mesa alphabetically is most likely re-enabling d3d9.

Portage does not care what the files are named.  It simply reads them collectively in alpha order.
Comment 6 Laszlo 2019-01-31 20:11:04 UTC
I found the issue, it was an entry in the autounmask file originally set by wine. Thanks for the help.