All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: add fix for gdb 7.12 and gdb 8.0 build on noMMU platforms
Date: Sat, 5 Aug 2017 14:23:42 +0200	[thread overview]
Message-ID: <20170805142342.027e1232@windsurf> (raw)
In-Reply-To: <4a2a10bc-9516-ddb6-b9b6-9c67038a8339@smile.fr>

Hello,

On Fri, 4 Aug 2017 22:43:26 +0200, Romain Naour wrote:

> > ../nat/linux-ptrace.c: In function 'int linux_fork_to_function(gdb_byte*, int (*)(void*))':
> > ../nat/linux-ptrace.c:273:29: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
> >        child_stack = xmalloc (STACK_SIZE * 4);
> > 
> > The patch has already been merged upstream, as of commit
> > ffce45d2243e5f52f411e314fc4e1a69f431a81f, and will therefore be part
> > of future gdb releases.  
> 
> What's the arch/config are you using?

This was happening on m68k Coldfire, if i remember correctly.

> It's seems no toolchain able to build gdb on noMMU case are present in the
> autobuilder.

We have a m68k Coldfire configuration in the autobuilders. However, the
pre-built toolchain is built without BR2_PTHREAD_DEBUG, and therefore
the target gdb is never built because it depends on
BR2_TOOLCHAIN_HAS_THREADS_DEBUG.

Best regards,

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

  reply	other threads:[~2017-08-05 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  7:15 [Buildroot] [PATCH] gdb: add fix for gdb 7.12 and gdb 8.0 build on noMMU platforms Thomas Petazzoni
2017-08-04 20:43 ` Romain Naour
2017-08-05 12:23   ` Thomas Petazzoni [this message]
2017-08-05 20:14     ` Romain Naour
2017-08-10  9:25 ` Arnout Vandecappelle
2017-08-10 12:23   ` Thomas Petazzoni
2017-09-05 21:45 ` 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=20170805142342.027e1232@windsurf \
    --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 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.