Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris J Arges <chris.j.arges@canonical.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Build Dependency Issue in Lustre Mainline Linux
Date: Fri, 6 Nov 2015 18:38:04 -0600	[thread overview]
Message-ID: <563D47EC.6080909@canonical.com> (raw)
In-Reply-To: <9c0ab2c280eb401f88d0ffd57ec3987b@EXCHCS32.ornl.gov>

On 11/06/2015 06:10 PM, Simmons, James A. 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/drivers/staging/lustre/lnet/lnet/lnet.ko
>> in dependency cycle!
>> depmod: WARNING:
>> /home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lustre/libcfs/libcfs.ko
>> in dependency cycle!
>> ./scripts/depmod.sh: line 57: 16836 Killed                  "$DEPMOD"
> 
> I solved your problem. If you delete IOC_LIBCFS_PING_TEST ioctl case  from libcfs/libcfs/module.c it work again. 
> That ioctl has not been is use for some time and it can be removed. What is happening is libcfs_nid2str is being
> called which requires lnet.ko now. This is a layer violation. I will be sending a patch very shortly.
> 

Thanks, good to hear.
--chris

      reply	other threads:[~2015-11-07  0:38 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
2015-11-07  0:10 ` Simmons, James A.
2015-11-07  0:38   ` Chris J Arges [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=563D47EC.6080909@canonical.com \
    --to=chris.j.arges@canonical.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