[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#639886: marked as done (FTBFS: standard includes have been moved from /usr/lib/* to /usr/bin/{arch directory}/*)



Your message dated Wed, 31 Aug 2011 20:13:01 +0200
with message-id <4E5E79AD.2080407@arcticnet.no>
and subject line Re: [pkg-wine-party] Bug#639886: FTBFS: standard includes have been moved from /usr/lib/* to /usr/bin/{arch directory}/*
has caused the Debian Bug report #639886,
regarding FTBFS: standard includes have been moved from /usr/lib/* to /usr/bin/{arch directory}/*
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
639886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639886
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wine
Version: 1.1.24
Justification: fails to build from source
Severity: serious

I did apt-get build-dep wine, apt-get source wine and then make depend
produces the error below.

Similarly, I had previously been tracking the wine git and building
regularly and recently that stopped working with the same error.

I believe the problem is that a recent upgrade of libc dev files moved
various standard library includes into arch specific sub directories for
multiarch support.

--------
$ make depend
make[1]: Entering directory `/home/sammy/src/wine-debian/wine-1.1.24/tools'
gcc -m32 -c -I. -I. -I../include -I../include -I/usr/include/freetype2
-Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement
--Wwrite-strings -Wtype-limits -Wpointer-arith  -g -O2  -o makedep.o
--makedep.c
In file included from /usr/include/bits/errno.h:25:0,
                 from /usr/include/errno.h:36,
                 from makedep.c:27:
/usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or
directory
compilation terminated.
make[1]: *** [makedep.o] Error 1
make[1]: Leaving directory `/home/sammy/src/wine-debian/wine-1.1.24/tools'
make: *** [tools/makedep] Error 2
--------

I do remember seeing a message about a week ago as part of a full-upgrade
mentioning a need to change include directories in non-debian build setups,
but I'm not sure how to find it again. I've looked through the changelogs of
all the relevant-sounding packages I can find and I found the following:

--------
linux-2.6 (3.0.0-2) unstable; urgency=high
[...]
  [ Ben Hutchings ]
  * linux-libc-dev: Install include/asm under arch-specific directory
    (thanks to Aurelien for correcting the directory); mark package as
    multi-arch-coinstallable (Multi-Arch: same)
--------

and this appears to be the change indicated here, based on the timing of the
error appearing.

So, it seems to me that either (a) wine needs to look in a different
directory (include the arch specific directory in the include path) or (b)
there needs to be some sane default set of includes in the non-arch-specific
directory (which set of includes might not be obvious on a multi-arch system
such as an amd64 system...)


I hope this is helpful and that wine will be buildable soon

Cheers & God bless
    Sam "SammyTheSnake" Penny

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
Den 31. aug. 2011 12:27, skrev sam penny:
Package: wine
Version: 1.1.24
Justification: fails to build from source
Severity: serious

No such version in Debian, closing. (The 1.1.24 in Debian was called wine-unstable 1.1.24-1. Obviously this is not that version.)

So, it seems to me that either (a) wine needs to look in a different
directory (include the arch specific directory in the include path) or (b)
there needs to be some sane default set of includes in the non-arch-specific
directory (which set of includes might not be obvious on a multi-arch system
such as an amd64 system...)

...in which case Wine shouldn't need to do or change anything.


--- End Message ---

Reply to: