All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Manuel Ebner <manuelebnerli@mailbox.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Linux Next Mailing List  <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [built failure] aicdb.h / __udivdi3
Date: Wed, 23 Sep 2026 17:10:23 +0100	[thread overview]
Message-ID: <20260923171023.5a134671@pumpkin> (raw)
In-Reply-To: <5d00e8d9c5e8118477efcafeb19b1347268bcc38.camel@mailbox.org>

On Wed, 23 Sep 2026 15:41:59 +0200
Manuel Ebner <manuelebnerli@mailbox.org> wrote:

> On Tue, 2026-09-22 at 12:25 -0700, Randy Dunlap wrote:
> > Hi--
> > 
> > On 9/22/26 11:13 AM, Manuel Ebner wrote:  
> > > Hi,
> > > 
> > > I did some built testing with randconf and got some build errors.
> > > 
> > > First error is:
> > >   
> > > > $ make KCFLAGS=-Werror -j8 > make_output.txt
> > > > aicasm_symbol.c:47:10: fatal error: aicdb.h: No such file or directory
> > > >    47 | #include "aicdb.h"
> > > >       |          ^~~~~~~~~  
> > > 
> > > This could be fixed by installing libdb-devel.
> > > But than I got this error with the same configuration:
> > >   
> > > > $ make KCFLAGS=-Werror -j8 > make_output.txt
> > > > date
> > > > drivers/scsi/aic7xxx/aicasm/aicasm: 880 instructions used
> > > > drivers/scsi/aic7xxx/aicasm/aicasm: 25 of 37 register definitions used
> > > > /usr/bin/ld.bfd: fs/exfat/super.o: in function `exfat_set_vol_flags.isra.0':
> > > > super.c:(.text+0x622): undefined reference to `__udivdi3'
> > > > make[2]: *** [scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1
> > > > make[1]: *** [/home/manuel/skripts/next/Makefile:1390: vmlinux] Error 2
> > > > make: *** [Makefile:248: __sub-make] Error 2  
> > > 
> > > What can I do about it?
> > > Is it me/ my system or the kernel?  
> > 
> > For the fs/exfat/ build error:
> > 
> > What is the target (x86_64, i386, arm64, arm, etc.)?  
> 
> My system is x86_64.
> But i guess this means the target is 32 bit:
> > CONFIG_X86_32=y  
> The rest of the .config is below.
> 
> > What is the compiler and its version?  
> 
> gcc (GCC) 16.2.1 20260819 (Red Hat 16.2.1-2)
> 
> > That error usually means that the target is a 32-bit CPU
> > and the code in question is doing an unsupported divide or
> > modulus function.  
> 
> Can the dependencies in the .config be improved to to make this issue impossible?
> 
> > It possibly should be using a kernel macro from <linux/math.h>
> > or other headers.  
> 
> I figured I didn't successfully checkout next but this shouldn't change this error.

I just tried to build the .config from below against a 'quite recent' linux-next.
If fails for a couple of unrelated reasons - I edited the config to fix them.
But there isn't a divide in exfat_set_vol_flags().
I can't see one in the source either.
The usual 'next stage' is to disassemble the .o file and work out which
source line is responsible.

David

  reply	other threads:[~2026-09-23 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 18:13 [built failure] aicdb.h / __udivdi3 Manuel Ebner
2026-09-22 19:25 ` Randy Dunlap
2026-09-23 12:34   ` David Laight
2026-09-23 13:41   ` Manuel Ebner
2026-09-23 16:10     ` David Laight [this message]
2026-09-23 18:01       ` Randy Dunlap

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=20260923171023.5a134671@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=manuelebnerli@mailbox.org \
    --cc=rdunlap@infradead.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 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.