As a temporary work around--link to code from non-standard directory to the 32-bit /usr/lib directory, for example:

if [[ $ARCH == *86 ]]; then
sudo find ${HOME}/lib32/ -name "libXvMC*" -type f -maxdepth 1 -exec bash -c 'ln -s "$0" /usr/lib/"${0##*/}"' {} \;
sudo find ${HOME}/lib32/ -name "libXvMC*" -type l -maxdepth 1 -exec bash -c 'ln -s "$0" /usr/lib/"${0##*/}"' {} \;
fi

Then delete links after compiling finishes:

sudo rm /usr/lib/libXvMC*

_____
Update: setting an rpath on 32-bit complied libXvMC* would still not let Meson find the libs.

Created attachment 144704 [details]
attachment-30153-0.html

I'm not at my computer right now (its a holiday here), but you might be
able to fix this by seeing -Dc_link_args="-L /path/with/xvmc"

I'm on mobile, please excuse autocorrect fail.

On Thu, Jul 4, 2019, 00:32 <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=110735#c1> on
> bug 110735 <https://bugs.freedesktop.org/show_bug.cgi?id=110735> from
> charlie <bug0xa3d2@hushmail.com> *
>
> As a temporary work around--link to code from non-standard directory to the
> 32-bit /usr/lib directory, for example:
>
> if [[ $ARCH == *86 ]]; then
> sudo find ${HOME}/lib32/ -name "libXvMC*" -type f -maxdepth 1 -exec bash -c 'ln
> -s "$0" /usr/lib/"${0##*/}"' {} \;
> sudo find ${HOME}/lib32/ -name "libXvMC*" -type l -maxdepth 1 -exec bash -c 'ln
> -s "$0" /usr/lib/"${0##*/}"' {} \;
> fi
>
> Then delete links after compiling finishes:
>
> sudo rm /usr/lib/libXvMC*
>
> _____
> Update: setting an rpath on 32-bit complied libXvMC* would still not let Meson
> find the libs.
>
> ------------------------------
> You are receiving this mail because:
>
>    - You are on the CC list for the bug.
>
>

I can wait.

Setting "-Dc_link_args" in a config file results in:
meson: error: unrecognized arguments: ..

So I set it in a meson crossfile like:
[properties]
c_link_args = ['-L /home/a/lib32']

Results in 'XvMCW not found'.

I also tried setting a native file (https://mesonbuild.com/Native-environments.html) mesa32.ini like:

[paths]
libdir = '/home/a/lib32'
prefix = '/home/a'

Still not found.

Created attachment 144713 [details]
attachment-31572-0.html

Ah, sorry. The -D version is for the command line, in the cross file it
would be :
c_link_args = ['-L', '/path']

I'm on mobile, please excuse autocorrect fail.

On Thu, Jul 4, 2019, 17:56 <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=110735#c3> on
> bug 110735 <https://bugs.freedesktop.org/show_bug.cgi?id=110735> from
> charlie <bug0xa3d2@hushmail.com> *
>
> I can wait.
>
> Setting "-Dc_link_args" in a config file results in:
> meson: error: unrecognized arguments: ..
>
> So I set it in a meson crossfile like:
> [properties]
> c_link_args = ['-L /home/a/lib32']
>
> Results in 'XvMCW not found'.
>
> I also tried setting a native file
> (https://mesonbuild.com/Native-environments.html) mesa32.ini like:
>
> [paths]
> libdir = '/home/a/lib32'
> prefix = '/home/a'
>
> Still not found.
>
> ------------------------------
> You are receiving this mail because:
>
>    - You are on the CC list for the bug.
>
>

In a crossfile, setting like:

c_link_args = ['-L', '/home/a/lib']

terminates meson configuring earlier and results in a new error:

meson.build:1114:2: ERROR: C library 'dl' not found

Thanks for your time.

I started thinking about this over the weekend, and realized that all of this work-arounding a lack of a .pc file for libxvmcw is silly, we should just add a pkg-config file so this is less painful:
https://gitlab.freedesktop.org/xorg/lib/libxvmc/merge_requests/2

I recompiled both 32-bit and 64-bit libXvMC with the patch applied and mesa meson configure error remains.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/939.