Why some flags of mesa are not installed?

unread,

Sep 10, 2022, 9:48:50 PM9/10/22

to ChromiumOS Development

Hello guys.

This is result of equery-amd64-generic uses media-lib/mesa, after build_packages --board=amd64-generic.

Some flags (classic, egl, gallium, gles2, shared-glapi) are set. But the flags are not installed.

Why does this happen?

unread,

Sep 13, 2022, 4:36:25 AM9/13/22

to ChromiumOS Development, Ted

Because ChromiumOS and amd64-generic-overlay in particular has been configured to build with these USE flags.

unread,

Oct 2, 2022, 12:30:34 AM10/2/22

to ChromiumOS Development, db...@google.com, Ted

Thank you for your reply.

I know that the flags (classic, egl, gallium, gles2, shared-glapi) are written in src/overlays/overlay-amd64-generic/profile/base/make.defaults .

But why Mesa is not being installed with the flags, when I do build_packages?

Could you guess what blocks the flags?

unread,

Oct 2, 2022, 1:42:53 AM10/2/22

to Ted, ChromiumOS Development

It should be. You should be able to check with "equery-amd64-generic uses mesa"

--

Dominik

unread,

Oct 2, 2022, 2:03:58 AM10/2/22

to ChromiumOS Development, db...@google.com, ChromiumOS Development, Ted

So what I am asking is the weird result of "equery-amd64-generic uses mesa".

Already I put the image above.

unread,

Oct 3, 2022, 7:00:15 PM10/3/22

to ChromiumOS Development, Ted, Dominik Behr, ChromiumOS Development

How are you determining that flags are "not installed"? Flags determine how package is built. Files are installed.

What do you see in /build/amd64-generic/var/db/pkg/media-libs/mesa*/CONTENTS and USE?

There should be selected mesa backends .so listed. And equivalent shared objects on the filesystem.

Reply all

Reply to author

Forward