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

[pkg-wine-party] Bug#833956: marked as done (wine-development: FTBFS on hurd-i386 and kfreebsd-i386)



Your message dated Mon, 22 Aug 2016 17:25:27 +0000
with message-id <E1bbsyV-0007ZH-7D@franck.debian.org>
and subject line Bug#833956: fixed in wine-development 1.9.17-1
has caused the Debian Bug report #833956,
regarding wine-development: FTBFS on hurd-i386 and kfreebsd-i386
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.)


-- 
833956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833956
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wine-development
Version: 1.9.15-1
Severity: normal
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
User: debian-hurd@lists.debian.org
Usertags: hurd


[ I hope I got the CC and tags right, first time I look into a
  portability issue. ]


Hi,

src:wine-development since 1.9.15-1 fails to build on hurd-i386
and kfreebsd-i386. It built successfully before.

The later uploaded src:wine 1.8.3-3 still builds successfully.

Build log for hurd-i386:
https://buildd.debian.org/status/fetch.php?pkg=wine-development&arch=hurd-i386&ver=1.9.15-1&stamp=1469253468

Build log kfreebsd-i386:
https://buildd.debian.org/status/fetch.php?pkg=wine-development&arch=kfreebsd-i386&ver=1.9.15-1&stamp=1469253097
~~~~~
gcc -c -o virtual.o virtual.c -I. -I../../include -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall \
  -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \
  -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith \
  -Wlogical-op -gdwarf-2 -gstrict-dwarf -fno-omit-frame-pointer -Werror -Wdate-time -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wno-error
virtual.c: In function 'virtual_get_system_info':
virtual.c:1363:20: error: storage size of 'sinfo' isn't known
     struct sysinfo sinfo;
                    ^
virtual.c:1372:10: warning: implicit declaration of function 'sysinfo' [-Wimplicit-function-declaration]
     if (!sysinfo(&sinfo))
          ^
virtual.c:1363:20: warning: unused variable 'sinfo' [-Wunused-variable]
     struct sysinfo sinfo;
                    ^
Makefile:711: recipe for target 'virtual.o' failed
~~~~~



I assume (not tested) this is because of:

commit d0832cdf428696e2c08b1aa27382baad4d1e376f
Author: Michael Müller <michael@fds-team.de>
Date:   Fri Jul 8 05:40:22 2016 +0200

    ntdll: Use sysinfo to report correct number of physical pages.

    Signed-off-by: Michael Müller <michael@fds-team.de>
    Signed-off-by: Sebastian Lackner <sebastian@fds-team.de>
    Signed-off-by: Alexandre Julliard <julliard@winehq.org>

http://source.winehq.org/git/wine.git/commitdiff/d0832cdf428696e2c08b1aa27382baad4d1e376f



The code is only called conditionally (ifdef HAVE_SYS_SYSINFO_H).

It has "include <sys/sysinfo.h>", which is provided in:
/usr/include/i386-gnu/sys/sysinfo.h           libc0.3-dev [hurd-i386] 
/usr/include/i386-kfreebsd-gnu/sys/sysinfo.h  libc0.1-dev [kfreebsd-i386] 

However "totalram" and "mem_unit" are only in:
/usr/include/linux/sysinfo.h                  linux-libc-dev

So sysinfo.h exists on hurd/kfreebsd, but doesn't provide everything
necessary!? Is there a fix for this, or should we disable this code
on hurd/kfreebsd explicitly? Or am I on a completely wrong track here?
Patches welcome, otherwise I'll ask upstream.

I found a similar (not identical) issue in busybox:
https://bugs.debian.org/677254.
Fix:
https://git.busybox.net/busybox/commit/?id=ac42e3de90ebf4b921035893e3670da63cad882c

Greets
jre

--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 1.9.17-1

We believe that the bug you reported is fixed in the latest version of
wine-development, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 833956@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jens Reyer <jre.winesim@gmail.com> (supplier of updated wine-development package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 22 Aug 2016 15:08:33 +0200
Source: wine-development
Binary: wine-development wine32-development wine64-development wine32-development-preloader wine64-development-preloader wine32-development-tools wine64-development-tools libwine-development libwine-development-dev
Architecture: source
Version: 1.9.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party <pkg-wine-party@lists.alioth.debian.org>
Changed-By: Jens Reyer <jre.winesim@gmail.com>
Description:
 libwine-development - Windows API implementation - library
 libwine-development-dev - Windows API implementation - development files
 wine-development - Windows API implementation - standard suite
 wine32-development - Windows API implementation - 32-bit binary loader
 wine32-development-preloader - Windows API implementation - prelinked 32-bit binary loader
 wine32-development-tools - Windows API implementation - 32-bit developer tools
 wine64-development - Windows API implementation - 64-bit binary loader
 wine64-development-preloader - Windows API implementation - prelinked 64-bit binary loader
 wine64-development-tools - Windows API implementation - 64-bit developer tools
Closes: 832129 833956
Changes:
 wine-development (1.9.17-1) unstable; urgency=medium
 .
   * New upstream release 1.9.17, released Aug 19, 2016.
     - Better exception handling on 64-bit.
     - Various improvements in joystick support.
     - Some more stream support in the C++ runtime.
     - Font embedding improvements.
     - More metafile support in GDI+.
     - Various bug fixes.
     - Check for sysinfo function to fix FTBFS on hurd and kfreebsd
       (closes: #833956). Thanks Pino Toscano and Sebastian Lackner.
     - Correct wrong symlink in wine.inf to fix regedit exporting the
       registry (closes: #832129). Thanks Joerg Schiermeier.
   * Refresh patches.
   * Make "update-alternatives --remove" quiet.
   * Make libc6-dev dependency portable.
Checksums-Sha1:
 e498f98cb6335f5ba64737e496cb9a26a0ab2367 3810 wine-development_1.9.17-1.dsc
 0d2302fd120c41f15fbea3645755037f24ef36d2 23006436 wine-development_1.9.17.orig.tar.bz2
 b695754e09fc38768561f103a400573d11cfa087 177668 wine-development_1.9.17-1.debian.tar.xz
Checksums-Sha256:
 de756586548193fda9d23d77cf47aaf14b32888ca547164d1b7a02ab1f94022c 3810 wine-development_1.9.17-1.dsc
 45fc9c9e59b3208c4b2ceb7173edc6c5926de77c6d86a8bea4d79db8ac88716c 23006436 wine-development_1.9.17.orig.tar.bz2
 ebb9f0adcf6e661480a2274551893385313f6896cc09878eb083728d61707eed 177668 wine-development_1.9.17-1.debian.tar.xz
Files:
 6fc31749a63b2853425d198d83fef716 3810 otherosfs optional wine-development_1.9.17-1.dsc
 2dcb2566472faf04fa62190770f0d9ca 23006436 otherosfs optional wine-development_1.9.17.orig.tar.bz2
 050cb0f131c16d83425f35167de2f1ee 177668 otherosfs optional wine-development_1.9.17-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXux5pAAoJEGCEEgMrVzB2MnwP/RuTYCsjAFwTAkc3QaW6yzNJ
k3CHJ3SVxa9/GZ3HYBeQT8VMNX+fSQGs+hLsugGHV6dJvhleYLI9fuQZH0oqeAdQ
NpIN5jUJlBIkpf4uquf0TUJEOTM9NhFVrmlbJarmnKYbUQKm40jxFu9cdM9Y1WfZ
IWNXjeQK4JaoCW07KKWOSA/vYvpa2vAvoUr7YVZ6N9hOP6DjO4E5bxaV4qbKTVWb
PSEstq74wOUIu4xeaTH+1YuHTQAH3ZirRdoPfXtHmvNECvy7dAAZsRft1Dvx4CFE
W151EM+UyzeeUguyvyHRQ3JrSARuafwMtxuqgdYz+tUNe7jryCSdTuIbcjvX3lLY
fKfVyPmO+oQtzJJuNC1RnCtwePGlav7pAnJ+cvd1ekShvZM6P6obVcG6hsvsZz0y
A1Gy+eTDHKm8+l9tp401M9XordtVoBqQqQq9dMu23HYMQaBua9NHF2Z917VYBgsL
RYbIkBP82zncd9MGeNwoKLk1RzGUPE9dSyfyis51L2qXtgl/VEqRa1PnMCt0PP9C
Tf+UB2oC/OXjg/5R86Jh9cYBBXTgvKKlCnIgbiP1nvzeWbLHP/8i2eOt+/+rppqp
N9fqJabvDTM1ZcC50KvV4zQCnh/6/PNP95NANPKAhVCvFu1XtV8fh0DdvEtfCHv1
a4dSedEz7XEU6uJogk/F
=g8Dy
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: