From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with building sudo
Date: Fri, 15 Dec 2006 16:10:39 +0100 [thread overview]
Message-ID: <20061215151039.GA14633@aon.at> (raw)
In-Reply-To: <4579D9F3.1070400@fortunet.com>
On Fri, Dec 08, 2006 at 01:32:35PM -0800, Boris Itkis (Linux) wrote:
>sudu.mk has a problem for building:
>
>$(TARGET_DIR)/usr/bin/sudo
>
>it echo's the command to install sudu instead of running it.
I'll look into this.
>
>It generally does not stop compile because on distributions like fedora
>because "touch -c" has a exit code of 0 even if the file does no exist.
That's a bug.
Point them to
http://www.opengroup.org/onlinepubs/009695399/utilities/touch.html#tag_04_143_18
which reads
"
At least one historical implementation of touch incremented the exit
code if -c was specified and the file did not exist. This volume of IEEE
Std 1003.1-2001 requires exit status zero if no errors occur.
"
next prev parent reply other threads:[~2006-12-15 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 21:32 [Buildroot] Problem with building sudo Boris Itkis
2006-12-15 15:10 ` Bernhard Fischer [this message]
2006-12-15 15:29 ` Bernhard Fischer
2006-12-15 18:14 ` Boris Itkis
2006-12-20 18:28 ` Bernhard Fischer
2006-12-20 22:04 ` Boris Itkis
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=20061215151039.GA14633@aon.at \
--to=rep.nop@aon.at \
--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