linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	xfs@oss.sgi.com, linux-next <linux-next@vger.kernel.org>,
	Jim Davis <jim.epost@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: randconfig build error with next-20150603, in fs/xfs/xfs_inode.c
Date: Thu, 4 Jun 2015 13:01:03 +1000	[thread overview]
Message-ID: <20150604030103.GJ9143@dastard> (raw)
In-Reply-To: <CAP=VYLppm7teN4LMpOAgXFunmDjnYLFV_mdbZTPaPWMqTwQPtg@mail.gmail.com>

On Wed, Jun 03, 2015 at 10:36:54PM -0400, Paul Gortmaker wrote:
> On Wed, Jun 3, 2015 at 12:31 PM, Jim Davis <jim.epost@gmail.com> wrote:
> > Building with the attached random configuration file,
> >
> > fs/built-in.o: In function `xfs_ifree_cluster':
> > /home/jim/linux/fs/xfs/xfs_inode.c:2268: undefined reference to `__umoddi3'
> 
> I don't think this is specific to a particular randconfig.
> 
> On ARM allmodconfig, I saw:
> 
> ERROR: "__aeabi_uldivmod" [fs/xfs/xfs.ko] undefined!
> 
> On powerpc with an older gcc-4.5 toolchain, I saw:
> 
> /bin/sh: line 1: 23453 Segmentation fault      powerpc-linux-ld -EB -m
> elf64ppc -r -T /home/paul/git/linux-head/scripts/module-common.lds
> arch/powerpc/lib/crtsavres.o --build-id -o fs/xfs/xfs.ko fs/xfs/xfs.o
> fs/xfs/xfs.mod.o
> make[2]: *** [fs/xfs/xfs.ko] Error 139
> 
> I have not investigated further than that.

A fix is already pending. Probably be in tomorrow's linux-next
build.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-06-04  3:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 16:31 randconfig build error with next-20150603, in fs/xfs/xfs_inode.c Jim Davis
2015-06-04  2:36 ` Paul Gortmaker
2015-06-04  3:01   ` Dave Chinner [this message]
2015-06-04  3:15     ` Paul Gortmaker

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=20150604030103.GJ9143@dastard \
    --to=david@fromorbit.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).