It looks like WSL might be assuming that *all* files are executables. Cygwin does the same thing if you don't have UNIX permissions emulation through Windows ACLs enabled (though it is by default). I'm not sure what the current state of WSL is in terms of emulating UNIX-style permissions, but I'd have assumed they were at least past needing to assume all files are executable.
Can you set the file build/pkgs/mpc/spkg-install to not be executable? E.g. chmod -x build/pkgs/mpc/spkg-install Afterwards you *should* have something like $ ls -l build/pkgs/mpc/spkg-install -rw-rw-r-- 1 embray embray 583 Apr 11 14:02 build/pkgs/mpc/spkg-install with no 'x' in the permissions string. If chmod still doesn't work then that's a problem with WSL (on which I'm not sure building Sage is fully supported yet anyways, though it has worked off-and-on). On Tue, Apr 17, 2018 at 5:40 PM, 3kk7 <[email protected]> wrote: > I downloaded Ubuntu binaries from the website, extracted tar, and ran make > in extracted directory. Attached is the error I'm getting from a package > called mpc-1.0.3.p0. > > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
