This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
running configure without arguments?
- From: Christian Jönsson <c dot christian dot joensson at telia dot com>
- To: binutils <binutils at sources dot redhat dot com>
- Date: Tue, 31 Dec 2002 12:47:10 +0100
- Subject: running configure without arguments?
This was on a Windows XP SP1/cygwin P4 system with these packages
binutils 2.13.90 20021118 (cygwin ver. 20021117-1)
cygwin 1.3.18-1
dejagnu 1.4.2.x (cygwin ver. 20021217-1)
gcc 3.2-3
Just for 'fun', I did a configure of the current cvs trunk withouit any arguments, i.e., ../src/configure
This is the log of the top configure:
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for ar... ar
checking for as... as
checking for dlltool... dlltool
checking for ld... ld
checking for nm... nm
checking for ranlib... ranlib
checking for windres... windres
checking for objcopy... objcopy
checking for objdump... objdump
checking for ar... ar
checking for as... as
checking for dlltool... dlltool
checking for ld... ld
checking for nm... nm
checking for ranlib... ranlib
checking for windres... windres
configure: creating ./config.status
config.status: creating Makefile
seems just fine to me. it's just a build- directory in the build
dir...
but then, issuing a make gets me this...
Configuring in build-/libiberty
creating cache ../config.cache
checking whether to enable maintainer-specific portions of Makefiles... no
checking for makeinfo... makeinfo
checking for perl... perl
checking host system type... config.sub: missing argument
Try `config.sub --help' for more information.
checking build system type... config.sub: missing argument
Try `config.sub --help' for more information.
checking for -ar... ar
checking for -ranlib... no
checking for ranlib... ranlib
checking for gcc... gcc
etc.
which I kind of suspect is not what is wanted, right?
Cheers,
/ChJ