From: Svante Signell <svante.signell@gmail.com>
Subject: Re: wine-development: FTBFS on hurd-i386
Message-Id: <1448124425.16354.25.camel@gmail.com>
Date: Sat, 21 Nov 2015 17:47:05 +0100
In-Reply-To: <1448046733.16354.9.camel@gmail.com>
References: <1448046733.16354.9.camel@gmail.com>

Signed-off by: svante.signell@gmail.com

Hello,

Submitting this patch directly to wine-patches on request from Jens
Ryer.

BTW: There are still some parts of the code using PATH_MAX, but does
not seem to be triggered with the debian builds. Is it of interest to
remove also the remaining entries?

Thanks!

On Fri, 2015-11-20 at 20:12 +0100, Svante Signell wrote:
> Source: wine-development
> Version: 1.7.55-3
> Severity: important
> Tags: patch
> Usertags: hurd
> User: debian-hurd@lists.debian.org
> 
> Hello,
> 
> Up till 1.7.55-2 wine-development built fine due to the recent
> upstream
> PATH_MAX fixes. Unfortunately, with the enabling of libpulse, the
> PATH_MAX problem arises again. The attached patch use the internally
> used MAX_PATH number, as for other parts of the code. With this patch
> the latest version builds OK too.
> 
> Please forward this upstream, since they are in a code freeze for
> wine-1.8.
> 
> Thanks!

X-Index: wine-development-1.7.55/dlls/winepulse.drv/mmdevdrv.c
===================================================================
--- wine-development-1.7.55.orig/dlls/winepulse.drv/mmdevdrv.c
+++ wine-development-1.7.55/dlls/winepulse.drv/mmdevdrv.c
@@ -440,7 +440,7 @@ static void pulse_probe_settings(int ren
 static HRESULT pulse_connect(void)
 {
     int len;
-    WCHAR path[PATH_MAX], *name;
+    WCHAR path[MAX_PATH], *name;
     char *str;
 
     if (!pulse_thread)
@@ -519,7 +519,7 @@ static void pulse_phys_speakers_cb(pa_co
 static HRESULT pulse_test_connect(void)
 {
     int len, ret;
-    WCHAR path[PATH_MAX], *name;
+    WCHAR path[MAX_PATH], *name;
     char *str;
     pa_operation *o;