Return to Question

I recently installed LAME encoder on my server to convert wav to mp3 and that worked with './configure, make, make install;

I then tried to install OGG encoder and that requires './configure, make, sudo make install' - which I cannot do, since I don't have a VPS (and I'd rather not pay $15 a month for a VPN just to install a codec).

I'm new to all this, and I understand sudo gives you permissions - but I have been trying to find out why exactly some 'make installs' require sudo access and others dont. I haven't yet found the answer. Again, very knew to this so I'm just trying to learn what's going on.

I recently installed LAME encoder on my server to convert wav to mp3 and that worked with ./configure; make; make install.

I then tried to install OGG encoder and that requires './configure, make, sudo make install' - which I cannot do, since I don't have a VPS (and I'd rather not pay $15 a month for a VPN just to install a codec).

I'm new to all this, and I understand sudo gives you permissions - but I have been trying to find out why exactly some make installs require sudo access and others don't. I haven't yet found the answer.

I recently installed LAME encoder on my server to convert wav to mp3 and that worked with './configure, make, make install;

I then tried to install OGG encoder and that requires './configure, make, sudo make install' - which I cannot do, since I don't have a VPS (and I'd rather not pay $15 a month for a VPN just to install a codec).

I'm new to all this, and I understand sudo gives you permissions - but I have been trying to find out why exactly some 'make installs' require sudo access and others dont. I haven't yet found the answer. Again, very knew to this so I'm just trying to learn whats going on.

I recently installed LAME encoder on my server to convert wav to mp3 and that worked with './configure, make, make install;

I then tried to install OGG encoder and that requires './configure, make, sudo make install' - which I cannot do, since I don't have a VPS (and I'd rather not pay $15 a month for a VPN just to install a codec).

I'm new to all this, and I understand sudo gives you permissions - but I have been trying to find out why exactly some 'make installs' require sudo access and others dont. I haven't yet found the answer. Again, very knew to this so I'm just trying to learn what's going on.

I recently installed LAME encoder on my server to convert wav to mp3 and that worked with './configure, make, make install;

I then tried to install OGG encoder and that requires './configure, make, sudo make install' - which I cannot do, since I dont have a VPS (and I'd rather not pay $15 a month for a VPN just to install a codec).

I'm new to all this, and I understand sudo gives you permissions - but I have been trying to find out why exactly some 'make installs' require sudo access and others dont. I haven't yet found the answer. Again, very knew to this so i'm just trying to learn whats going on.

I recently installed LAME encoder on my server to convert wav to mp3 and that worked with './configure, make, make install;

I then tried to install OGG encoder and that requires './configure, make, sudo make install' - which I cannot do, since I don't have a VPS (and I'd rather not pay $15 a month for a VPN just to install a codec).

I'm new to all this, and I understand sudo gives you permissions - but I have been trying to find out why exactly some 'make installs' require sudo access and others dont. I haven't yet found the answer. Again, very knew to this so I'm just trying to learn whats going on.