Re: [orbitcpp-list] Yep, I'm the FNG

[Adam Y. <ay...@fo...>]

Yup, that worked.  Got me back to the cross compliling error:
here's my config.log

where does bad_cast come from?  

On my machine I have 

/usr/local/lib/gcc-lib/i386-pc-linux-gnu/2.96/include/exception
and 
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/exception

Neither have a reference to bad_cast.  
What is the issue with cross compiling?  Cross compiling what? Is there
some way to ignore this test to see what happens?


Adam



This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:603: checking for a BSD compatible install
configure:656: checking whether build environment is sane
configure:713: checking whether make sets ${MAKE}
configure:752: checking for working aclocal
configure:765: checking for working autoconf
configure:778: checking for working automake
configure:791: checking for working autoheader
configure:804: checking for working makeinfo
configure:818: checking whether to enable maintainer-specific portions
of Makefiles
configure:937: checking host system type
configure:958: checking build system type
configure:978: checking for ranlib
configure:1008: checking for gcc
configure:1121: checking whether the C compiler (gcc -g ) works
configure:1137: gcc -o conftest -g   conftest.c  1>&5
configure:1163: checking whether the C compiler (gcc -g ) is a
cross-compiler
configure:1168: checking whether we are using GNU C
configure:1177: gcc -E conftest.c
configure:1196: checking whether gcc accepts -g
configure:1239: checking for ld used by GCC
configure:1301: checking if the linker (/usr/bin/ld) is GNU ld
GNU ld version 2.9.5 (with BFD 2.9.5.0.22)
configure:1317: checking for BSD-compatible nm
configure:1353: checking whether ln -s works
ltconfig:603: checking for object suffix
ltconfig:604: gcc -c -g  conftest.c 1>&5
ltconfig:629: checking for executable suffix
ltconfig:630: gcc -o conftest -g   conftest.c  1>&5
ltconfig:776: checking if gcc PIC flag -fPIC works
ltconfig:777: gcc -c -g -fPIC -DPIC  conftest.c 1>&5
ltconfig:829: checking if gcc supports -c -o file.o
ltconfig:830: gcc -c -g -o out/conftest2.o  conftest.c 1>&5
ltconfig:862: checking if gcc supports -c -o file.lo
ltconfig:863: gcc -c -g -c -o conftest.lo  conftest.c 1>&5
ltconfig:914: checking if gcc supports -fno-rtti -fno-exceptions
ltconfig:915: gcc -c -g -fno-rtti -fno-exceptions -c conftest.c 
conftest.c 1>&5ltconfig:958: checking if gcc static flag -static works
ltconfig:959: gcc -o conftest -g   -static conftest.c  1>&5
GNU ld version 2.9.5 (with BFD 2.9.5.0.22)
ltconfig:1653: checking if global_symbol_pipe works
ltconfig:1654: gcc -c -g  conftest.c 1>&5
ltconfig:1657: eval "/usr/bin/nm -B conftest.o | sed -n -e 's/^.*[ 
]\([ABCDGISTW]\)[ 	][ 	]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2\3 \3/p' >
conftest.nm"
ltconfig:1709: gcc -o conftest -g -fno-builtin -fno-rtti
-fno-exceptions   conftest.c conftstm.o 1>&5
configure:1541: checking for gcc
configure:1654: checking whether the C compiler (gcc -g ) works
configure:1670: gcc -o conftest -g   conftest.c  1>&5
configure:1696: checking whether the C compiler (gcc -g ) is a
cross-compiler
configure:1701: checking whether we are using GNU C
configure:1729: checking whether gcc accepts -g
configure:1765: checking for c++
configure:1797: checking whether the C++ compiler (c++ -g -Wall ) works
configure:1813: c++ -o conftest -g -Wall   conftest.C  1>&5
configure:1839: checking whether the C++ compiler (c++ -g -Wall ) is a
cross-compiler
configure:1844: checking whether we are using GNU C++
configure:1853: c++ -E conftest.C
configure:1872: checking whether c++ accepts -g
configure:1915: checking for a BSD compatible install
configure:2024: checking for orbit-config
configure:2059: checking for ORBit - version >= 0.5.1
configure:2242: checking for orbit-idl
configure:2288: checking how to run the C preprocessor
configure:2309: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:2368: checking for ANSI C header files
configure:2381: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:2474: checking whether c++ compiler (c++) supports bad_cast
configure:2491: c++ -c -g -Wall  conftest.C 1>&5
configure: In function `int main ()':
configure:2487: `bad_cast' undeclared (first use this function)
configure:2487: (Each undeclared identifier is reported only once for
each function it appears in.)
configure:2487: parse error before `;'
configure: failed program was:
#line 2484 "configure"
#include "confdefs.h"
#include <exception>
int main() {
 bad_cast a; 
; return 0; }
configure:2518: checking for size of c++ new memory info block
[ayoung@yosemite orbitcpp]$ 


Phil Dawes wrote:
> 
> Hi Adam,
> 
> It looks like autoconf/automake can't find the ORBit.m4 macro. If you
> have installed ORBit from source then this is in your installation
> prefix under $PREFIX/share/aclocal/ORBit.m4  (e.g.
> /usr/local/share/aclocal/ORBit.m4).
> 
> I suspect that this macro is not being picked up because aclocal is
> looking in /usr/share/aclocal/
> Try copying the file there and see what happens. (Looks like the same
> for libtool.m4)
> 
> I'm confused about your config.log being empty - noramlly this is filled
> up as the configure script works AFAIK.
> 
> Cheers,
> 
> Phil.
>