Where is thus stuff coming from?

[Ian Pilcher <i.pilcher@xxxxxxxxxxx>]

I'm trying to build an RPM of the latest version of WINE on Fedora Core
4.  If I simply untar the source, export CC=gcc32, ./configure, make,
the configure script completes and the build begins.  (I.e. things work
as expected.)

When I try to do the same thing within RPM, however, the configure
script dies.

Here are the relevant sections of the SPEC file:

  %prep
  %setup -q -n wine-%{version}
  #%patch0 -p1 -b .stabs+
  #%patch1 -p1 -b .nvidia-opengl
  #%patch2 -p1 -b .generated

  %build
  export CC=gcc32
  #export CFLAGS="$RPM_OPT_FLAGS"
  #autoconf
  #%configure \
  #	--sysconfdir=%{_sysconfdir}/wine
  ./configure

From my understanding of the way RPM works, this should essentially be
identical to the "standalone" process.  What I'm getting, however, is
very different:

Executing(%build): /bin/sh -e /home/pilcher/rpm/tmp/rpm-tmp.64720
+ umask 022
+ cd /home/pilcher/rpm/BUILD
+ cd wine-20050628
+ LANG=C
+ export LANG
+ unset DISPLAY
+ export CC=gcc32
+ CC=gcc32
+ CFLAGS='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 
-march=i386 -mtune=pentium4 -fasynchronous-unwind-tables'
+ export CFLAGS
+ CXXFLAGS='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 
-march=i386 -mtune=pentium4 -fasynchronous-unwind-tables'
+ export CXXFLAGS
+ FFLAGS='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 
-march=i386 -mtune=pentium4 -fasynchronous-unwind-tables'
+ export FFLAGS
++ find . -name config.guess -o -name config.sub
+ for i in '$(find . -name config.guess -o -name config.sub)'
++ basename ./tools/config.guess
+ '[' -f /usr/lib/rpm/redhat/config.guess ']'
+ /bin/rm -f ./tools/config.guess
++ basename ./tools/config.guess
+ /bin/cp -fv /usr/lib/rpm/redhat/config.guess ./tools/config.guess
`/usr/lib/rpm/redhat/config.guess' -> `./tools/config.guess'
+ for i in '$(find . -name config.guess -o -name config.sub)'
++ basename ./tools/config.sub
+ '[' -f /usr/lib/rpm/redhat/config.sub ']'
+ /bin/rm -f ./tools/config.sub
++ basename ./tools/config.sub
+ /bin/cp -fv /usr/lib/rpm/redhat/config.sub ./tools/config.sub
`/usr/lib/rpm/redhat/config.sub' -> `./tools/config.sub'
+ ./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu 
--target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr 
--exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
--sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include 
--libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var 
--sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking whether make sets $(MAKE)... yes
checking for i686-redhat-linux-gnu-gcc... gcc32
checking for C compiler default output file name... configure: error: C 
compiler cannot create executables
See `config.log' for more details.

(In contrast, when I run ./configure manually, the output begins with
"checking build system type...".)

So what the heck is setting all of those environment variables and
adding all that junk to the configure command line?

TIA

--
========================================================================
Ian Pilcher                                        i.pilcher@xxxxxxxxxxx
========================================================================