[Mesa-users] Question-Mesa-installation-permission-issue

[Rob Farmer]

Hi,
So this is why we say don't use sudo. It makes a complete mess of things
and has likely left your mesa install in a mix of root/non-root files.

You don't need to make a new user to run without root privileges, any
command you run without sudo at the start will run with your normal user
privileges:

./install # Runs as a normal user
sudo ./install # Runs with elevated privileges.

So now we need to clean up the mess sudo left:

First delete $MESA_DIR as well as the sdk directory as both are now
possibly broken by using sudo. This is the only time to use sudo:
sudo rm -rf $MESA_DIR $MESASDK_ROOT

Then redownload MESA and the sdk and follow the steps for installing the
sdk (don't use sudo here). Then once the sdk is setup, follow the
instructions for installing MESA (again don't use sudo here).

Then let us know if you still have issues.

Again do not use sudo for any stage of installing mesa or the sdk.

Rob
p.s Don't use sudo to install mesa


On Thu, 5 Aug 2021 at 12:10, Nancy Kain <nancy.kain8890 at gmail.com> wrote:

> Hi,
> that's true, I was installing mesa using root. I'm new to linux / Ubuntu.
> Now I added a new non root user, even defined sudo user and used 'chmod
> u+rwx' and switched to it. I prepared mesasdk and mesa-r15140 in a
> directory inside my home directory.
>
> I still have 2 issues related to setting the environmental variables for
> SDK.
> The first one appears after I use ' source $MESASDK_ROOT/bin/mesasdk_init.sh
> '' (unsupported architecture),
> The second one  after ./install, As if i didn't install SDK, it's telling
> me to set the environmental variables even though i did that, probably
> related to the first error (unsupported architecture, mesa_init.sh)
>
> I even tried the svn tool and got the latest version of mesa, It even
> started the ./install but then stopped after a while with an error like
> '/home/NaNiNaNa/MESA48t/mesa-15140/utils
> ./build_and_test FAILED'
> A previous try gave similar error with another mesa dir than utils.
>
> I want to try a previous version of mesa (mesa-r12778 and
> mesasdk-x86_64-linux-20.3.2) but i do not think that would solve the
> problem since the initialization of SDK is facing the Checking architecture
> error already!
>
> I'll be thankful for any help!
>
> Best, Nancy
>
> On Tue, Aug 3, 2021 at 1:10 PM Rob Farmer <robert.j.farmer37 at gmail.com>
> wrote:
>
>> Hi,
>> You do not need to (and should not) install MESA with root privileges.
>> Simply calling ./install is sufficient. As you have both mesa and the sdk
>> in your home directory you can keep them there.
>>
>> Note MESA does not move files outside of MESA_DIR during installation
>> which is why it does not need to use root.
>>
>> Rob
>>
>> On Tue, 3 Aug 2021 at 12:10, Nancy Kain via Mesa-users <
>> mesa-users at lists.mesastar.org> wrote:
>>
>>> Hello,
>>>
>>> I am installing the latest version of MESA (mesa-r15140), using Ubuntu /
>>> Linux on my windows 10, so far I have prepared & extracted in my home
>>> directory the mesasdk-x86_64-linux-21.4.1, & mesa-r15140. As administrator.
>>> In a final step, in the $MESA_DIR, typing './install' gives me an error:
>>> ''Mesa should not be installed using root privileges, sudo is a bad idea
>>> to solve the problem. *Contact the mesa-users mailing-list if you have
>>> permission issues.* Or change the ./install file to avoid this check''
>>>
>>> So for ex. ''sudo apt-get install'' ...is not helping. & i don't know
>>> how to change the ./install file to allow the installation on a root
>>> location. So I should probably change some permissions settings to let the
>>> mesa install but what/ where exactly?
>>>
>>> I hope this is the right address for this question,
>>> Thank You in advance,
>>> NK
>>> _______________________________________________
>>> mesa-users at lists.mesastar.org
>>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20210805/5d76e698/attachment.htm>