Roderick Colenbrander wrote:
1.1.15 fails to build using an identical layout to 1.1.14, which means something has changed with either the build dependencies or the way configure is working.
Here's the build failure I'm getting on amd64, but it fails on all arches: http://launchpadlibrarian.net/22606029/buildlog_ubuntu-intrepid-amd64.wine_1...
I'm going to sleep now, but hopefully I'll figure this out Valentine's day. In the meanwhile, 1.1.15 won't be available in Ubuntu packages just yet.
Thanks, Scott Ritchie
A packager of a debian based distro reported the same issue. They are doing: CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=$${prefix}/share/man --infodir=$${prefix}/share/info $(CONFFLAGS)
Where the two DEB_* variables are: DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
When building 32-bit packages DEB_HOST_GNU_TYPE is set to i486-linux-gnu and this results in 'i486-linux-gnu-as not found'.
Personally I consider it a misconfigured build system. It can be fixed by installing the proper binutils package for this architecture which I'm sure debian has. The same should be done for your ubuntu packages. You can't expect apps to build if you only have one half of the build apps (the compiler).
Roderick
I've tried manually build-depending on the binutils and binutils-multiarch packages, however neither fix the build failure. I'm not quite sure what I'm looking for here.
Thanks, Scott Ritchie