#6 .configure error with 2.27 on Debian unstable

closed-fixed
nobody
None
5
2004-07-11
2004-07-11
No

Hello,

Just trying to compile the plugin under Debian
(unstable) but running /.configure fails with the
following error:
---
checking dlfcn.h usability... yes
checking dlfcn.h presence... no
configure: WARNING: dlfcn.h: accepted by the compiler,
rejected by the preprocessor!
configure: WARNING: dlfcn.h: proceeding with the
compiler's result
checking for dlfcn.h... yes
checking for g++... no
checking for c++... no
checking for gpp... gpp
checking whether we are using the GNU C++ compiler... no
checking whether gpp accepts -g... no
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails
sanity check
See `config.log' for more details.
---

I tried having a look around the net for a solution but
no luck. At least one more person seems to have
reported it though. Also, I came across a similar
report for another program and there the suggestion was
that there was a problem with configure.am(?)

Anyway, this is way over my head. I attach the
config.log just in case.

HTH

Discussion

  • Anonymous - 2004-07-11

    config.log

     
  • Anonymous - 2004-07-11

    Logged In: YES
    user_id=475552

    Ooops, lets try that upload once more...

     
  • Bill Tompkins

    Bill Tompkins - 2004-07-11

    Logged In: YES
    user_id=21203

    Huh. I develop the plugin on my Debian-unstable box, and it
    usually works for me :)

    I see the following error in your config.log:

    cpp: installation problem, cannot exec `cc1plus': No such
    file or directory.

    Make sure that you have g++ (the C++ compiler) installed,
    not just gcc. I'm not sure why the configure process is
    looking for/requiring C++, as the plugin doesn't use it,
    but... there's autoconf for you.

    If that doesn't fix it, there may be something screwy with
    the versions of GCC on your system, and perhaps setting the
    envronment variables:
    export CC="gcc-3.3"
    export CXX="g++-3.3"
    (substitute appropriately for the actual name of the
    compiler only your system) and then running ./configure,
    will do the trick.

    -Bill

     
  • Bill Tompkins

    Bill Tompkins - 2004-07-11
    • assigned_to: nobody --> obobo
     
  • Anonymous - 2004-07-11

    Logged In: YES
    user_id=475552

    Installing g++ fixed the problem - thanks a lot! Is it
    possible to have .configure check for g++ (like it does with
    glib etc)? I don't code, so it is not something I would have
    installed normally.

    This bug is probably ripe for closing then.

    Thanks again!

     
  • Bill Tompkins

    Bill Tompkins - 2004-07-11
    • assigned_to: obobo --> nobody
    • status: open --> closed-fixed
     

Log in to post a comment.