All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ltrace: disable on mips/mipsel
Date: Thu, 14 Aug 2014 18:42:22 +0100	[thread overview]
Message-ID: <53ECF4FE.3060308@imgtec.com> (raw)
In-Reply-To: <1408038104-9440-1-git-send-email-thomas.petazzoni@free-electrons.com>

On 08/14/2014 06:41 PM, Thomas Petazzoni wrote:
> ltrace currently doesn't build on mips/mipsel, and it's an upstream
> issue that has been reported. Until it get fixed, let's disable ltrace
> for mips/mipsel.
>
> Fixes:
>
>    http://autobuild.buildroot.org/results/43a/43a8fc7075f52eab74ebfee4c9f25dd2b886e75e/
>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>   package/ltrace/Config.in | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/package/ltrace/Config.in b/package/ltrace/Config.in
> index 4d1acfa..8cabfa2 100644
> --- a/package/ltrace/Config.in
> +++ b/package/ltrace/Config.in
> @@ -1,6 +1,10 @@
>   config BR2_PACKAGE_LTRACE
>   	bool "ltrace"
> -	depends on (BR2_i386 || BR2_arm || BR2_mips || BR2_mipsel \
> +	# ltrace normally has mips/mipsel support, but it's currently
> +	# broken (error: 'struct ltelf' has no member named
> +	# 'relplt_count'). Issue reported upstream at
> +	# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756764.
> +	depends on (BR2_i386 || BR2_arm \
>   		|| BR2_powerpc || BR2_sparc || BR2_x86_64)
>   	select BR2_PACKAGE_LIBELF
>   	select BR2_PACKAGE_ELFUTILS
>

Thanks Thomas.

-- 
Vincent

  reply	other threads:[~2014-08-14 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 17:41 [Buildroot] [PATCH] ltrace: disable on mips/mipsel Thomas Petazzoni
2014-08-14 17:42 ` Vicente Olivert Riera [this message]
2014-08-15  8:14 ` Peter Korsgaard

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=53ECF4FE.3060308@imgtec.com \
    --to=vincent.riera@imgtec.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 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.