mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Failed to compile gdbserver
Date: Tue, 9 Oct 2018 12:45:39 +0200	[thread overview]
Message-ID: <20181009104539.6csixlwck2z6tyvx@pengutronix.de> (raw)
In-Reply-To: <228b1c6d087e75cb500308dbff7a8d0baa231e4e.camel@cn-eng.de>

On Sat, Sep 29, 2018 at 03:19:45PM +0200, Andreas Pretzsch wrote:
> On Mon, 2018-07-30 at 13:44 +0200, Michael Olbrich wrote:
> > On Mon, Jul 30, 2018 at 11:29:04AM +0000, Denis OSTERLAND wrote:
> > > I try to compile gdbserver with OSELAS.Toolchain-2018.02.0 on
> > > armv5te + armv7a, but it fails.
> > > I tried the default version 7.6.1:
> 
> Just hit me too, same setup.
> Well, with ptxdist-2018.09, but same topic.
> 
> 
> > You need to use the same version as the gdb in the toolchain. That's
> > 8.1, if I remember correctly.
> 
> Correct, there gdb 8.1 is used. Build is successful with
> PTXCONF_GDB_VERSION="8.1"
> PTXCONF_GDB_MD5="0c85ecbb43569ec43b1c9230622e84ab"
> 
> 
> Might be worth to check this, like it's done with gcc and glibc.
> Their versions are set in platformconfig (and checked), in this case:
> PTXCONF_CROSSCHAIN_CHECK="7.3.1"
> PTXCONF_GLIBC_VERSION="2.27"
> And so kind of centralizing toolchain version dependencies.
> 
> But gdb version (which gdbserver follows) is set in ptxconfig, as
> PTXCONF_GDB_VERSION and PTXCONF_GDB_MD5. Where it belongs to, as those
> are installed to the target. Either gdbserver or even full gdb.
> 
> Thinking of ways to improve this, I could imagine
> 
> 1.) keep PTXCONF_GDB_* in ptxconfig, but add some "use version from
> toolchain" config flag, which will in turn take the data setup in
> platformconfig (probably new options there)

I've implemented something like this:
For an OSELAS.Toolchain it will now fetch the version and md5 from the
toolchain ptxconfig. The md5 can be overwritten if necessary.
For all other toolchains <prefix>-gdb --version is parsed and the md5 must
be specified.
This is all optional, the old way to specify version and md5 can be used
too.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-10-09 10:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 11:29 Denis OSTERLAND
2018-07-30 11:44 ` Michael Olbrich
2018-07-30 11:56   ` Denis OSTERLAND
2018-09-29 13:19   ` Andreas Pretzsch
2018-10-09 10:45     ` Michael Olbrich [this message]

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=20181009104539.6csixlwck2z6tyvx@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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