From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: alsa-lib
Date: Fri, 27 Jul 2007 17:59:15 +0200 [thread overview]
Message-ID: <20070727155915.GB25147@aon.at> (raw)
In-Reply-To: <1185429498.31437.11.camel@localhost.localdomain>
On Thu, Jul 26, 2007 at 07:58:18AM +0200, Hans-Christian Egtvedt wrote:
>
>On Mon, 2007-07-23 at 15:34 +0200, Bernhard Fischer wrote:
>> On Mon, Jul 23, 2007 at 03:18:05PM +0200, Ulf Samuelsson wrote:
>
><cut alsa-lib patch and use of install instead of cp>
>
>> Just using install(1) for new packages -- and eventually gradually
>> fixing old ones -- is sufficient. We can easily either use busybox's
>> install or have our own in buildroot to circumvent eventual buggy
>> incarnations on the host. This would also help the MacOS10 folks, i'd
>> say.
>
>FYI
>
>IIRC the install shipped with buildroot is buggy (they might have fixed
>it). It had a bug when it would not unlink the old file before writing
>the new.
$ echo BAR > foo
$ echo FOO > new
$ ./busybox install new foo
[]
open("new", O_RDONLY) = 3
open("foo", O_WRONLY|O_CREAT|O_EXCL, 0100644) = -1 EEXIST (File exists)
unlink("foo") = 0
open("foo", O_WRONLY|O_CREAT|O_EXCL, 0100644) = 4
read(3, "FOO\n", 8192) = 4
write(4, "FOO\n", 4) = 4
read(3, "", 8192) = 0
close(4) = 0
close(3) = 0
So it looks like "they" fixed it.
next prev parent reply other threads:[~2007-07-27 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 7:54 [Buildroot] svn commit: trunk/buildroot/package: alsa-lib ulf at uclibc.org
2007-07-23 10:33 ` Bernhard Fischer
2007-07-23 13:18 ` Ulf Samuelsson
2007-07-23 13:34 ` Bernhard Fischer
2007-07-23 14:42 ` Ulf Samuelsson
2007-07-26 7:01 ` Hans-Christian Egtvedt
[not found] ` <1185429498.31437.11.camel@localhost.localdomain>
2007-07-27 15:59 ` Bernhard Fischer [this message]
2007-08-20 8:34 ` [Buildroot] [RFC] Building linux kernel in $(PROJECT_BUILD_DIR) Ulf Samuelsson
2007-08-20 15:56 ` Bernhard Fischer
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=20070727155915.GB25147@aon.at \
--to=rep.dot.nop@gmail.com \
--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