Ask Your Question

Revision history [back]

It seems that you unpacked the source tarball in a directory mounted with a noexec flag. This may be the case if you did it on /tmp/ which is likely to be a tmpfs on RAM.

To understand this, go into the sage source directory, and type

df .
mount

(do not forget the dot in the first command), here you see where is the directory mounted, and then you can see whether there is a noexec flag to the corresponding mount line.

If this is the case, just put the sage directory on a "regular" device.

It seems that you unpacked the source tarball in a directory on which a device is mounted with a noexec flag. This may be the case if you did it on /tmp/ which is likely to be a tmpfs on RAM.

To understand this, go into the sage source directory, and type

df .
mount

(do not forget the dot in the first command), here you see where which device is mounted on the directory mounted, directory, and then you can see whether there is a noexec flag to the corresponding mount line.

If this is the case, just put the sage directory on a "regular" device.

It seems that you unpacked the source tarball in a directory on which a device is mounted with a noexec flag. option. This may be the case if you did it on /tmp/ which is likely to be a tmpfs on RAM.

To understand this, go into the sage source directory, and type

df .
mount

(do not forget the dot in the first command), here you see which device is mounted on the directory, and then you can see whether there is a noexec flag option to the corresponding mount line.

If this is the case, just put the sage directory on a "regular" device.filesystem (typically: a hard disk).

It seems that you unpacked the source tarball in a directory on which a device is mounted with a noexec option. This may be the case if you did it on /tmp/ which is likely to be a tmpfs on RAM.

To understand this, go into the sage source directory, and type

df .
mount

(do not forget the dot in the first command), here you see which device is mounted on the directory, and then you can see whether there is a noexec option to the corresponding mount line.

If this is the case, just put the sage directory on a "regular" filesystem (typically: a POSIX filesystem on a hard disk).