On Mon, Nov 10, 2008 at 09:54:04PM +0100, Farkas Levente wrote:
Daniel P. Berrange wrote:
On Mon, Nov 10, 2008 at 07:28:06PM +0000, Daniel P. Berrange wrote:
./configure --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu \ --target=x86_64-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/lib64 \ --libexecdir=/usr/libexec \ --localstatedir=/var \ --sharedstatedir=/usr/com \ --mandir=/usr/share/man \ --infodir=/usr/share/info
But for mingw,its only defining the --prefix
./configure \ --build=x86_64-unknown-linux-gnu --host=i686-pc-mingw32 --target=i686-pc-mingw32 \ --prefix=/usr/i686-pc-mingw32/sys-root/mingw
We need to fix %_mingw32_configure macro to work the same way as the native macro & thus not rely on unpredictable autoconf defaults which vary depending on what version of autoconf the upstream app happened to generate their configure script with.
ok but which one? there is a mingw32-configure.sh and also there is a %_mingw32_configure macro in /etc/rpm/macros.mingw32. why these two different place, it's redundant. does it really needed?
The 'mingw32-configure.sh' shell script in /usr/bin is for developers who are doing builds outside the context of RPMs. As such it should only set the minimal possible args to cross-compile. It should not apply RPM packaging policy. So we don't need to change mingw32-configure.sh
Just the %_mingw32_ocnfigure macro definition whose purpose is to apply RPM packaging policy such as man page in /usr/share/man
Regards, Daniel