All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Manuel Ebner <manuelebnerli@mailbox.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 13:34:07 +0100	[thread overview]
Message-ID: <20260923133407.7411334a@pumpkin> (raw)
In-Reply-To: <0aa303bc-d3e9-4670-91e5-8299ddfcb6db@infradead.org>

On Tue, 22 Sep 2026 12:25:09 -0700
Randy Dunlap <rdunlap@infradead.org> 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.)?
> What is the compiler and its version?

What strange set of build options are being used?

> 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.
> 
> It possibly should be using a kernel macro from <linux/math.h>
> or other headers.
> 


  reply	other threads:[~2026-09-23 12:34 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 [this message]
2026-09-23 13:41   ` Manuel Ebner
2026-09-23 16:10     ` David Laight
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=20260923133407.7411334a@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.