All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Anssi Kolehmainen <anssi@aketzu.net>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod] AC_FUNC_MALLOC cross-compile failure
Date: Wed, 6 Jan 2021 08:19:34 +0100	[thread overview]
Message-ID: <CAMRc=Mfq+e9CGqXZiTSh-fZfQxVfBzsi+VHSX4OEM49gG+1fKg@mail.gmail.com> (raw)
In-Reply-To: <X/TDYJYMRo7hEAoR@kelvin.aketzu.net>

On Tue, Jan 5, 2021 at 8:54 PM Anssi Kolehmainen <anssi@aketzu.net> 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 <anssi@aketzu.net> 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

  reply	other threads:[~2021-01-06  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 14:09 [libgpiod] AC_FUNC_MALLOC cross-compile failure Anssi Kolehmainen
2021-01-05 17:24 ` Andy Shevchenko
2021-01-05 19:52   ` Anssi Kolehmainen
2021-01-06  7:19     ` Bartosz Golaszewski [this message]
2021-01-06  7:21 ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMRc=Mfq+e9CGqXZiTSh-fZfQxVfBzsi+VHSX4OEM49gG+1fKg@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=andy.shevchenko@gmail.com \
    --cc=anssi@aketzu.net \
    --cc=linux-gpio@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.