From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2013.08.0 released
Date: Tue, 20 Aug 2013 11:28:39 +0200 [thread overview]
Message-ID: <32883ccbfb6f0bd3bb38ff0507681c8b@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20130816131211.GG29492@pengutronix.de>
Hei hei,
Am 2013-08-16 15:12, schrieb Michael Olbrich:
>> I guess this is commit 51c5786c16a9a3508af9b6cc69947a2f3b8bc7cf and it
>> causes the *.in files in my platforms folder to be ignored. So I have
>> two files in my platforms folder in my BSP overwriting one rule from
>> ptxdist platforms folder and adding another one. These are ignored with
>> the current release so the entries defined there do not appear in
>> platformconfig menu. :-/
>>
>> Can someone confirm this?
>
> Are these *.in files hosttools? In that case take a look at the commit.
> They now need a "## SECTION=hosttools_platform" header.
No they are not. It's especially at91bootstrap.in and another boot
loader related rule. I tested the patch Bernhard Walle posted on Friday
afternoon. It addresses the very same changeset and it fixes my problem.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-08-20 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 17:52 Marc Kleine-Budde
2013-08-13 9:28 ` Alexander Dahl
2013-08-16 13:12 ` Michael Olbrich
2013-08-20 9:28 ` Alexander Dahl [this message]
2013-08-17 10:18 ` Stephan Linz
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=32883ccbfb6f0bd3bb38ff0507681c8b@idefix.lespocky.dyndns.org \
--to=post@lespocky.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