Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1387558
| From | Jens Axboe <axboe@kernel.dk> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build failure after merge of the block tree |
| Date | 2016-04-26 16:50 +0200 |
| Message-ID | <rsctk-Xx-23@gated-at.bofh.it> (permalink) |
| References | <rs20W-By-23@gated-at.bofh.it> <rsbnA-9L-9@gated-at.bofh.it> <rsctk-Xx-25@gated-at.bofh.it> <rsctk-Xx-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 04/26/2016 08:40 AM, Nicolas Pitre wrote:
> On Tue, 26 Apr 2016, Stephen Rothwell wrote:
>
>> Hi Michal,
>>
>> On Tue, 26 Apr 2016 15:30:01 +0200 Michal Marek <mmarek@suse.cz> wrote:
>>>
>>> On 2016-04-26 05:38, Stephen Rothwell wrote:
>>>> Hi Nicolas,
>>>>
>>>> After merging the block tree, today's linux-next build (powerpc
>>>> ppc64_defconfig) failed like this:
>>>>
>>>> ERROR: ".blk_queue_write_cache" [drivers/block/virtio_blk.ko] undefined!
>>>> ERROR: ".blk_queue_write_cache" [drivers/block/ps3disk.ko] undefined!
>>>> ERROR: ".blk_queue_write_cache" [drivers/block/nbd.ko] undefined!
>>>>
>>>> Caused by commit
>>>>
>>>> 089095b8eef9 ("kbuild: better abstract vmlinux sequential prerequisites")
>>>>
>>>> from the kbuild-pite tree.
>>>>
>>>> I have reverted that commit for today.
>>>
>>> I can't reproduce this with today's linux-next and the revert reverted.
>>> Also, CONFIG_TRIM_UNUSED_KSYMS is disabled in the defconfig as expected,
>>> so I have no idea what went wrong.
>>
>> Yeah, I couldn't figure it out either, but the revert made it work for
>> me. Could it be that I do incremental builds - so today, I would have
>> built commit b087ce990625 ("Merge remote-tracking branch 'input/next'")
>> which worked, then commit 9d67df654092 ("Merge remote-tracking branch
>> 'block/for-next'") which failed.
>>
>> The only suspect code in the block tree has been there since April 13
>> with no build failures.
>>
>> Anyway, I can see how things go tomorrow, but I hate it when things
>> seem fragile like this.
>
> If you can reproduce this build failure, could you try a make mrproper
> and attempt it again? I, too, would like to find an explanation and a
> way to reproduce.
I just took a look at it, and it doesn't make any sense to me...
--
Jens Axboe
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: build failure after merge of the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-26 05:40 +0200
Re: linux-next: build failure after merge of the block tree Michal Marek <mmarek@suse.cz> - 2016-04-26 15:40 +0200
Re: linux-next: build failure after merge of the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-26 16:00 +0200
Re: linux-next: build failure after merge of the block tree Jens Axboe <axboe@kernel.dk> - 2016-04-26 16:50 +0200
Re: linux-next: build failure after merge of the block tree Nicolas Pitre <nicolas.pitre@linaro.org> - 2016-04-26 16:50 +0200
Re: linux-next: build failure after merge of the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-26 17:20 +0200
Re: linux-next: build failure after merge of the block tree Nicolas Pitre <nicolas.pitre@linaro.org> - 2016-04-26 22:50 +0200
Re: linux-next: build failure after merge of the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-26 23:40 +0200
Re: linux-next: build failure after merge of the block tree Michal Marek <mmarek@suse.cz> - 2016-04-27 11:10 +0200
Re: linux-next: build failure after merge of the block tree Nicolas Pitre <nicolas.pitre@linaro.org> - 2016-04-27 15:50 +0200
csiph-web