./configure: Permission denied on removable media - Page 2

vishesh · 08-27-2009, 06:06 AM

Move into directory where your configure script is located

thnks

jschiwal · 08-27-2009, 06:37 AM

Copy the package tarball to your home directory and build it there. Then you will have full permissions. A fat filesystem will have all files with the same permissions. All directories will have the same permissions as well. The fmask=0111 will clear the x bit on all files. You can't use chmod or chown on a fat file system. The configure script or Make file may use the chmod command and this will a failure later on.

wakrein · 08-27-2009, 03:44 PM

Quote:

Originally Posted by jschiwal

Copy the package tarball to your home directory and build it there. Then you will have full permissions. A fat filesystem will have all files with the same permissions. All directories will have the same permissions as well. The fmask=0111 will clear the x bit on all files. You can't use chmod or chown on a fat file system. The configure script or Make file may use the chmod command and this will a failure later on.

listen i have a 4gb solid state disk i have to work off of my media drive.

Quote:

Originally Posted by colucix

Be sure you're in the directory where configure is placed:

Code:

pwd
ls

/home/user/D:/shed-1.15

colucix · 08-27-2009, 04:50 PM

Quote:

Originally Posted by wakrein

/home/user/D:/shed-1.15

I am lost here. Weren't you on /media/D: according to your previous posts? In any case the last error message simply means you are not in the directory containing the configure executable. Just a matter of surfing around until you find it. And yes - I've just checked - the shed source directory contains a configure file and according to the instructions in the INSTALL doc, the installation process is the typical

Code:

./configure
make
make install   # as root

wakrein · 08-27-2009, 05:11 PM

Quote:

Originally Posted by colucix

I am lost here. Weren't you on /media/D: according to your previous posts? In any case the last error message simply means you are not in the directory containing the configure executable. Just a matter of surfing around until you find it. And yes - I've just checked - the shed source directory contains a configure file and according to the instructions in the INSTALL doc, the installation process is the typical

Code:

./configure
make
make install   # as root

yeah but when i go to the /home/user/D:/shed-1.15 diretory and try to ./configure i get the output of permssion denied the reason why i thought this was because the shed-1.15 is on removable media, it denies me for some reason

colucix · 08-27-2009, 05:25 PM

Quote:

Originally Posted by wakrein

yeah but when i go to the /home/user/D:/shed-1.15 diretory and try to ./configure i get the output of permssion denied the reason why i thought this was because the shed-1.15 is on removable media, it denies me for some reason

Ok, please be patient with me but in one of your latest post the error was "No such file or directory", different from the very first one. I assume you're in /home/user/D:/shed-1.15 now. There isn't a configure file in it?

wakrein · 08-27-2009, 05:29 PM

Quote:

Originally Posted by colucix

Ok, please be patient with me but in one of your latest post the error was "No such file or directory", different from the very first one. I assume you're in /home/user/D:/shed-1.15 now. There isn't a configure file in it?

oh sorry if i came off all jumpy

ide like to say i realy appriciate your assistance. anyways yeah im in the shed-1.15 directory now with a configure file in i. In the shed-1.15 directory there is a configure.log file and a configure file.

colucix · 08-27-2009, 05:39 PM

Ok. The presence of configure.log (that I believe is config.log) means you have already run the configure step. In any case, run it again and if it is successful you will see the following at the end of the output:

Code:

[alex@linux shed-1.15]$ ./configure
<omitted>
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands

Just an aside question: what Linux distribution are you running on? Have you tried if there is a shed binary package available before trying to compile it from source? Just out of curiosity.

wakrein · 08-27-2009, 05:52 PM

Quote:

Originally Posted by colucix

Ok. The presence of configure.log (that I believe is config.log) means you have already run the configure step. In any case, run it again and if it is successful you will see the following at the end of the output:

Code:

[alex@linux shed-1.15]$ ./configure
<omitted>
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands

Just an aside question: what Linux distribution are you running on? Have you tried if there is a shed binary package available before trying to compile it from source? Just out of curiosity.

./configure

Code:

bash: ./configure: Permission denied

im running xandros, if it were up to me i would run ubuntu but i only hae a 4gb solid state disk that came with my eeepc900a

wakrein · 08-28-2009, 12:30 AM

im still googleing, cant find anything

any other recommendations?

jschiwal · 08-28-2009, 01:11 AM

You probably copied the shed-1.15 directory to your home directory instead of untar'ing it into your home directory. The bad permissions where then copied as well, since /media/D: uses the fat file system. This means that the `configure' script has the 'x' bit cleared.
If the source tarball is on the /media/D: drive, you can delete the directory and untar it to your home directory.

tar -C ~ -xvf /media/D:/shed-1.15.tar.gz
cd ~/shed-1.15
./configure
make
sudo make install

windtalker10 · 08-28-2009, 01:24 AM

I haven't read the whole post but,,,,,,
you have either done something that made the directory a root directory so are being denied as a user or you're in a root directory trying to install as user, which you can't as user doesn't have that right.

If the directory is laying somewhere like on your desktop, as root, delete it and drop a new directory in it's place and start over as user to have a clean start.
su
cd /path/to/file
rm -r name_of_file

If the above doesn't apply and you have browsed somewhere else through a root folder,,, which is where the media drive folder is,,,, you have no choice but to become root and do your install, which I do not recommend.
Never a wise thing to ./configure and make as root.

Try this:
As root type cp /path/to/media/file_name /home/user-name/Desktop

Note: that is a command and two different locations so make sure you leave a space between each one or you will just get an error code.
Since you're not being allowed to do things as user, it might be faster to just go ahead and copy as root.
That will copy the folder on your desktop.
If it doesn't, try dropping the file name from the command path.

Open the folder and strike F4.
A terminal should open up and as user you can then do ./configure.
If it's still locked as root you can try to:
su
cd /home/user-name/Desktop
chmod 644 name-of-file

Then try to run ./configure again.

wakrein · 08-28-2009, 01:26 AM

Quote:

Originally Posted by jschiwal

You probably copied the shed-1.15 directory to your home directory instead of untar'ing it into your home directory. The bad permissions where then copied as well, since /media/D: uses the fat file system. This means that the `configure' script has the 'x' bit cleared.
If the source tarball is on the /media/D: drive, you can delete the directory and untar it to your home directory.

tar -C ~ -xvf /media/D:/shed-1.15.tar.gz
cd ~/shed-1.15
./configure
make
sudo make install

ill try this but i have very limited hard drive space left

jschiwal · 08-28-2009, 01:40 AM

You don't need the tarball to exist in your home directory if it's on the /media/D:/ directory. You could look at deleting your thumbnails to free up space first: rm ~/.thumbnails/* -rf

From your later posts, you have already copied the D: contents to your home directory. Delete that first before running tar.
Now you should have more room than before.

Good Luck!

wakrein · 08-28-2009, 11:50 PM

i dont think it is impossable to write on vfat, in my cse ./configure but i think my problem is within modifying fstab but i am unfamiure with fstab and uid's