From: fixed-term.Oleksij.Rempel <fixed-term.Oleksij.Rempel@de.bosch.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] add initial version of host-openocd package
Date: Thu, 19 Jan 2017 06:10:43 +0100 [thread overview]
Message-ID: <0cdd0c1f-6faa-0204-c4ab-0745457b17e5@de.bosch.com> (raw)
In-Reply-To: <1484773964.15432.35.camel@ws-apr.office.loc>
[-- Attachment #1.1: Type: text/plain, Size: 1696 bytes --]
Hallo Andreas,
On 18.01.2017 22:12, Andreas Pretzsch wrote:
> On Di, 2017-01-17 at 15:56 +0100, Roland Hieber wrote:
>> On 17.01.2017 14:22, fixed-term.Oleksij.Rempel@de.bosch.com wrote:
>>> From: Oleksij Rempel <linux@rempel-privat.de>
>>>
>>> openocd 0.10.0-rc2
>>>
>>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
>>> ---
>>> rules/host-openocd.in | 8 ++++++++
>>> rules/host-openocd.make | 37 +++++++++++++++++++++++++++++++++++++
>>> [...]
>>>
>>
>> Well, that was short and easy :) But I see various enable/disable flags
>> in the configure help that default to "auto" and are not handled here in
>> the Makefile. These flags should be included for the build to be
>> reproducible, or have you checked that they don't depend on the build
>> order of the system? In any case, it is probably a good idea to include
>> any configure options in the menu to let the user choose the feature set
>> (i.e., memory footprint, and additional dependencies, if any).
>
> Back in 2014, I prepared a host package for openocd 0.8.0, which you
> might use as a template. Essentially the same as the target one (which
> got included mainline), just in a host variant. The host package was not
> really needed by anyone (me included), so it did not went in.
>
> You can find the threads on the mailinglist resp. there:
Thank you, i'll take a look on it.
Right now i have some problems to build clean latest PTXdist from git:
./p get host-openocd
mkfifo: cannot create fifo '/tmp/ptxdist.X7jGIC/get-fifo': File exists
ptxdist: error: failed to source lib:
/home/bob/tmp/ptxdist/ptxdist/scripts/lib/ptxd_make_serialize.sh
Any one any idea why?
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-01-19 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 13:22 fixed-term.Oleksij.Rempel
2017-01-17 14:56 ` Roland Hieber
2017-01-18 21:12 ` Andreas Pretzsch
2017-01-19 5:10 ` fixed-term.Oleksij.Rempel [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=0cdd0c1f-6faa-0204-c4ab-0745457b17e5@de.bosch.com \
--to=fixed-term.oleksij.rempel@de.bosch.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