From: Alexander Dahl <post@lespocky.de>
To: buildroot@busybox.net
Subject: [Buildroot] changing sources before patching
Date: Sun, 13 Mar 2016 20:28:03 +0100 [thread overview]
Message-ID: <56E5BF43.90507@lespocky.de> (raw)
Hei hei,
in the fli4l [1] project, we use buildroot as build system, a little
custom stuff on top, but basically it's buildroot. Now Carsten wanted to
make a package for sfftools [2], especially sfftobmp3. The source is
only available from subversion and we need to patch it. The problem we
face is: some files we need to patch (e.g. configure.ac) have CRLF aka
DOS line endings and patch fails then. So we want to convert the line
endings to LF aka unix before patching. Is this possible with buildroot
and how? Or does anyone else has a good idea for an elegant solution to
this problem?
(please keep Carsten and Christoph in Cc)
Greets
Alex
[1] http://www.fli4l.de/
[2] https://sourceforge.net/projects/sfftools/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160313/8a531e54/attachment.asc>
next reply other threads:[~2016-03-13 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 19:28 Alexander Dahl [this message]
2016-03-13 19:45 ` [Buildroot] changing sources before patching Bernd Kuhls
2016-03-13 21:53 ` Arnout Vandecappelle
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=56E5BF43.90507@lespocky.de \
--to=post@lespocky.de \
--cc=buildroot@busybox.net \
/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