How to fix this compile error for Xdebug on Homestead - xdebug

I cannot install Xdebug on Homestead because I get some sort of compile error.
I am following the Xdebug Wizard (https://xdebug.org/wizard) and when I input the ./configure command I get this error:
configure: error: in /home/vagrant/code/xdebug-2.7.2:
configure: error: cannot run C compiled programs.
If you meant to cross compile, use '--host'.
See 'config.log' for more details

This points at that you don't have a C compiler installed at all. You will have better luck after installing the php-dev package first, which should pull in the compilers that PHP extensions will need.

Related

C preprocessor "/lib/cpp" fails sanity check on Mac

I am trying to install a software package called HYPRE on my Macbook (High Sierra 10.13.6). I follow the install instructions, which require me to first navigate to the appropriate folder and type ./configure in the terminal. This generates the error:
checking how to run the C preprocessor... /lib/cpp
configure: error: in /Users/Tilton/FVM/HYPRE/hypre-master/src': configure: error: C preprocessor "/lib/cpp" fails sanity check See config.log' for more details
I searched around and saw some similar error issues reported online, but could not understand the issue. I am happy to share the config.log file, but it's very long ...

Cannot install macvim due to Xcode as "pre-release"

I'm trying to upgrade my Vim to MacVim by running:
$ brew install macvim --with--override-system-vim
I'm getting this error message saying that the package cannot be compiled:
configure: creating cache auto/config.cache
checking whether make sets $(MAKE)... yes
checking for gcc... clang
checking whether the C compiler works... no
configure: error: in `/private/tmp/macvim-20161028-10122-1pp1odr/macvim-snapshot-113/src':
configure: error: C compiler cannot create executables
See `config.log' for more details
I have Xcode 8.1 installed on my machine. But brew seems to think it's a pre-release version:
Warning: You are using a pre-release version of Xcode.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.

Upgraded to Mavericks, C compiler cannot create executables

Upgrading to Mavericks, I appear to have broken my Ruby on Rails development environment, which requires ruby 1.9.3 because of various gem dependencies. Within that app directory, I'm trying to reinstall ruby 1.9.3-p547:
rvm reinstall ruby-1.9.3-p547
I then get an error:
checking whether the C compiler works... no
configure: error: in `/Users/dsfaulkenberry/.rvm/src/ruby-1.9.3-p547':
configure: error: C compiler cannot create executables
Looking at the config.log file (~/.rvm/src/ruby-1.9.3-p547/config.log), I see:
dyld: Library not loaded: /usr/local/opt/cloog-ppl015/lib/libcloog.0.dylib
Referenced from: /usr/local/Cellar/gcc46/4.6.4/gcc/libexec/gcc/x86_64-apple-darwin12.4.0/4.6.4/cc1
Reason: image not found
I can see that other people have encountered issues vis-à-vis upgrading to Mavericks and having c compiler issues, but I can't find any referencing this specific library or what I should do (reinstall gcc? is that even a thing I can do?)
Many solutions mention accepting an XCode license agreement, which I have done, and the problem persists.
Reinstalling gcc46 solved the issue for me:
brew uninstall gcc46 && brew install gcc46

Package path error when trying to install lib package in C

I am trying to install libpackedobjects on my fedora 17. The path that I am trying to install it on is home/libpackedobjects. The steps that I am following are:
git clone git://gitorious.org/libpackedobjectsd/libpackedobjectsd.git
cd libpackedobjectsd
autoreconf -i
./configure
when I am trying to run the ./configure I am getting error:
checking for LIBPACKEDOBJECTS... no
configure: error: Package requirements (libpackedobjects) were not met:
No package 'libpackedobjects' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBPACKEDOBJECTS_CFLAGS
and LIBPACKEDOBJECTS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I do understand that the path can not be found, but do not know how to repair the problem. Any suggestions?
As evident from your error report:
checking for LIBPACKEDOBJECTS... no
configure: error: Package requirements (libpackedobjects) were not met:
No package 'libpackedobjects' found
Hence, You have to install the packages libpackedobjects and libXml2to install the libpackedobjectsd.
If you still get this error after installing the depenedent packages, there might be a PATH issue or linking issue.

error installing BRugs "C compiler cannot create executables"

I am trying to install the R library BRugs on my Ubuntu 12.04 desktop.
> sessionInfo()
R version 2.15.1 (2012-06-22)
Platform: x86_64-pc-linux-gnu (64-bit)
But I get the following error:
* installing *source* package ‘BRugs’ ...
** package ‘BRugs’ successfully unpacked and MD5 sums checked
checking for prefix by checking for OpenBUGS... /usr/bin/OpenBUGS
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/RtmpnNLTG1/R.INSTALL488b7635d4c0/BRugs':
configure: error: C compiler cannot create executables
See `config.log' for more details
ERROR: configuration failed for package ‘BRugs’
* removing ‘/home/myuser/lib/R/BRugs’
Warning in install.packages("BRugs") :
installation of package ‘BRugs’ had non-zero exit status
The downloaded source packages are in
‘/tmp/Rtmp2ytOWn/downloaded_packages’
Here is a link to config.log. It is difficult to tell what the error is, except that the errors starts with gcc: error: unrecognized option '-V'.
How can I get around this error (and install BRugs)?
According to the package description:
Versions running on Linux and on 64-bit R under Windows are in "beta"
status and less efficient.
And it looks like configure is trying to build the package using 32-bit executables (note the -m32 flags). It's probably best if you contact the package maintainer(s) and ask them how to build the 32-bit executable under 64-bit Ubuntu.

Resources