Configure errors for Cbc-2.2.2 on Fedora11 (64 bits)

[svigerske]

Issue created by migration from Trac.

Original creator: fmargot

Original creation time: 2009-06-18 11:39:29

Assignee: @andrea5w

Version: 0.5

CC: fmargot@andrew.cmu.edu

The following (non fatal) errors are reported when running

../configure -C

for compiling Cbc-2.2.2.

configure:2482: gcc -c -g -O2  conftest.c >&5
conftest.c:2: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'me'
configure:2488: $? = 1
configure: failed program was:
| #ifndef __cplusplus
|   choke me
| #endif

configure:3419: g++ -c -g -O2  conftest.cc >&5
conftest.cc: In function 'int main()':
conftest.cc:13: error: 'exit' was not declared in this scope
configure:3425: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| 
| #define PACKAGE_NAME "Cbc"
| #define PACKAGE_TARNAME "cbc"
| #define PACKAGE_VERSION "2.2.2"
| #define PACKAGE_STRING "Cbc 2.2.2"
| #define PACKAGE_BUGREPORT "coin-cbc`@`lists.coin-or.org"
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| exit (42);
|   ;
|   return 0;
| }
configure:3374: g++ -c -g -O2  conftest.cc >&5
conftest.cc:9: error: 'void std::exit(int)' should have been declared inside 'std'

configure:6630: gcc -E  conftest.c
conftest.c:14:28: error: ac_nonexistent.h: No such file or directory

I attach the main config.log file

[svigerske]

Attachment config.log by fmargot created at 2009-06-18 11:40:07

[svigerske]

Comment by @andrea5w created at 2009-06-23 14:45:47

hHi Francois,

I think those "errors" are benign, I have looked at the "exit" part before. The configure tests are meant to create also errors, like in the first example, where it is essentially trying to see if __cplusplus is defined automatically by the compiler.

Why do these messages worry you?

Andreas

[svigerske]

Comment by fmargot created at 2009-06-23 16:27:05

Replying to [comment:1 andreasw]:

hHi Francois,

I think those "errors" are benign, I have looked at the "exit" part before. The configure tests are meant to create also errors, like in the first example, where it is essentially trying to see if __cplusplus is defined automatically by the compiler.

As I said, these are non-fatal errors, but since no such error occur on Fedora 10 ix86 32-bits, I thought that maybe something can be done to remove them.

Why do these messages worry you?

How would I know what is worrysome or not? That is your job :->

Francois

[svigerske]

Comment by @LouHafer created at 2010-12-09 03:56:37

I'm with Andreas. Never look inside config.log, it'll just upset you. :-) More seriously, 64-bit configure has worked fine for me on Fed12 and Fed14. I'm going to claim this is fixed.

[svigerske]

Comment by @LouHafer created at 2010-12-09 03:56:37

Resolution: fixed