From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xenproject.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Linux 5.11-rc6 compile error
Date: Wed, 3 Feb 2021 15:04:15 -0700 [thread overview]
Message-ID: <7e05fe6d-9bf3-7d8d-5cda-8f4745bb144d@linuxfoundation.org> (raw)
In-Reply-To: <CAHk-=wg983RfAiSSo4zLMADEfzLEuoBi+rye30Zrq7Bor8zg_Q@mail.gmail.com>
On 2/3/21 1:06 PM, Linus Torvalds wrote:
> On Wed, Feb 3, 2021 at 11:58 AM Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive
>> is not an object
>> make: *** [Makefile:1170: vmlinux] Error 1
>
> That honestly sounds like something went wrong earlier - things like
> doing a system upgrade in the middle of the build, or perhaps running
> out of disk space or similar.
>
> I've not seen any other reports of the same, and google doesn't find
> anything like that either.
>
> Does it keep happening if you do a "git clean -dqfx" to make sure you
> have no old corrupt object files sound and re-do the whole build?
>
> Linus
>
My bad. I was playing with two test systems this morning and totally
lost track. All is well after a "make clean" and make.
Sorry for the noise.
thanks,
-- Shuah
next prev parent reply other threads:[~2021-02-03 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 19:58 Linux 5.11-rc6 compile error Shuah Khan
2021-02-03 20:06 ` Linus Torvalds
2021-02-03 22:04 ` Shuah Khan [this message]
2021-02-03 21:05 ` 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=7e05fe6d-9bf3-7d8d-5cda-8f4745bb144d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xenproject.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