From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Martin Bonner <martingreybeard@gmail.com>
Cc: Bin Meng <bmeng.cn@gmail.com>, u-boot@lists.denx.de
Subject: Re: [PATCH v4] Improve Windows build documentation
Date: Wed, 27 Jul 2022 15:56:07 +0200 [thread overview]
Message-ID: <809d36a7-12a8-669b-e9e5-07a398e0f746@gmx.de> (raw)
In-Reply-To: <d61edd94-045c-e223-1c8b-1f02e5aef366@gmx.de>
On 7/27/22 15:51, Heinrich Schuchardt wrote:
> On 7/27/22 15:29, Heinrich Schuchardt wrote:
>> On 7/25/22 09:42, Martin Bonner wrote:
>>> * Add three more modules that are required.
>>> * Remove the version numbers (because they are hard to keep in sync
>>> with the latest MSYS2 versions)
>>> * Add a pacman command line to install everything.
>>>
>>> Signed-off-by: Martin Bonner <martingreybeard@gmail.com>
>>
>> Your mail is not a valid patch:
>>
>> $ git am /tmp/0.patch
>> Applying: Improve Windows build documentation
>> error: corrupt patch at line 10
>> Patch failed at 0001 Improve Windows build documentation
>>
>> Please, use 'git send-email' for sending patches.
>>
>> Best regards
>>
>> Heinrich
>>
>>> ---
>>> doc/build/tools.rst | 22 ++++++++++++++--------
>>> 1 file changed, 14 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/doc/build/tools.rst b/doc/build/tools.rst
>>> index c06f915274..5f8a04a31b 100644
>>> --- a/doc/build/tools.rst
>>> +++ b/doc/build/tools.rst
>>> @@ -24,14 +24,20 @@ you can use MSYS2, a software distro and building
>>> platform for Windows.
>>> Download the MSYS2 installer from https://www.msys2.org. Make sure
>>> you have
>>> installed all required packages below in order to build these host
>>> tools::
>>>
>>> - * gcc (9.1.0)
>>> - * make (4.2.1)
>>> - * bison (3.4.2)
>>> - * diffutils (3.7)
>>> - * openssl-devel (1.1.1.d)
>>> -
>>> -Note the version numbers in these parentheses above are the package
>>> versions
>>> -at the time being when writing this document. The MSYS2 installer
>>> tested is
>>> + * gcc
>>> + * make
>>> + * bison
>>> + * diffutils
>>> + * openssl-devel
>>> + * flex
>>> + * libgnutls-devel
>>> + * libuuid-devel
>
> This should not be pre-formatted text but simply a list.
>
>>> +
>>> +You probably want ``git`` as well. You can install all these with::
>
> Allow for syntax highlighting:
>
> .. code-block:: bash
>
>>> +
>>> + $ pacman -S gcc make bison diffutils openssl-devel flex
>>> libgnutls-devel libuuid-devel git
>
> The line should be limited to 80 characters. Use \.
> Please, remove the leading $.
>
> Best regards
>
> Heinrich
>
>>> +
>>> +The MSYS2 installer tested is
>>> http://repo.msys2.org/distrib/x86_64/msys2-x86_64-20190524.exe.
Do you really suggest to download a 3 year old version?
Shouldn't we simply remove this sentence?
Best regards
Heinrich
>>>
>>> There are 3 MSYS subsystems installed: MSYS2, MinGW32 and MinGW64.
>>> Each
>>> --
>>> Martin Bonner
>
next prev parent reply other threads:[~2022-07-27 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 7:42 [PATCH v4] Improve Windows build documentation Martin Bonner
2022-07-25 7:46 ` Bin Meng
2022-07-27 13:29 ` Heinrich Schuchardt
2022-07-27 13:51 ` Heinrich Schuchardt
2022-07-27 13:56 ` Heinrich Schuchardt [this message]
2022-07-27 14:15 ` Tom Rini
2022-07-27 15:15 ` Martin Bonner
2022-07-27 15:24 ` Tom Rini
2022-07-27 15:07 ` Martin Bonner
2022-07-27 16:21 ` Heinrich Schuchardt
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=809d36a7-12a8-669b-e9e5-07a398e0f746@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=bmeng.cn@gmail.com \
--cc=martingreybeard@gmail.com \
--cc=u-boot@lists.denx.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