Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/freeswitch: enable video support
Date: Fri, 10 Jun 2016 00:35:03 +0200	[thread overview]
Message-ID: <20160610003503.7ebe8f20@free-electrons.com> (raw)
In-Reply-To: <1461445358-32052-1-git-send-email-bernd.kuhls@t-online.de>

Hello,

On Sat, 23 Apr 2016 23:02:38 +0200, Bernd Kuhls wrote:

> +# needed in addition for patch 0003 for cross-compiling libs/libvpx
> +ifeq ($(BR2_TOOLCHAIN_EXTERNAL),y)
> +# host/opt/ext-toolchain/bin/ is not part of $PATH, instead of passing

And this is intentional, because you should never call binaries in
host/opt/ext-toolchain/bin/.

> +# GNU_TARGET_NAME we need to pass TOOLCHAIN_EXTERNAL_CROSS which stores
> +# the full path, needed to avoid build error with external toolchains,
> +# quote from compile log:
> +#    [AR] libvpx_g.a
> +# make[3]: x86_64-buildroot-linux-musl-ar: Command not found
> +# or
> +# make[3]: sparc64-buildroot-linux-gnu-ar: Command not found
> +FREESWITCH_MAKE_ENV += CROSS=$(TOOLCHAIN_EXTERNAL_CROSS)
> +else
> +FREESWITCH_MAKE_ENV += CROSS=$(GNU_TARGET_NAME)-
> +endif

Have you tried replacing this complicated stuff with just:

   FREESWITCH_MAKE_ENV += CROSS=$(TARGET_CROSS)

$(TARGET_CROSS) is already defined properly depending on
internal/external.

Could you check if that works and submit an updated version?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-06-09 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23 21:02 [Buildroot] [PATCH v2 1/1] package/freeswitch: enable video support Bernd Kuhls
2016-06-09 22:35 ` Thomas Petazzoni [this message]
2016-06-09 22:39   ` Yann E. MORIN
2016-06-10  4:57     ` Bernd Kuhls

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=20160610003503.7ebe8f20@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox