mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2016.06.0 released
Date: Fri, 1 Jul 2016 16:25:54 +0200	[thread overview]
Message-ID: <20160701142554.GA846@archie.localdomain> (raw)
In-Reply-To: <20160701102850.GM18320@pengutronix.de>

On Fri, Jul 01, 2016 at 12:28:50PM +0200, Michael Olbrich wrote:
> Now I get it. You cannot update the md5sum for gdbserver with
> '--update-md5'. You need to do it manually. gdb and gdbserver share the
> md5sum and the kconfig symbol is PTXCONF_GDB_MD5. Run
> "md5sum /home/clemens/shared-src/gdb-7.11.1.tar.gz" and enter the result in
> 'ptxdist menuconfig' or edit the ptxconfig manually to update
> PTXCONF_GDB_MD5.

Hm, OK, I am entering it manually now, but would this be hard to
implement in ptxdist to automatically set a kconfig symbol if it does
not exist yet?
Same problem appears when updating toolchain components.

And why is the PTXCONF_GDBSERVER_MD5 kconfig symbol removed from ptxconfig when
leaving ptxdist menu?

Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-07-01 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 12:10 Michael Olbrich
2016-06-22 13:22 ` Clemens Gruber
2016-06-22 13:34   ` Clemens Gruber
2016-06-22 14:43   ` Michael Olbrich
2016-06-28 12:58     ` Bruno Thomsen
2016-06-30  7:10       ` m.olbrich
2016-06-30  7:48         ` Ladislav Michl
2016-06-30 14:07           ` Michael Olbrich
2016-06-30 16:08         ` Clemens Gruber
2016-07-01  6:33           ` Michael Olbrich
2016-07-01  8:39             ` Clemens Gruber
2016-07-01 10:28               ` Michael Olbrich
2016-07-01 14:25                 ` Clemens Gruber [this message]
2016-07-04  6:35                   ` Michael Olbrich
2016-07-04 15:47                     ` Clemens Gruber

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=20160701142554.GA846@archie.localdomain \
    --to=clemens.gruber@pqgruber.com \
    --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