If the patch is applied, the libtoolize tool has populated m4/* and you've
regenerated the aclocal.m4 with aclocal, the configure and Makefile.in, then it
should suffice, yes.
I am more than willing to send you my spec file for you to look at and
can also attach instructions on how to try to build this from source if
you wish - just let me know. But it definitely isn't working!
That's what I understood, however this is an easy case as most x86_64 build
systems I know can support i686 executables if the necessary libraries are
installed, and I found this particular situation (build for i686 on x86_64) to
be particularly convenient on Fedora.
That's not the point. The point is to build a clean i686 package, which
is free from any build-machine-arch dependencies (like libgc-x86_64
etc). With the patch I attached (which even though quite basic and
rudimentary) this is done, though I think a better solution needs to be
found.
I think you could. ./configure CC="gcc -m32" would normally do, but I haven't
gotten around to test drive things on F14.
The arch-dependent flags (line -mXX, -mtune etc) are handled
'automatically' when I specify the --target parameter (i.e.
--target=i686 'automatically' sets a bunch of CCFLAGS/LDFLAGS which are
arch-dependent) - these are stored in a pretty standard way through 1)
the appropriate environment variables (CCFLAGS, LDFLAGS etc); and 2) via
the Makefile generated after ./configure is run/executed.
This works for 99% of all cases, except where the appropriate CCFLAGS or
LDFLAGS are hard-coded (which is very bad program practice by the way)
in a propriety Makefile as is the case with the OpenVPN plugins.
Well, for patch testing that's the thing. For the next releases, we'll have to
wait what James, David, Samuli decide.
So be it then.
