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

[Phil D. <ph...@us...>]

Hi Adam,

Sorry I took so long to reply - I've been away from the fray for a few
days,

The standard dev approach we use is to grab autoconf, automake and
libtool, then do:

./autogen.sh
make
make check

Then start hacking!


Could you mail your config.log file to the mailing list? That file
contains more information.

I'm not sure what's wrong - I use redhat 6.1 and the configure script
works out of the box. It could be a gcc 2.96 thing (I'm using gcc
2.95.2). I'll try and grab a copy of gcc 2.96 today if I remember.

Cheers,

Phil.


Adam Young wrote:
> 
> Yeah, I kept digging but figured I'd keep my spam's down to two per
> day.   conftest is created, compiled, run and removed by configure.  I
> commented out the code that removes it, and after running configure I
> still didn't see it.
> 
> So I got the CVS source and tried autoconf orbitcpp-config.in  crapped
> out in the middle
> 
> Then I tried running ./autogen.sh and it told me I needed libtool.  SO
> now I am in the process of getting libtool and trying that.
> 
> How do y'all work this?  What is the standard Development tactic?
> 
> Adam
> 
> > I believe that conftest is generated during the configure process. the
> > configure script outputs, compiles, and runs little programs to figure
> > out how your system works.
> >
> > It looks like for some reason configure thinks you are running a
> > cross-compiler, which should not be the case.  I don't exactly know
> > how it tells that.
> 
> _______________________________________________
> orbitcpp-list mailing list
> orb...@li...
> http://lists.sourceforge.net/mailman/listinfo/orbitcpp-list