From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] coreutils: get the uptime program to work
Date: Thu, 11 Sep 2014 10:12:21 +0100 [thread overview]
Message-ID: <54116775.1080204@imgtec.com> (raw)
In-Reply-To: <1410381844-14466-1-git-send-email-thomas.petazzoni@free-electrons.com>
Dear ThomasP,
On 09/10/2014 09:44 PM, Thomas Petazzoni wrote:
> coreutils configure script needs to know whether /proc/uptime is
> available, but this is not possible in a cross-compilation
> context. This leads to an uptime program that fails to work on the
> target, as it has been compiled without /proc/uptime reading support.
>
> This commit fixes that by telling coreutils at configure time that
> /proc/uptime will be available on the target (which seems to be a
> reasonable assumption on Linux systems).
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> package/coreutils/coreutils.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/coreutils/coreutils.mk b/package/coreutils/coreutils.mk
> index 07a1347..e6af7e2 100644
> --- a/package/coreutils/coreutils.mk
> +++ b/package/coreutils/coreutils.mk
> @@ -57,6 +57,7 @@ COREUTILS_CONF_ENV = ac_cv_c_restrict=no \
> gl_cv_func_working_mkstemp=yes \
> gl_cv_func_working_utimes=yes \
> gl_getline_needs_run_time_check=no \
> + gl_cv_have_proc_uptime=yes \
> utils_cv_localtime_cache=no \
> PERL=missing
>
>
Welcome to Buildroot
(none) login: root
# uptime
00:00am up 0:00, 1 user, load average: 0.46, 0.00, 0.10
It works :)
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
--
Vincent
next prev parent reply other threads:[~2014-09-11 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 20:44 [Buildroot] [PATCH] coreutils: get the uptime program to work Thomas Petazzoni
2014-09-11 9:12 ` Vicente Olivert Riera [this message]
2014-09-13 21:54 ` Peter Korsgaard
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=54116775.1080204@imgtec.com \
--to=vincent.riera@imgtec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.