All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] sysvinit-2.88 build is failing for ARM64
Date: Sat, 19 Sep 2015 22:34:45 +0300	[thread overview]
Message-ID: <20150919193445.GC2782@tarshish> (raw)
In-Reply-To: <20150918092604.6029c0a6@free-electrons.com>

Hi Thomas,

On Fri, Sep 18, 2015 at 09:26:04AM +0200, Thomas Petazzoni wrote:
> On Fri, 18 Sep 2015 00:39:16 +0300, Baruch Siach wrote:
> > Why not use /dev/null for gcc output instead of a temporary file? 
> > Something like:
> > 
> > HAS_LIBCRYPT=$(shell echo 'int main(void) {}' | $(CC) -o /dev/null -xc - -lcrypt >/dev/null 2>&1 && echo y)
> 
> Because it is known to not work with all toolchains:
> 
>    http://git.buildroot.net/buildroot/commit/toolchain/helpers.mk?id=375bc18850f0f8fec90e1e478c0e9d2159377a64

Good to know, thanks. Maybe it's time for /dev/null.d/.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-09-19 19:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  9:40 [Buildroot] [PATCH v2] mplayer: enable building on ARM64 jpinto
2015-09-17 10:28 ` [Buildroot] sysvinit-2.88 build is failing for ARM64 Joao Pinto
2015-09-17 10:35   ` Baruch Siach
2015-09-17 10:39     ` Joao Pinto
2015-09-17 10:55       ` Joao Pinto
2015-09-17 11:12         ` Baruch Siach
2015-09-17 11:13           ` Joao Pinto
2015-09-17 21:07           ` Thomas Petazzoni
2015-09-17 21:39             ` Baruch Siach
2015-09-18  7:26               ` Thomas Petazzoni
2015-09-19 19:34                 ` Baruch Siach [this message]
2015-09-17 21:31 ` [Buildroot] [PATCH v2] mplayer: enable building on ARM64 Thomas Petazzoni

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=20150919193445.GC2782@tarshish \
    --to=baruch@tkos.co.il \
    --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.