From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/mplayer
Date: Thu, 26 Jul 2007 09:01:42 +0200 [thread overview]
Message-ID: <1185433302.31437.42.camel@localhost.localdomain> (raw)
In-Reply-To: <37c712e0707230535r4ce29af9t3e39b53037b6fd8d@mail.gmail.com>
On Mon, 2007-07-23 at 08:35 -0400, Allan Clark wrote:
> On 7/23/07, ulf at uclibc.org <ulf@uclibc.org> wrote:
> > Author: ulf
> > Date: 2007-07-23 05:40:43 -0700 (Mon, 23 Jul 2007)
> > New Revision: 19229
> >
> > Log:
> > Cleanup of mplayer package
> >
> > [...]
> >
> > $(MPLAYER_DIR)/$(MPLAYER_BINARY): $(MPLAYER_DIR)/.configured
> > $(MAKE) -C $(MPLAYER_DIR)
> > - @touch -c $@
> > + touch -c $@
> >
> > $(TARGET_DIR)/$(MPLAYER_TARGET_BINARY): $(MPLAYER_DIR)/$(MPLAYER_BINARY)
> > $(INSTALL) -m 0755 -D $(MPLAYER_DIR)/$(MPLAYER_BINARY) $(TARGET_DIR)/$(MPLAYER_TARGET_BINARY)
> > -$(STRIP) --strip-unneeded $(TARGET_DIR)/$(MPLAYER_TARGET_BINARY)
> > - @touch -c $@
> > + touch -c $@
>
> I don't see the logic for these last two touch commands. Sure "-c"
> says "do not create", but they seem unnecessary.
Agree, all the "touch -c <some binary file given by the Makefile rule>"
does not do anything useful. Touch will return 0, and Makefile will
think it was a success.
~ > touch -c doesnotexist
~ > echo $?
0
~ >
--
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: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 12:40 [Buildroot] svn commit: trunk/buildroot/package/mplayer ulf at uclibc.org
2007-07-23 12:35 ` Allan Clark
2007-07-26 7:01 ` Hans-Christian Egtvedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-28 15:43 ulf at uclibc.org
2007-08-29 15:54 jacmet at uclibc.org
2007-08-30 22:40 aldot at uclibc.org
2007-09-20 21:52 ulf at uclibc.org
2007-09-25 11:56 ulf at uclibc.org
2007-09-25 12:01 ulf at uclibc.org
2007-09-25 12:16 ` 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=1185433302.31437.42.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