From: Jon Ringle <jonringle@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 2/2] host-coreutils: build touch
Date: Tue, 14 Oct 2014 09:17:06 -0400 [thread overview]
Message-ID: <6D91C932-F587-4254-A5A1-B7B1DE68F6CD@gmail.com> (raw)
In-Reply-To: <20141014053223.GA3143@pengutronix.de>
> On Oct 14, 2014, at 1:32 AM, Michael Olbrich <m.olbrich@pengutronix.de> wrote:
>
>> On Tue, Oct 14, 2014 at 01:23:36AM -0400, Jon Ringle wrote:
>> I've found that the below patch isn't good enough. The HOST_COREUTILS
>> only gets installed if systemd is selected. But I need the 'touch'
>> provided by HOST_COREUTILS to get installed before any targetinstall
>> rule gets run. I'm not sure how to make this happen though...
>
> Indeed. '--no-dereference' for touch was introduced in 2009. That's rather
> old. Maybe we should just check and only use it, if it's available. The
> original commit was made to minimize the differences between two builds of
> a BSP. Having a few links with changing timestaps is not too bad. But I
> think we should add 'touch' to coreutils checks in configure.ac.
>
It is in Ubuntu-10.04, which is on our build server. Our IT dept will be upgrading the server in Q1 of 2015 when the LTS support for it runs out. Until then I need to live with needing to build on this build server with the old touch.
Jon
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-10-14 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 2:42 [ptxdist] [PATCH 1/2] systemd: coredumpctl and configuration files jon
2014-10-07 2:42 ` [ptxdist] [PATCH 2/2] host-coreutils: build touch jon
2014-10-14 5:23 ` Jon Ringle
2014-10-14 5:32 ` Michael Olbrich
2014-10-14 13:17 ` Jon Ringle [this message]
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=6D91C932-F587-4254-A5A1-B7B1DE68F6CD@gmail.com \
--to=jonringle@gmail.com \
--cc=ptxdist@pengutronix.de \
/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