--- On Sun, 15/2/09, Ben Klein <shacklein(a)gmail.com> wrote:
2009/2/15 Hin-Tak Leung <hintak_leung(a)yahoo.co.uk>:
--- On Sun, 15/2/09, Ben Klein
<shacklein(a)gmail.com> wrote:
2009/2/15 Hin-Tak Leung
<hintak_leung(a)yahoo.co.uk>:
I have no idea why suddenly at wine 1.1.15 it requires the x86_64-redhat-linux-{as,ld,nm} form of the binutils tools. It seems to treat x86_64 suddenly as a cross-compiling environment.
Are you sure nothing in the build environment just happened to change in the last 2 weeks or so?
Well, I do my weekly fedora update, so a few hundred MB changes weekly. Given that this problem happens with both Debian/Ubuntu systems and fedora, this week... and I have had my rpmbuild system working smoothly for about a year...
If I am going to guess, I think the change has something to do with cross-compiling, instead of just the occasional -m32 .
scguy318 just brought this to my attention on IRC: http://bugs.winehq.org/show_bug.cgi?id=17340
Argh... the original reporter of that bug seems to be rather mistaken - there is no need to have a separate cross-compile tool chain on 64-bit fedora (which I am also using) to build 32-bit applications. Just passing -m32 to both the compiler (CFLAGS for c , CXXFLAGS for c++ code and FFLAGS for fortrans) and the linker (LDFLAGS) would do. So to make it work for one person's peculiar build environment, everybody else's normal environment has to break...