From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH 1/3] fix buildroot sed handling on Mac OS X
Date: Fri, 09 Mar 2007 21:28:39 +0200 [thread overview]
Message-ID: <45F1B567.5020902@cs.helsinki.fi> (raw)
In-Reply-To: <20070309083503.GB11011@aon.at>
Bernhard Fischer kirjoitti:
> On Thu, Mar 08, 2007 at 11:36:22PM +0200, Heikki Lindholm wrote:
>
>>Bernhard Fischer kirjoitti:
>>
>>>On Sun, Feb 25, 2007 at 01:22:38PM +0200, Heikki Lindholm wrote:
>>>
>>>
>>>>Improve the checking of sed by adding some common GNU sed installation
>>>>names (gsed/gnused), checking for a basic OS X sed feature in command
>>>>line option handling, checking the actual result of the sed run against
>>>>the expected result, and placing common code for the check under
>>>>toolchain/dependencies/.
>
>
> Applied. Will most likely be moved from diff to cmp since we already use
> cmp (IIRC, didn't look). Care to verify if cmp is already used and if
> so, use cmp instead?
I found no cmp usage in buildroot. How about just using the shell as in
the attached patch?
-- Heikki Lindholm
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot-070309-sed-diff.patch
Url: http://busybox.net/lists/buildroot/attachments/20070309/68d32a7a/attachment.pot
next prev parent reply other threads:[~2007-03-09 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 11:22 [Buildroot] [RFC/PATCH 1/3] fix buildroot sed handling on Mac OS X Heikki Lindholm
2007-03-08 16:35 ` Bernhard Fischer
2007-03-08 21:36 ` Heikki Lindholm
2007-03-09 8:35 ` Bernhard Fischer
2007-03-09 19:28 ` Heikki Lindholm [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 16:10 Heikki Lindholm
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=45F1B567.5020902@cs.helsinki.fi \
--to=holindho@cs.helsinki.fi \
--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