From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3222CC433E0 for ; Wed, 6 Jan 2021 07:20:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D88AB23102 for ; Wed, 6 Jan 2021 07:20:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725903AbhAFHU0 (ORCPT ); Wed, 6 Jan 2021 02:20:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46300 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725896AbhAFHU0 (ORCPT ); Wed, 6 Jan 2021 02:20:26 -0500 Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1F6ACC06134D for ; Tue, 5 Jan 2021 23:19:46 -0800 (PST) Received: by mail-ej1-x62b.google.com with SMTP id jx16so3718840ejb.10 for ; Tue, 05 Jan 2021 23:19:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=V3ZcyhwHrSxkFPuIV49eaDr28EF5hgFTj3hRiNXOjj0=; b=V+HnYHkYebrELWqZ1b9qiO4TyvftqwmSuDMW6gD7nRww4SXtaiLjjX5sG7rCz/LQf2 8O4jWoUWM8hILcHF8qp3rGPe9W97qfG6NYZZMOmma7B4b3imfFFUStt4NRx9k3D8q+kL 4+vGCi2MCUm5UlErgdo+xKWePeBkNEFGjZzX81jujWhBdcfSJ7uI7I5Vvb/gYop+dhUE DutPAtIBB68LfNPky3xGZac3L39LnHEa4EKblFskxhwJf2nm/ljXNUGxHn8uiheGA37J CglhcNW9O9Ia+EkifYNk7AxwfHrIFT9YwXLUeno6URXQh2D1EtAOhHDgaQe5uE6BC56U 6KXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=V3ZcyhwHrSxkFPuIV49eaDr28EF5hgFTj3hRiNXOjj0=; b=nqtcPJvVSQJMt4zzwBgQ6i+sjwY8Imkc+rESmrH54ecG3MnMLc58lpsWbEGTZ8u1fd lsFZWwsvM/VkfLG6DJs5yTdSWp/IKso1G8w1m/nE8175xbTfNoxWyfgndkC8g+Y8cXu+ KUNtuUY+As7aZ2NUq/zARogEAgLoK5H1YWujMhhFUtuyUGsM6/aZ4lMbRE0+U7EOgdbp yk6DEzahzkbk/34fmn79acoCpFIJiJw5VllCbjgqc9A6DrVrdDdgIHUvirlpo9to1arA I4O1UVKLsoIoPmLcpPzKqD+lxqlZ6sjnvArmdv03cjf7pj4YPs2UdhBKYSdAwPblmMnT 1qoQ== X-Gm-Message-State: AOAM532warymWpUS9Xh0NLzuBOlrmSSn/UAFpuIBfaBL8C3X6bwrFTOq u9JaIyXFoXJSsAOEehucJgFlTgStnEmA7uMthEnkDw== X-Google-Smtp-Source: ABdhPJya8ovyxTSQgfRGTEyHYMnvFJkA8djK/axhM3YxM1+5VcYH6UGM85c4eGTm7IgmH4/bol6RaKK1kbPYplJ2rOs= X-Received: by 2002:a17:906:5912:: with SMTP id h18mr1961031ejq.261.1609917584945; Tue, 05 Jan 2021 23:19:44 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bartosz Golaszewski Date: Wed, 6 Jan 2021 08:19:34 +0100 Message-ID: Subject: Re: [libgpiod] AC_FUNC_MALLOC cross-compile failure To: Anssi Kolehmainen Cc: Andy Shevchenko , "open list:GPIO SUBSYSTEM" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, Jan 5, 2021 at 8:54 PM Anssi Kolehmainen wrote: > > On Tue, Jan 05, 2021 at 07:24:46PM +0200, Andy Shevchenko wrote: > >On Tue, Jan 5, 2021 at 4:17 PM Anssi Kolehmainen wrote: > >> > >> When libgpiod is cross-compiled it will use rpl_malloc instead malloc which then > >> causes linking failure at later stage. > >> > >> This happens because AC_FUNC_MALLOC wants to execute malloc() in a live system > >> and thus cannot be run at cross-compilation time. libgpiod should just do > >> AC_CHECK_FUNC instead. > > > >Which version of aufotools you tried? (2.69?) > >Btw, have you tried autotools-2.70? > > I have autoconf 2.69 from Debian testing. > > Quick testing with 2.70 looks good. > Apparently fixed in 7fbb55372 in May 2012... And 2.69 is from April 2012. > > I don't know which kind of facepalm would be suitable for this. > > -- > Anssi Kolehmainen IIRC someone suggested this to me a long time ago but since there were no other reports and I mostly just use an SDK generated by yocto which has some workaround for it, I never saw the need for it. I'll apply the patch even if it was fixed in v2.70 because it looks like a valid concern. Bartosz