mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Ian Abbott <abbotti@mev.co.uk>, barebox@lists.infradead.org
Subject: Re: [PATCH v2] scripts: socfpga_import_preloader: Translate DOS line endings
Date: Fri, 16 Jun 2023 13:33:25 +0200	[thread overview]
Message-ID: <20230616113325.GK18491@pengutronix.de> (raw)
In-Reply-To: <20230616113149.GJ18491@pengutronix.de>

On Fri, Jun 16, 2023 at 01:31:49PM +0200, Sascha Hauer wrote:
> On Fri, Jun 16, 2023 at 12:36:11PM +0200, Ahmad Fatoum wrote:
> > Hi,
> > 
> > On 16.06.23 12:30, Sascha Hauer wrote:
> > > On Fri, Jun 16, 2023 at 10:19:38AM +0100, Ian Abbott wrote:
> > >> On 16/06/2023 07:41, Sascha Hauer wrote:
> > >>> Hi Ian,
> > >>>
> > >>> On Thu, Jun 15, 2023 at 04:57:38PM +0100, Ian Abbott wrote:
> > >>>> If the handoff files were generated on a Windows system, they will have
> > >>>> DOS line endings.  The `indent` program (with the options used by the
> > >>>> script) does a lousy job tidying up those files, leaving ASCII CR
> > >>>> characters embedded in the lines.  This is particularly bad for array
> > >>>> initializers that have one value per line, because they all end up on a
> > >>>> single line with embedded ASCII CR characters between each value.
> > >>>>
> > >>>> Add an initial `sed` command to `copy_source()` to match and remove an
> > >>>> ASCII CR character from the end of each input line.
> > >>>>
> > >>>> Also output a message before running `unifdef` and fix the spelling of
> > >>>> "paths" in one of the other messages.
> > >>>>
> > >>>> Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
> > >>>> ---
> > >>>> v2: Corrected tabs in echoed output.
> > >>>> ---
> > >>>>   scripts/socfpga_import_preloader | 6 +++++-
> > >>>>   1 file changed, 5 insertions(+), 1 deletion(-)
> > >>>>
> > >>>> diff --git a/scripts/socfpga_import_preloader b/scripts/socfpga_import_preloader
> > >>>> index bd54e1b913..26a8556b1a 100755
> > >>>> --- a/scripts/socfpga_import_preloader
> > >>>> +++ b/scripts/socfpga_import_preloader
> > >>>> @@ -79,6 +79,10 @@ copy_source() {
> > >>>>   	cp $src $tgt
> > >>>> +	echo "	Translating DOS line endings..."
> > >>>> +	sed -i "s/`echo -e '\r'`$//" $tgt
> > >>>
> > >>> Why `echo -e '\r'` here? A plain \r should work as well.
> > >>
> > >> A plain \r doesn't work, but \\\r works. I prefer '\r'.
> > > 
> > > Strange, would be interesting to know where the difference is.
> > > Here both of these commands have behave the same:
> > > 
> > > echo hallo | unix2dos | sed "s/`echo -e '\r'`$//" | hexdump -C
> > > echo hallo | unix2dos | sed "s/\r$//" | hexdump -C
> > 
> > Speaking of unix2dos, socfpga_get_sequencer and socfpga_xml_to_config.sh
> > already use dos2unix. Why can't we do likewise here and avoid any
> > dash/bash/sed/gsed incompatibilities that might be there?
> 
> We could, but you sent a patch that uses sed instead ;)
> 
> I'm fine with using dos2unix. I thought you were doing so to avoid
> adding another dependency to the barebox build system. In the end
> this script is not even part of the build system, but only a helper
> script which is called manually, so this shouldn't be a problem.
> Also unix2dos/dos2unix is likely found in all Linux distributions. Just
> go for it.

Erm, sorry, I thought I am answering Ian. I didn't realize Ahmad wrote
this mail.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2023-06-16 11:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 13:55 [PATCH] " Ian Abbott
2023-06-15 15:49 ` Ian Abbott
2023-06-15 15:57 ` [PATCH v2] " Ian Abbott
2023-06-16  6:41   ` Sascha Hauer
2023-06-16  9:19     ` Ian Abbott
2023-06-16 10:30       ` Sascha Hauer
2023-06-16 10:36         ` Ahmad Fatoum
2023-06-16 11:31           ` Sascha Hauer
2023-06-16 11:33             ` Sascha Hauer [this message]
2023-06-16 12:02         ` Ian Abbott
2023-06-16 12:31   ` [PATCH v3] " Ian Abbott
2023-06-16 12:35     ` Ahmad Fatoum
2023-06-21  9:34     ` Sascha Hauer

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=20230616113325.GK18491@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=abbotti@mev.co.uk \
    --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