From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2016.06.0 released
Date: Fri, 1 Jul 2016 08:33:29 +0200 [thread overview]
Message-ID: <20160701063329.GJ18320@pengutronix.de> (raw)
In-Reply-To: <20160630160839.GA12940@archie.localdomain>
On Thu, Jun 30, 2016 at 06:08:39PM +0200, Clemens Gruber wrote:
> There is only one longstanding issue, which is probably a ptxdist
> problem but it is occuring during the toolchain build as well:
> The problem seems to be that some _MD5 lines are removed from the config
> during clean or at other stages of the build and are then missing if
> built again.
> For example PTXCONF_GLIBC_HEADERS_MD5, PTXCONF_GLIBC_CRT_MD5, etc.
> After ptxdist clean, only PTXCONF_GLIBC_MD5="..." remains and I have to
> manually add all other variations for the build to succeed.
>
> I also experienced this problem when building gdbserver in my BSP:
> I have to manually add a PTXCONF_GDBSERVER_MD5="" line for ptxdist
> targetinstall gdbserver --update-md5 to succeed. It gets removed by
> ptxdist again later on. Only PTXCONF_GDB_MD5=".." remains and if I now
> enter ptxdist clean gdbserver && ptxdist targetinstall gdbserver, the
> build fails again, until I add PTXCONF_GDBSERVER_MD5=".." to the
> ptxconfig.
>
> Can you reproduce this?
You're saying, that PTXdist modifies the ptxconfig when you run 'ptxdist
clean gdbserver'? I've never seen anything like this. Can you create a
minimal BSP that has this problem and send it to me?
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
next prev parent reply other threads:[~2016-07-01 6:33 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 [this message]
2016-07-01 8:39 ` Clemens Gruber
2016-07-01 10:28 ` Michael Olbrich
2016-07-01 14:25 ` Clemens Gruber
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=20160701063329.GJ18320@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