From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116964 invoked by alias); 9 Nov 2019 16:04:41 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 116954 invoked by uid 89); 9 Nov 2019 16:04:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=multilib, incredibly X-HELO: einhorn-mail.in-berlin.de Received: from einhorn-mail.in-berlin.de (HELO einhorn-mail.in-berlin.de) (217.197.80.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 09 Nov 2019 16:04:40 +0000 X-Envelope-From: doko@ubuntu.com Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id xA9G4Zjk029501 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 9 Nov 2019 17:04:35 +0100 Subject: Re: libffi 3.3 release candidate 1 To: Anthony Green Cc: libffi-discuss References: From: Matthias Klose Message-ID: <288adc9e-ad74-7813-eed8-e94dcb4e185f@ubuntu.com> Date: Sat, 09 Nov 2019 16:04:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00058.txt.bz2 On 08.11.19 15:27, Anthony Green wrote: > Thanks, Matthias, this is incredibly helpful. > > For ecl, it looks like they are using FFI_UNIX64 on the 32-bit x86, and > similar for amd64. This is easy to fix, and I'll submit a patch to > upstream ecl. > > The arm64 failures are mysterious runtime failures. The libffi test > results for arm64 are good, so I'm wondering if the debian package adds any > patches. no patches. > The jffi failures all look like this: > > [exec] make[2]: *** No rule to make target '-L/usr/lib/../lib', > needed by '/<>/build/jni/jffi/LongDouble.o'. Stop. > > Perhaps this has something to do with how libffi is installed now? > Regardless, it's probably easy to fix whatever it is. libffi has in the pkg-config file: Libs: -L/usr/lib/../lib Normally pkg-config filters out system directories, but apparently fails for noncanonical paths. And jffi only expects libs. So something packagers should catch, unless you want to remove all the multilib build support, but I'm still awaiting your libffi merge for GCC 10 ;) > The arm64 failures seem like a blocker for the release, which I'm still > hoping to get out on Nov 12. haskell-stack haskell-termonad are the remaining regressions, but I'm not sure if they are related at all. Matthias