Re: compile failure with current CVS: can only configure for one host and one target at a time

[Duncan Sands <duncan.sands@math.u-psud.fr>]

On Wednesday 26 January 2005 16:22, Daniel Jacobowitz wrote:
> On Wed, Jan 26, 2005 at 04:21:14PM +0100, Duncan Sands wrote:
> > $ ./configure
> > ...
> > $ make
> > ...
> > configure: configuring in gdb.gdbtk
> > configure: running /bin/sh './configure' --prefix=/usr/local  '--prefix=/usr/local' '--cache-file=./config.cache' '--build=i686-pc-linux-gnu' '--host=i686-pc-linux-gnu' '--target=i686-pc-linux-gnu' '--with-gnu-as' '--with-gnu-ld' '--program-transform-name=s,y,y,' 'CC=gcc' 'CFLAGS=-g -O2' 'LDFLAGS=' 'build_alias=i686-pc-linux-gnu' 'host_alias=i686-pc-linux-gnu' 'target_alias=i686-pc-linux-gnu' '--cache-file=.././config.cache' '--srcdir=.' --cache-file=../.././config.cache --srcdir=.
> > configure: warning: CC=gcc: invalid host type
> > configure: warning: CFLAGS=-g -O2: invalid host type
> > configure: error: can only configure for one host and one target at a time
> > configure: error: /bin/sh './configure' failed for gdb.gdbtk
> > configure: error: /bin/sh './configure' failed for testsuite
> > make: *** [configure-gdb] Error 1
> 
> I recommend checking out just GDB instead of the whole source tree, or
> deleting the directories associated with insight.  Or reporting the
> problem to insight@ and getting them to update their autoconf.

Hi Daniel, I thought gdb.gdbtk was part of "just GDB" - it lives in the
gdb subdirectory.  Anyway, if I move the gdb subdirectory out of the rest
of the source tree and confiure in it, then I get

$ ./configure
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for AIX... no
checking for library containing strerror... none required
checking for gcc option to accept ANSI C... none needed
configure: error: cannot find install-sh or install.sh in `cd .;pwd`/.. ./`cd .;pwd`/..

So probably I misunderstood you...

Sorry for the bother,

Duncan.