All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Ott <sebott@linux.ibm.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Robert Jarzmik <robert.jarzmik@free.fr>, linux-kernel@vger.kernel.org
Subject: make TAGS broken with commit 99443f811c452c6 ("scripts/tags.sh: change find_other_sources()...")
Date: Thu, 26 Apr 2018 13:25:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1804261311150.1592@schleppi> (raw)

Hi,

on my s390 test system make TAGS is broken since commit 99443f811c452c6
("scripts/tags.sh: change find_other_sources() for include directories")

# make TAGS
  GEN     TAGS
xargs: etags: terminated by signal 11

This is a rather old etags from fedora 24. On x86 using a more recent
etags (fedora 27) make TAGS works as expected. I'll try to update the
test system maybe that'll fix the problem..

Regards,
Sebastian

             reply	other threads:[~2018-04-26 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 11:25 Sebastian Ott [this message]
2018-04-26 12:40 ` make TAGS broken with commit 99443f811c452c6 ("scripts/tags.sh: change find_other_sources()...") Sebastian Ott

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=alpine.LFD.2.21.1804261311150.1592@schleppi \
    --to=sebott@linux.ibm.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.jarzmik@free.fr \
    /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.