Results 1 to 10 of 10

Thread: Permission denied even as root user

  1. #1
    Join Date
    Jan 2012
    Beans
    8

    Question Permission denied even as root user

    Hey guys,
    I'm trying to compile DOSBox, I type "./configure" while in the correct directory (I'm 100% positive that this is the right one, and this is all in terminal of course). But, I get this:

    Code:
    root@chris-desktop:/media/Beta/dosbox# ./configure
    bash: ./configure: Permission denied
    I don't know if I'm posting this in the right section, but I'm stumped as to how it can deny permission to the root user...

    I've considered that maybe I'm doing it wrong, so if anyone whom has built DOSBox from source in Ubuntu before has any pointers, by all means.

  2. #2
    Join Date
    Feb 2009
    Location
    Dallas, TX
    Beans
    6,593
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Permission denied even as root user

    Hi garandcarbine.

    If the file does not have execution permisions, bash can't execute it.

    Add execute permission to the file:
    Code:
    chmod a+x ./configure
    and then try to execute it again.

    Let us know how it goes.
    Regards.

  3. #3
    Join Date
    Jan 2012
    Beans
    8

    Question Re: Permission denied even as root user

    Hi,
    Tried what you said, here is what terminal gave me (In lieu of output after doing the configure bit, I tried to move on to the next step, exactly as the instructions said)

    Code:
    chris@chris-desktop:/media/Beta/dosbox$ chmod a+x ./configure
    chris@chris-desktop:/media/Beta/dosbox$ make
    make: *** No targets specified and no makefile found.  Stop.
    EDIT: Bollocks, I copied the wrong bit. It's the correct one now, although they had the same result.
    Last edited by garandcarbine; September 27th, 2012 at 05:28 AM. Reason: Wrong code!

  4. #4
    Join Date
    May 2012
    Beans
    43

    Re: Permission denied even as root user

    Doing the chmod command only makes the file executable, it does not run it.
    Try running the configure script now, and then make.

    If that doesn't work, have you tried "sh" instead of "./" ?

  5. #5
    Join Date
    Sep 2006
    Beans
    7,198
    Distro
    Lubuntu Development Release

    Use the repositories

    I see that the repositories have version 0.74 available. You should be able to get it with Synaptic or the Software Center. Is there any particular reason you are trying to compile from source instead of using the pre-packaged edition?

  6. #6
    Join Date
    Aug 2010
    Location
    Lancs, United Kingdom
    Beans
    1,079
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: Use the repositories

    Quote Originally Posted by Lars Noodén View Post
    I see that the repositories have version 0.74 available. You should be able to get it with Synaptic or the Software Center. Is there any particular reason you are trying to compile from source instead of using the pre-packaged edition?
    +1. Prefer pre-built packages to compiling yourself.

    If you do have a reason to compile it yourself then... Does /media/Beta/dosbox sit on a Linux native filesystem? The fact that configure is not already executable suggests that it may be on a Windows filesystem (e.g. FAT, NTFS). If you are doing that, it is probably doomed to failure. Make sure you compile Linux programs on Linux filesystems.

  7. #7
    Join Date
    Jan 2012
    Beans
    8

    Re: Use the repositories

    Quote Originally Posted by Lars Noodén View Post
    I see that the repositories have version 0.74 available. You should be able to get it with Synaptic or the Software Center. Is there any particular reason you are trying to compile from source instead of using the pre-packaged edition?
    Someone told me it's more likely to work if you compile it yourself, because it's configured to work with your system, or some such thing like that. And when I looked on the DOSBox website, I didn't see any builds for Ubuntu, so I thought I'd make my own.

  8. #8
    Join Date
    Jan 2012
    Beans
    8

    Re: Use the repositories

    Quote Originally Posted by spjackson View Post
    +1. Prefer pre-built packages to compiling yourself.

    If you do have a reason to compile it yourself then... Does /media/Beta/dosbox sit on a Linux native filesystem? The fact that configure is not already executable suggests that it may be on a Windows filesystem (e.g. FAT, NTFS). If you are doing that, it is probably doomed to failure. Make sure you compile Linux programs on Linux filesystems.
    Yeah, it's on an NTFS filesystem from when I was running Windows 7. I'll reformat it to a Linux filesystem and try it then. If it doesn't work, then I'll look on software center.

  9. #9
    Join Date
    Jan 2012
    Beans
    8

    Re: Permission denied even as root user

    I got it to configure, turns out it was the filesystem I was compiling on. I installed SDL, and I configured DOSBox, but it gives me this when I try make:

    Code:
    root@chris-desktop:/media/Beta/dosbox# make
    make  all-recursive
    make[1]: Entering directory `/media/Beta/dosbox'
    Making all in src
    make[2]: Entering directory `/media/Beta/dosbox/src'
    Making all in cpu
    make[3]: Entering directory `/media/Beta/dosbox/src/cpu'
    Making all in core_full
    make[4]: Entering directory `/media/Beta/dosbox/src/cpu/core_full'
    make[4]: Nothing to be done for `all'.
    make[4]: Leaving directory `/media/Beta/dosbox/src/cpu/core_full'
    Making all in core_normal
    make[4]: Entering directory `/media/Beta/dosbox/src/cpu/core_normal'
    make[4]: Nothing to be done for `all'.
    make[4]: Leaving directory `/media/Beta/dosbox/src/cpu/core_normal'
    Making all in core_dyn_x86
    make[4]: Entering directory `/media/Beta/dosbox/src/cpu/core_dyn_x86'
    make[4]: Nothing to be done for `all'.
    make[4]: Leaving directory `/media/Beta/dosbox/src/cpu/core_dyn_x86'
    Making all in core_dynrec
    make[4]: Entering directory `/media/Beta/dosbox/src/cpu/core_dynrec'
    make[4]: Nothing to be done for `all'.
    make[4]: Leaving directory `/media/Beta/dosbox/src/cpu/core_dynrec'
    make[4]: Entering directory `/media/Beta/dosbox/src/cpu'
    source='callback.cpp' object='callback.o' libtool=no \
        DEPDIR=.deps depmode=none /bin/bash ../../depcomp \
        g++ -DHAVE_CONFIG_H -I. -I../..  -I../../include -I/usr/local/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT   -c -o callback.o callback.cpp
    ../../depcomp: line 611: exec: g++: not found
    make[4]: *** [callback.o] Error 127
    make[4]: Leaving directory `/media/Beta/dosbox/src/cpu'
    make[3]: *** [all-recursive] Error 1
    make[3]: Leaving directory `/media/Beta/dosbox/src/cpu'
    make[2]: *** [all-recursive] Error 1
    make[2]: Leaving directory `/media/Beta/dosbox/src'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/media/Beta/dosbox'
    make: *** [all] Error 2
    Now that, does not look good... Do I need to chmod make as well?

  10. #10
    Join Date
    Sep 2006
    Beans
    7,198
    Distro
    Lubuntu Development Release

    Re: Permission denied even as root user

    Quote Originally Posted by garandcarbine View Post
    I got it to configure, turns out it was the filesystem I was compiling on. I installed SDL, and I configured DOSBox, but it gives me this when I try make:

    Code:
    ../../depcomp: line 611: exec: g++: not found
    It looks like you need to add the compiler to your system. It's added along with a lot of other things when you install the package build-essential

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •