How do you compile an application not as the ROOT user?[SOLVED]

[Jasper]

Hi all

I guess my title says it all

Occasionally, I come across an application that requires to be built not as the ROOT user.

I am using Fossapup64-95, can someone enlighten me?

TIA

[Sofiya]

Hi all

I guess my title says it all

Occasionally, I come across an application that requires to be built not as the ROOT user.

I am using Fossapup64-95, can someone enlighten me?

TIA

Code: Select all

run-as-spot chromium

Code: Select all

run-as-spot program name

[dimkr]

run-as-spot bash to get a shell running as spot, then proceed normally from there.

[mikewalsh]

run-as-spot bash to get a shell running as spot, then proceed normally from there.

Wouldn't you then run into the issue of linking to/against root-owned system files? Or does that not matter? (Me no expert when it comes to compiling, 'cos my "skills" are utterly abysmal in this area!)

Mike.

[Jasper]

@dimkr

Trying to compile a new update for BusyBox ....... that's an example of an application that requires one to compile not as the root user.

[Burunduk]

Trying to compile a new update for BusyBox ....... that's an example of an application that requires one to compile not as the root user.

This is a bit strange. I've recently compiled Busybox 1.36.1 on Fossapup64-9.5 as root without a problem.
Edit: Tried again, against GNU libc this time - OK. It's even easier - just make menuconfig and then make. It seems you've updated a lot of tools on your system, maybe this makes a difference.

[Jasper]

@Burunduk

Thank you as always for your input/suggestions lol and more often the solutions

I am going to have another attempt at this, not sure what I have missed. I will as suggested do menuconfig beforehand

The building tools I have updated but the core packages/libraries within Fossapup64-95 remain the same eg Python. This way hope updates will benefit other FP95 users. Unless I have uploaded an updated package ..... I do share them and add them as additional dependencies.

[dimkr]

run-as-spot bash to get a shell running as spot, then proceed normally from there.

Wouldn't you then run into the issue of linking to/against root-owned system files? Or does that not matter?

Yes, you'll link at libraries in /lib, /usr/lib, etc', and they may be root owned. But this doesn't matter, because spot has read permissions.

[mikewalsh]

run-as-spot bash to get a shell running as spot, then proceed normally from there.

Wouldn't you then run into the issue of linking to/against root-owned system files? Or does that not matter?

Yes, you'll link at libraries in /lib, /usr/lib, etc', and they may be root owned. But this doesn't matter, because spot has read permissions.

Fair comment! That's something new I've learned today. All "grist for t' mill". Thanks!

Mike.

[Jasper]

@Burunduk

Got it compile & working .............still unsure as to what I did wrong initially