From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: alsa-lib
Date: Thu, 26 Jul 2007 09:01:21 +0200 [thread overview]
Message-ID: <1185433281.31437.34.camel@localhost.localdomain> (raw)
In-Reply-To: <20070723133400.GC7902@aon.at>
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.
Pretty funny trying to upgrade libc then; Busybox would truncate the
file to 0 bytes and then try to copy in the new one, never being able to
complete that job because of missing libc.
--
With kind regards,
Hans-Christian Egtvedt, siv.ing. (M.Sc.)
Applications Engineer - AVR32 System Solutions - Atmel Norway
--
Mvh
Hans-Christian Egtvedt
next prev parent reply other threads:[~2007-07-26 7:01 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 [this message]
[not found] ` <1185429498.31437.11.camel@localhost.localdomain>
2007-07-27 15:59 ` Bernhard Fischer
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=1185433281.31437.34.camel@localhost.localdomain \
--to=hcegtvedt@norway.atmel.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