Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Alan Maguire <alan.maguire@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alan Maguire <alan.maguire@oracle.com>
Subject: Re: linux-next: build failure after merge of the kunit-next tree
Date: Thu, 16 Jan 2020 11:23:09 +0000 (GMT)
Message-ID: <alpine.LRH.2.20.2001161120230.2505@dhcp-10-175-200-122.vpn.oracle.com> (raw)
In-Reply-To: <20200116165703.4e04be51@canb.auug.org.au>

On Thu, 16 Jan 2020, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the kunit-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> x86_64-linux-gnu-ld: drivers/base/test/property-entry-test.o: in function `kunit_test_suites_init':
> property-entry-test.c:(.text+0x26): undefined reference to `kunit_run_tests'
> x86_64-linux-gnu-ld: drivers/base/test/property-entry-test.o: in function `pe_test_reference':
> property-entry-test.c:(.text+0x275): undefined reference to `kunit_binary_assert_format'
> x86_64-linux-gnu-ld: property-entry-test.c:(.text+0x2c4): undefined reference to `kunit_do_assertion'
> 
> and lots more ...
> 
> Caused by commit
> 
>   27f9d7e984d9 ("software node: introduce CONFIG_KUNIT_DRIVER_PE_TEST")
> 
> from the pm tree interacting with commit
> 
>   35c57fc3f8ea ("kunit: building kunit as a module breaks allmodconfig")
> 
> I have disabled CONFIG_KUNIT_DRIVER_PE_TEST for today.
>

Apologies again, I should have explicitly specified that
CONFIG_KUNIT_DRIVER_PE_TEST depends on KUNIT=y; I've
sent a patch to fix this:

https://lore.kernel.org/lkml/1579173451-2439-1-git-send-email-alan.maguire@oracle.com/T/#u

Thank you!

Alan
 
> -- 
> Cheers,
> Stephen Rothwell
> 

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  5:57 Stephen Rothwell
2020-01-16 11:23 ` Alan Maguire [this message]
2020-01-16 23:27   ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2020-01-10  6:43 Stephen Rothwell
2020-01-10 11:56 ` Alan Maguire
2020-01-13 21:11   ` Brendan Higgins

Reply instructions:

You may reply publically 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=alpine.LRH.2.20.2001161120230.2505@dhcp-10-175-200-122.vpn.oracle.com \
    --to=alan.maguire@oracle.com \
    --cc=brendanhiggins@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    --cc=skhan@linuxfoundation.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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git