mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andreas Geisenhainer <Andreas.Geisenhainer@atsonline.de>
To: barebox@lists.infradead.org
Subject: Re: bareboxenv - tricky ptxdist behavior
Date: Wed, 27 May 2015 10:05:23 +0200	[thread overview]
Message-ID: <55657AC3.3040609@atsonline.de> (raw)
In-Reply-To: <20150527064145.GO6325@pengutronix.de>

On 27/05/15 08:41 AM, Sascha Hauer wrote:
> Hi Alexander,
>
> On Tue, May 26, 2015 at 11:50:39AM +0200, Alexander Richter wrote:
>> Hallo,
>>
>> I just used bareboxenv tool in linux userspace after a long
>> troublesome trip through ptxdist.
>> That would not have to be, if the description of "build bareboxenv
>> tool for target" in barebox config has said, that i has to enable
>> the tool  platformconfig.
> Is there a "in" missing in the sentence above? There is a platformconfig
> in ptxdist, but this is a file or a ptxdist subcommand, not a tool.
> Could you clarify what your problem was? I do not really understand.

Let me pitch in here.

Alexander tried to build `bareboxenv` by enabling it
within the barebox.config. He succeeded in doing so.
But the tool did not show up in the final rootfs because
the option "install bareboxenv" from platformconfig was not
enabled.

Yes, the "build bareboxenv" tooltip cleary states that it will
be build. But there's no word about the "install barebox" option
in platformconfig.

At this point we wished for a small hint, pointing us in the right
direction.

I have no idea how to resolve this properly since barebox
(and bareboxenv) can be build without ptxdist and pointing to a
nonexisting (ptxdist-)configuration will get people confused.



regards
Andreas

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-05-27  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  9:50 Alexander Richter
2015-05-27  6:41 ` Sascha Hauer
2015-05-27  8:05   ` Andreas Geisenhainer [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=55657AC3.3040609@atsonline.de \
    --to=andreas.geisenhainer@atsonline.de \
    --cc=barebox@lists.infradead.org \
    /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