Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Build Dependency Issue in Lustre Mainline Linux
Date: Thu, 5 Nov 2015 22:10:01 +0000	[thread overview]
Message-ID: <D261223F.118B92%andreas.dilger@intel.com> (raw)
In-Reply-To: <563BB5D7.2040506@canonical.com>

On 2015/11/05, 13:02, "lustre-devel on behalf of Chris J Arges"
<lustre-devel-bounces at lists.lustre.org on behalf of
chris.j.arges@canonical.com> wrote:

>Just did a fresh git pull --rebase and tried to do 'make deb-pkg' with
>an Ubuntu config (which enables lustre). I got the following:
>
>depmod: WARNING: found 2 modules in dependency cycles!
>depmod: WARNING:
>/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/driver
>s/staging/lustre/lnet/lnet/lnet.ko
>in dependency cycle!
>depmod: WARNING:
>/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/driver
>s/staging/lustre/lustre/libcfs/libcfs.ko
>in dependency cycle!
>./scripts/depmod.sh: line 57: 16836 Killed                  "$DEPMOD"
>"$@" "$KERNELRELEASE" $SYMBOL_PREFIX
>make[2]: *** [_modinst_post] Error 137
>make[1]: *** [deb-pkg] Error 2
>make: *** [deb-pkg] Error 2
>
>This was building fine in v4.3, so I suspect something after this tag is
>causing issue. (My HEAD is at 8e483ed13).

Could you run git bisect to find the offending patch?  The error messages
don't really give very much to go on.

Cheers, Andreas
-- 
Andreas Dilger

Lustre Software Architect
Intel High Performance Data Division

  reply	other threads:[~2015-11-05 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 20:02 [lustre-devel] Build Dependency Issue in Lustre Mainline Linux Chris J Arges
2015-11-05 22:10 ` Dilger, Andreas [this message]
2015-11-07  0:10 ` Simmons, James A.
2015-11-07  0:38   ` Chris J Arges

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=D261223F.118B92%andreas.dilger@intel.com \
    --to=andreas.dilger@intel.com \
    --cc=lustre-devel@lists.lustre.org \
    /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