All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] buildtools: fix icc build
Date: Mon, 06 Nov 2017 21:45:18 +0100	[thread overview]
Message-ID: <4092310.7GeyUAk7Gr@xps> (raw)
In-Reply-To: <20171102002510.26917-1-ferruh.yigit@intel.com>

02/11/2017 01:25, Ferruh Yigit:
> There are random build errors in test reports [1]. Build error
> is not directly related to DPDK but observed during DPDK build.
> 
> When I get similar unexpected build errors in my system, found
> out that /dev/null is invalid.
> 
> It seems ICC overwrites the /dev/null with "icc -o /dev/null" instead
> of sending output to /dev/null. This is not always reproducible, so
> hard to say what exactly is triggering the error.
> 
> I suspect test-report build errors can be because of the same reason,
> and it is good to add a protection for this case.
> 
> Instead of sending output to /dev/null save it to the tmp folder and
> remove it back when done.
> 
> [1]
> http://dpdk.org/ml/archives/test-report/2017-November/034053.html
> Failure #3
> 
> /usr/src/linux-headers-4.4.0-97-generic/include/linux/sysfs.h:517:37:
> error: pointer targets in passing argument 2 of ‘kernfs_find_and_get’
> differ in signedness [-Werror=pointer-sign]
>   return kernfs_find_and_get(parent, name);
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied, thanks

Note: this script does not always remove its temporary files.
We need to add a shell trap to catch early exit and do the cleanup.

      reply	other threads:[~2017-11-06 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  0:25 [PATCH] buildtools: fix icc build Ferruh Yigit
2017-11-06 20:45 ` Thomas Monjalon [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=4092310.7GeyUAk7Gr@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /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.