On Wed, 14 May 2014, Miguel Angel Salazar de Troya wrote:

> I am using petsc 3.4-4 and gcc 4.7. I have gcc 4.8 installed by default, by
> I thought I would change to 4.7 since it is the last version you guys
> tested libmesh with (as it appears in the website).

Gah, thanks for the information.  We need to update the website; I've
been using libMesh successfully with gcc-4.8 for a while, and once
with whatever gcc-4.9-pre version is available in the Ubuntu PPAs.

> I highlight here some of the errors I get during the configuration stage:
>
> gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-7ubuntu3)
> configure:5662: $? = 0
> configure:5651: /usr/bin/gcc-4.7 -V >&5
> gcc-4.7: error: unrecognized command line option '-V'
> gcc-4.7: fatal error: no input files
> compilation terminated.
> configure:5662: $? = 4
> configure:5651: /usr/bin/gcc-4.7 -qversion >&5
> gcc-4.7: error: unrecognized command line option '-qversion'
> gcc-4.7: fatal error: no input files
> compilation terminated.

These aren't actually errors; configure is just autodetecting which
compiler flags your compiler does and doesn't support.

> configure:10667: /usr/bin/gcc-4.7 -E  conftest.c
> conftest.c:12:28: fatal error: ac_nonexistent.h: No such file or directory

This is an *intentional* error; configure is making sure that your
compiler gives a failure code on exit when the preprocessor fails.

> In file included from /usr/include/c++/4.8/unordered_map:35:0,
>                 from conftest.cpp:56:
> /usr/include/c++/4.8/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.

This *probably* isn't an error; we test for compiler/STL support for
several different versions of hash table based containers, and on
recent gcc versions this particular hash table should indeed only be
enabled when using C++11.

> The makecheck.log also includes some errors that prompted me to write this
> email.

Send us those?  We still might have to back up into the configure logs
to figure out what caused them, but at least in "make" there shouldn't
be any expected errors to distract from whatever the real problem is.
---
Roy

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to