RE: Target gdb

["Earl Olsen" <earl dot olsen at dilithiumnetworks dot com>]

> -----Original Message-----
> From: Khem Raj [mailto:khem@mvista.com] 
> Sent: Friday, February 03, 2006 11:44 AM
> To: Earl Olsen
> Cc: crossgcc maillist
> Subject: Re: Target gdb
> 
> because the configury does not know about your build system 
> it thinks that the native build it being done on a powerpc 
> machine and tries to run the a.out which is to be run on 
> powerpc machine on your host machine which I guess is a x86 
> machine. Thats the problem you are seeing. If you add --build 
> option to the configure call it should be able to find out 
> that the build machine is not same as host machine.

I added --build=i686-pc-linux-gnu and got further (it took me a bit 
of detective work to figure out what the exact setting should be).
It blew up when building something called "readline".
So I looked at the gdb bug tracking system and found a suggestion
to export bash_cv_have_mbstate_t=yes before doing configure.
That did it.  

So the complete receipe is:

    cd $BUILD_TMP_DIR/build-gdb
    export bash_cv_have_mbstate_t=yes 
    CC=$TARGET-gcc $BUILD_TMP_DIR/$GDB_DIR/configure \
         --prefix=$PREFIX/$TARGET --host=$TARGET
--build=i686-pc-linux-gnu
    make BUILD_SUBDIR=""
    make install

Clear as mud!  Anyway, now to try the gdb on the target.

Thanks for all the help guys.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org