Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile fails on up-to-date Fedora 18 system #91

Open
GoogleCodeExporter opened this issue Mar 20, 2015 · 2 comments
Open

Compile fails on up-to-date Fedora 18 system #91

GoogleCodeExporter opened this issue Mar 20, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Download tarball (or zip file)
2. Expand
3. assert ./configure

What is the expected output?
effective Makefile

What do you see instead?
clean terminal output; error-filled config.log
]$ grep -i error config.log
g++: error: unrecognized command line option '-V'
g++: fatal error: no input files
g++: error: unrecognized command line option '-qversion'
g++: fatal error: no input files
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
conftest.c:59:23: error: expected expression before ')' token
conftest.c:60:24: error: expected expression before ')' token
conftest.c:61:13: error: '__uint16' undeclared (first use in this function)
conftest.c:61:24: error: expected expression before ')' token
conftest.cpp:30:28: fatal error: ac_nonexistent.h: No such file or directory
conftest.cpp:30:28: fatal error: ac_nonexistent.h: No such file or directory
conftest.cpp:63:37: fatal error: google/malloc_extension.h: No such file or 
directory
conftest.cpp:30:37: fatal error: google/malloc_extension.h: No such file or 
directory
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../include/c++/4.7.2/bits/c++0x_
warning.h:32:2: error: #error This file requires compiler and library support 
for the ISO C++ 2011 standard. This support is currently experimental, and must 
be enabled with the -std=c++11 or -std=gnu++11 compiler options.
conftest.cpp:35:7: error: 'unordered_map' in namespace 'std' does not name a 
type
conftest.cpp:36:33: error: 't' was not declared in this scope
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../include/c++/4.7.2/bits/c++0x_
warning.h:32:2: error: #error This file requires compiler and library support 
for the ISO C++ 2011 standard. This support is currently experimental, and must 
be enabled with the -std=c++11 or -std=gnu++11 compiler options.
conftest.cpp:35:7: error: 'tr1' in namespace 'std' does not name a type
conftest.cpp:36:33: error: 't' was not declared in this scope
conftest.cpp:35:7: error: 'unordered_map' in namespace 'std' does not name a 
type
conftest.cpp:36:33: error: 't' was not declared in this scope
conftest.cpp:41:14: error: 'std::tr1' has not been declared
conftest.cpp:41:24: error: expected primary-expression before 'int'
conftest.cpp:41:24: error: expected ',' or ';' before 'int'

What version of the product are you using? On what operating system?
sparsehash-2.0.2
Fedora 18 - X86-64 PC

Please provide any additional information below.
tarball contains both configure.ac and configure. Autoconf does not modify or 
replace configure, so configure.ac seems out of place.
Renaming configure to configure.backup produces a new configure file, with the 
following message:
]$ autoconf
aclocal.m4:16: warning: this file was generated for autoconf 2.68.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
There is no autoreconf.
The new configure file produced the cited error list. The error list produced 
by the downloaded configure file was similar.

Original issue reported on code.google.com by burniew...@gmail.com on 8 Apr 2013 at 4:47

@GoogleCodeExporter
Copy link
Author

Hi,

the errors in the config.log seem to be mainly for testing the capabilities of 
the build machine. Can you confirm that a Makefile is not correctly produced 
after running ./configure ?

Also, have you got automake installed? If you want to play around with the 
build configuration, you'll need the parts of that package.

Let me know how you get on.

Cheers,
Donovan.

Original comment by DonovanH...@gmail.com on 8 Apr 2013 at 9:50

@GoogleCodeExporter
Copy link
Author

I have automake installed. I have little direct experience with either; in the 
past my ./configure/make/make install sequences have worked fine.

I tried g++ --help; it exhibited no -V option. Also, gcc has no "qversion" - 
looks like a typo to me.

Makefiles were produced; make all produces no error messages. I did not install 
before posting b/c of the error messages.

Install exhibits no error messages. Looks like your surmise was correct; 
installation indicates libraries properly inserted into /usr/local. If they 
work for me, I may or may not try to correct the build configuration - if I do 
I will let you know about it.

Thanks much for your help, Donovan

  -- Burnie

Original comment by burniew...@gmail.com on 8 Apr 2013 at 2:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant