From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] use a more portable syntax for mktemp. fixes build problem under MacOS X
Date: Wed, 19 Sep 2012 22:30:28 +0200 [thread overview]
Message-ID: <20120919223028.168abba2@skate> (raw)
In-Reply-To: <20120919164317.GA20160@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Wed, 19 Sep 2012 18:43:17 +0200, Waldemar Brodkorb wrote:
> diff --git a/support/kconfig/lxdialog/check-lxdialog.sh b/support/kconfig/lxdialog/check-lxdialog.sh
> index 969cd4c..fb4d90b 100644
> --- a/support/kconfig/lxdialog/check-lxdialog.sh
> +++ b/support/kconfig/lxdialog/check-lxdialog.sh
> @@ -33,7 +33,7 @@ ccflags()
> }
>
> # Temp file, try to clean up after us
> -tmp=$(mktemp)
> +tmp=$(mktemp -t yyy)
> trap "rm -f $tmp" 0 1 2 3 15
>
> # Check if we can link to ncurses
If you make any changes to support/kconfig/, then those changes should
also be done in the patches in support/kconfig/patches/ that help us
port our changes to later versions of kconfig when we sync kconfig with
the latest kernel version.
In your case, changing patch 11 sounds like a good plan. However, does
Buildroot really works on Mac OS X? I don't think anybody uses
Buildroot on Mac OS X, and I suspect that a lot of things might be
broken besides just kconfig, no?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-19 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 16:43 [Buildroot] [PATCH] use a more portable syntax for mktemp. fixes build problem under MacOS X Waldemar Brodkorb
2012-09-19 20:30 ` Thomas Petazzoni [this message]
2012-09-20 7:49 ` Waldemar Brodkorb
2012-09-20 12:13 ` 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=20120919223028.168abba2@skate \
--to=thomas.petazzoni@free-electrons.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