From: "Peter Nørlund" <pch@ordbogen.com>
To: David Miller <davem@davemloft.net>
Cc: fengguang.wu@intel.com, kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [net-next:master 647/682] fib_semantics.c:undefined reference to `__divdi3'
Date: Mon, 5 Oct 2015 23:31:58 +0200 [thread overview]
Message-ID: <20151005233158.2c09adce@tyr> (raw)
In-Reply-To: <20151005.042638.1280563834697071426.davem@davemloft.net>
On Mon, 05 Oct 2015 04:26:38 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: kbuild test robot <fengguang.wu@intel.com>
> Date: Mon, 5 Oct 2015 18:54:18 +0800
>
> > tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> > master head: 937317c7c1097aa878a5000e3aab616eb5c590c0 commit:
> > 0e884c78ee19e902f300ed147083c28a0c6302f0 [647/682] ipv4: L3
> > hash-based multipath config: i386-defconfig (attached as .config)
> > reproduce: git checkout 0e884c78ee19e902f300ed147083c28a0c6302f0
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > All errors (new ones prefixed by >>):
> >
> > net/built-in.o: In function `fib_rebalance':
> >>> fib_semantics.c:(.text+0x9df14): undefined reference to `__divdi3'
>
> Peter please fix this.
Darn! Didn't consider that 32-bit architectures would behave
differently. I'll remember to at also test on i386 and ARM in the
future.
What is the proper way to supply fixes for this kind of errors? Should
I submit the original patches again with the bug fixed, or should I
submit a patch fixing this particular problem? I imagine bisecting
becomes annoying when a particular commit doesn't compile.
The ARM compilation errors is apparently solved by the same fix.
Best Regards
Peter Nørlund
next prev parent reply other threads:[~2015-10-05 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 10:54 [net-next:master 647/682] fib_semantics.c:undefined reference to `__divdi3' kbuild test robot
2015-10-05 11:26 ` David Miller
2015-10-05 21:31 ` Peter Nørlund [this message]
2015-10-05 21:35 ` Florian Westphal
2015-10-06 6:42 ` David Miller
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=20151005233158.2c09adce@tyr \
--to=pch@ordbogen.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).