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: Thu, 30 Jun 2016 18:08:39 +0200	[thread overview]
Message-ID: <20160630160839.GA12940@archie.localdomain> (raw)
In-Reply-To: <20160630071018.GD18320@pengutronix.de>

On Thu, Jun 30, 2016 at 09:10:18AM +0200, m.olbrich@pengutronix.de wrote:
> I've pushed this (with the extra ')') to master.
> 
> Have you noticed anything else? I'll probably create a stable release for
> this. It would be great if I got some feedback if there are anny other
> issues that should be fixed.

Looks good to me!

--

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?

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2016-06-30 16:08 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 [this message]
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
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=20160630160839.GA12940@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