Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: ./configure error .. "no acceptable C compiler found in $PATH"

  1. #1
    Join Date
    Mar 2011
    Location
    U.K.
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    ./configure error .. "no acceptable C compiler found in $PATH"

    I'm trying to install a package on Ubuntu 10.10 and I've tried on both localhost server and a remote server .. but getting the same permissions error.

    I started by downloading a *.tar.gz to install.
    unzip and then I navigate to the folder to run ./configure.

    I try the command ./configure
    but the error points to config.log: Permission denied

    Code:
    ./configure: line 2044: config.log: Permission denied
    ./configure: line 2054: config.log: Permission denied
    And in the log file "no acceptable C compiler found in $PATH"

    I've searched around for a solution and I've tried these commands

    Code:
    sudo apt-get install build-essentials    (typo corrected: syntax used was "build-essential")
    sudo apt-get install gcc build-essentials     (typo corrected: syntax used was "build-essential")
    sudo apt-get install g++ build-essentials    (typo corrected: syntax used was "build-essential")
    but I still can't install the package. Permission denied.

    Any other suggestions to get past this point?
    Last edited by dragonfly41; November 17th, 2011 at 03:31 PM.

  2. #2
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    13,820
    Distro
    Kubuntu Development Release

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    First the package is called "build-essential" not "build-essentials". When you ran the commands you gave, you should have gotten an obvious error. You only need to install build-essential; it will bring the compilers in for you.

    Next, the "config.log" errors indicate that you're trying to build it in a directory to which you don't have permissions. Try this using your own account throughout. Create a "build" directory in your home directory, untar the source tarball to that directory, go to the directory that was created, then run ./configure and make. If everything compiles cleanly, run "sudo make install" to install it.

    It's quite possible that configure will fail with complaints about missing headers and libraries. If you're trying to compile a package that already exists in the repositories (say you want a more recent version), you should run "sudo apt-get build-dep packagename" to install any needed source dependencies before running configure.

  3. #3
    Join Date
    Dec 2006
    Beans
    7,307

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Can I ask what package you are compiling?
    You think that's air you're breathing now?

  4. #4
    Join Date
    Mar 2011
    Location
    U.K.
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Firstly, thank you SeijiSensei and Andrew.46 for your replies.


    That was my typo error in my post .. in fact I did use the correct syntax

    "sudo apt-get build-essential" and not "sudo apt-get build-essentials"


    I'll expand further on my objectives (might help others following the same path):


    "To install caucho.com resin-4.0.23 (open source version) on Ubuntu 10.10 remote server (Amazon EC2 instance)"


    Why am I interested in Caucho Resin-4.0.23 when I can install Tomcat7?

    Because Caucho allows tighter integration of PHP (through Quercus PHP servlet) and Java.

    And I have this duo running fine in localhost mode.

    Apache2.2 is the front end and Resin-4.0.23 is the backend.

    See "Resin with Apache" here .. http://www.caucho.com/resin-3.0/install/install.xtp

    The problem is installation of Caucho Resin on a remote Ubuntu 10.10 server (EC2 instance) using only terminal commands and FileZilla.

    The following notes might help others trying to follow this path.

    ....

    In my local development environment I am running Windows Vista and Ubuntu 10.10 in dual boot mode so I can switch between the two environments. I still have to refer to some Windows apps although the target deployment is on Ubuntu

    I have an instance of Ubuntu 10.10 on EC2.

    I access Amazon AWS through Windows PuTTY client (and Pageant running for key reference) and FileZilla.

    ....

    My first attempt to install resin-4.0.23 was to try to use the .deb package

    http://caucho.com/resin-4.0/admin/st...buntuandDebian


    From the running instance of Ubuntu 10.10 I downloaded /etc/apt/sources.list to my Windows client

    and added to sources.list the line ..

    Code:
    deb http://caucho.com/download/debian unstable multiverse
    I uploaded sources.list to the EC2 instance to overwrite the default sources.list file.

    Initially there were a few headaches on file permissions but from a PuTTY session I

    temporarily used these commands

    Code:
    sudo chown -R ubuntu:ubuntu /etc/apt/sources.list
    
    sudo chmod u+rwx /etc/apt/sources.list
    then I could upload edited sources.list from my client through FileZilla

    After uploading I could then right click on the uploaded /etc/apt/sources.list file and

    reset file permissions back to 644.

    ..


    Now I tried the commands to install the deb package:-

    Code:
    sudo apt-get update
    
    sudo apt-get install resin
    Note: I made a point of installing the open source resin and not the commercial version
    resin-pro which requires a licence. But the log still shows reference to resin-pro.

    I hit a dead-end with this message from terminal

    Code:
    Setting up resin-pro (4.0.23) ...
    /usr/sbin/invoke-rc.d: 446: /etc/init.d/resin: not found
    invoke-rc.d: initscript resin, action "start" failed.
    dpkg: error processing resin-pro (--configure):
    subprocess installed post-installation script returned error exit status 127
    Processing triggers for libc-bin ...
    ldconfig deferred processing now taking place
    Errors were encountered while processing:
    resin-pro
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    .................................................. ....................


    I searched around and found this reference


    http://bugs.caucho.com/bug_view_adva...hp?bug_id=4816

    which is linked to ubuntu forum post

    http://ubuntuforums.org/showthread.php?p=11330606

    At the bottom of the caucho bug post is this comment ..

    the error is in the script of the deb package: /etc/init.d/resin
    to solve, change the first line:

    #!@BASH@
    to
    #!/bin/sh
    I don't know how to hack deb files to make the above correction (using 7-zip I did confirm that the above file does have #!@BASH@ at top but after editing this file I would have to repack the deb).

    I did consider this idea but gave up and decided on a different approach (unless someone can explain how to unpack/edit/repack a deb file).

    This bug report indicates that this will be fixed (ETA) in resin-4.0.24 (which is not yet listed on caucho downloads page)

    ....

    I restarted by launching a fresh instance of EC2 and terminated the other EC2 instance which had the failed installation of resin-pro (not resin).

    I read this .. "Compiling things on Ubuntu the Easy Way"

    https://help.ubuntu.com/community/CompilingEasyHowTo


    I downloaded resin-4.0.23.tar.gz into root

    (not sure if this should be downloaded and unpacked into /usr/local/resin-4.0.23 ).

    Code:
    wget http://www.caucho.com/download/resin-4.0.23.tar.gz
    Unpacked the .tar.gz

    Code:
    tar -zxvf resin-4.0.23.tar.tgz
    Navigate to unpacked resin-4.0.23 (in folder so I don't need a "build" folder).

    Code:
    cd resin-4.0.23
    
    ./configure
    and I hit the errors as in my first post above.

    I have not progressed to using
    make
    make install




    Other references to resin and Ubuntu found here ..

    http://bugs.caucho.com/my_view_page.php

    http://bugs.caucho.com/view_all_bug_...?page_number=1

    http://bugs.caucho.com/view.php?id=4851

    0004851: $ sudo apt-get install resin-pro fails on Ubuntu 11.10 64 bit (Multiple)

  5. #5
    Join Date
    May 2010
    Location
    Lancaster, UK
    Beans
    315
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Have you tried

    Code:
    sudo ./configure
    rather than just

    Code:
    ./configure

  6. #6
    Join Date
    May 2010
    Location
    Lancaster, UK
    Beans
    315
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Also, since its lines 2044 and 2054 in your configure file that seem to be the trouble, can you please post them.
    Last edited by carranty; November 17th, 2011 at 03:53 PM.

  7. #7
    Join Date
    May 2010
    Location
    Lancaster, UK
    Beans
    315
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Also, since its lines 2044 and 2054 in your configure file that seem to be the trouble, can you please post them. If your not sure how the command

    Code:
    cat -n configure | grep 2044
    and

    Code:
    cat -n configure | grep 2054
    should extract them.

  8. #8
    Join Date
    Mar 2011
    Location
    U.K.
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Have you tried sudo ./configure?
    I thought I had .. but appears not .. trying this ..

    Code:
    cd resin-4.0.23
    sudo ./configure
    yields ...

    Code:
    Resin Configuration summary:
    
      RESIN_HOME  : /usr/local/resin
          root    : /var/www
          conf    : /etc/resin
          log     : /var/log/resin
          plugins : common resin_os
          init    : /etc/init.d/resin
      JAVA_HOME: /usr/lib/jvm/java-6-openjdk
    
        + 32-bit JNI in -I/usr/lib/jvm/java-6-openjdk/include
        + JNI CFLAGS: -g -O2 -DPOLL -DEPOLL -D_POSIX_PTHREAD_SEMANTICS -pthread -fPIC -fno-omit-frame-pointer -O2 -m32 -DHAS_SOCK_TIMEOUT -DHAS_JVMTI
        + epoll() for keepalives
        + not using OpenSSL
    Then still in resin-4.0.23

    make
    make install


    and finally ..

    ~resin-4.0.23/bin/resin.sh

    (Note: httpd.sh referred to in above old link from caucho.com is now replaced with resin.sh )

    yields this ..

    Code:
    ~$ resin-4.0.23/bin/resin.sh
      Resin requires a command:
      console - start Resin in console mode
      status - watchdog status
      start - start a Resin server
      start-with-foreground - start Resin server keeping parent JVM (OSX)
      gui - start a Resin server with a GUI
      stop - stop a Resin server
      restart - restart a Resin server
      kill - force a kill of a Resin server
      shutdown - shutdown the watchdog
      deploy - deploys an application
      deploy-copy - copies an application
      deploy-list - lists all deployed applications
      deploy-restart - restarts an application
      deploy-start - starts an application
      deploy-stop - stops an application
      undeploy - undeploys an application
      heap-dump - produces a heap dump
      thread-dump - produces a thread dump
      pdf-report - generates pdf report (Pro version only)
      profile - profiles the system
      list-restarts - lists server restart timestamps
      log-level - sets a log level
      jmx-list - lists MBeans, attributes, operations
      jmx-dump - dumps all MBean attributes and values
      jmx-set - sets value on MBean's attribute
      jmx-call - invokes a method on MBean
      user-add - adds an admin user
      user-remove - removes an admin user
      user-list - lists admin users
      help <command> - prints command usage message
      version - prints version
    So I executed

    Code:
    ~$ resin-4.0.23/bin/resin.sh start
    hoping to start the resin server .. and this was the output

    Code:
    com.caucho.config.ConfigRuntimeException: java.io.IOException: Cannot create directory: /home/ubuntu/resin-4.0.23/watchdog-data
            at com.caucho.config.ConfigException.create(ConfigException.java:168)
            at com.caucho.env.service.ResinSystem.configureRoot(ResinSystem.java:172)
            at com.caucho.env.service.ResinSystem.<init>(ResinSystem.java:159)
            at com.caucho.boot.ResinBoot.<init>(ResinBoot.java:128)
            at com.caucho.boot.ResinBoot.main(ResinBoot.java:242)
    Caused by: java.io.IOException: Cannot create directory: /home/ubuntu/resin-4.0.23/watchdog-data
            at com.caucho.vfs.FilePath.mkdirs(FilePath.java:494)
            at com.caucho.env.service.RootDirectorySystem.<init>(RootDirectorySystem.java:69)
            at com.caucho.env.service.RootDirectorySystem.createAndAddService(RootDirectorySystem.java:85)
            at com.caucho.env.service.ResinSystem.configureRoot(ResinSystem.java:170)
            ... 3 more
    ...

    but at least we are past the configure point and nearer the launch point.

    Any further ideas on curing the java.IOException .. or is it a permissions issue??


    [NOTE ADDED]

    I have found the same symptoms in this caucho bug report ..

    http://bugs.caucho.com/bug_view_adva...hp?bug_id=4602

    deploying to remote server

    I'll have to investigate




    [FURTHER ADDED NOTE]

    To answer the question on the configure file errors ..

    cat -n configure | grep 2044
    returns ...
    2044 cat >config.log <<_ACEOF

    cat -n configure | grep 2054
    returns ...
    2054 exec 5>>config.log
    Last edited by dragonfly41; November 17th, 2011 at 06:10 PM. Reason: Answering earlier question on configure file errors

  9. #9
    Join Date
    May 2010
    Location
    Lancaster, UK
    Beans
    315
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    Its not a permissions issue anymore, as far as I an tell. Have you got the java runtime environmet installed? You might need it, you can get it using the below code

    Code:
    sudo add-apt-repository ppa:sun-java-community-team/sun-java6
     sudo apt-get update
     sudo apt-get install sun-java6

  10. #10
    Join Date
    Mar 2011
    Location
    U.K.
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: ./configure error .. "no acceptable C compiler found in $PATH"

    We're on the same track ..

    Inspecting /usr/lib/jvm/

    there is ....
    Code:
    default-java
    java-1.6.0-openjdk
    java-6-openjdk
    .java-6-openjdk.jinfo
    But inspecting /etc/init.d/resin

    there this ..
    Code:
    JAVA_HOME="/usr/lib/jvm/java-6-sun"
    RESIN_HOME="/usr/share/resin"
    CONSOLE="/var/log/resin/console.log
    So this is looking for java-6-sun

    I searched around and found this article

    http://java.dzone.com/articles/sun-j...untu-1004-1010

    Much to my surprise, but probably not those of the Open Source Ruling Class, Sun's Java 6 has been removed from the Ubuntu Multiverse. Apparently the Ubuntu folks have started putting some weight behind their recommendations for switching to the "OpenJDK." Fortunately, the official, "proprietary" Java is still available through another Ubuntu repository.

    Ubuntu 10.10
    To install Sun's Java 6 JDK on Ubuntu 10.10, add the Sun Java6 Community PPA and install:
    add-apt-repository ppa:sun-java-community-team/sun-java6
    apt-get update
    apt-get install sun-java6-jdk
    update-java-alternatives -s java-6-sun
    But at the end of this installation was this ..

    Code:
    Setting up resin-pro (4.0.23) ...
    /usr/sbin/invoke-rc.d: 446: /etc/init.d/resin: not found
    invoke-rc.d: initscript resin, action "start" failed.
    dpkg: error processing resin-pro (--configure):
     subprocess installed post-installation script returned error exit status 127
    Errors were encountered while processing:
     resin-pro
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    ubuntu@ip-10-56-53-46:~$ sudo update-java-alternatives -s java-6-sun
    update-alternatives: error: no alternatives for mozilla-javaplugin.so.
    update-alternatives: error: no alternatives for xulrunner-1.9-javaplugin.so.
    update-alternatives: error: no alternatives for mozilla-javaplugin.so.
    update-alternatives: error: no alternatives for xulrunner-1.9-javaplugin.so.
    .......

    there is another approach here .. http://www.webupd8.org/2011/09/how-t...-7-jdk-in.html


    I've just tried this ..

    but then the pop up menu will not work in a remote server configuration where there is no GUI !


    ~$ sudo update-java

    (gksudo:2209 ): Gtk-WARNING **: cannot open display:

    (zenity:2228 ):Gtk-WARNING **: cannot open display:



    End of that experiment ...

    .......

    Unless there is something obvious I've missed .. I think I've reached the point where I should terminate my EC2 instance of Ubuntu 10.10 and start again with a fresh instance using the lessons learned above to get a clean installation of resin .. probably into /usr/local/ as explained here ... http://blog.caucho.com/2011/05/26/an...n-directories/

    Another posting suggests that resin-pro can be installed without a licence.

    If I get resin working in Ubuntu 10.10 / EC2 I'll post here a precis of the setup.
    Last edited by dragonfly41; November 17th, 2011 at 10:15 PM.

Page 1 of 2 12 LastLast

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
  •