From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nfs-utils: fix build error under tests folder
Date: Tue, 18 Dec 2018 10:31:58 +0800 [thread overview]
Message-ID: <5C185C1E.5030009@windriver.com> (raw)
In-Reply-To: <7043db17733d9237d5b3e706dd66471b34e4f54e.camel@linuxfoundation.org>
On 2018年12月18日 01:16, richard.purdie@linuxfoundation.org wrote:
> On Mon, 2018-12-17 at 00:47 -0800, mingli.yu@windriver.com wrote:
>> From: Mingli Yu <Mingli.Yu@windriver.com>
>>
>> * Redefine the reference path of libnfs.a to
>> ../support/nfs/.libs/libnfs.a to fix below
>> error when run "make -C tests statdb_dump".
>> | make: *** No rule to make target '../support/nfs/libnfs.a',
>> needed by 'statdb_dump'. Stop.
>> | make: *** No rule to make target '../../support/nfs/libnfs.a',
>> needed by 'nsm_client'. Stop.
>>
>> * The function generic_make_pathname is introduced in
>> nfs-utils 2.3.1.
>> Add the source file which defines function generic_make_pathname to
>> libnsm_a_SOURCES of libnsm.a to fix the undefined reference
>> when run "make -C tests statdb_dump"
>> | ../support/nsm/libnsm.a(file.o): In function `nsm_make_pathname':
>> | /usr/src/debug/nfs-utils/2.3.1-r0/nfs-utils-
>> 2.3.1/support/nsm/file.c:175: undefined reference to
>> `generic_make_pathname'
>> | /usr/src/debug/nfs-utils/2.3.1-r0/nfs-utils-
>> 2.3.1/support/nsm/file.c:175: undefined reference to
>> `generic_make_pathname'
>> | /usr/src/debug/nfs-utils/2.3.1-r0/nfs-utils-
>> 2.3.1/support/nsm/file.c:175: undefined reference to
>> `generic_make_pathname'
>> | ../support/nsm/libnsm.a(file.o): In function
>> `nsm_setup_pathnames':
>> | /usr/src/debug/nfs-utils/2.3.1-r0/nfs-utils-
>> 2.3.1/support/nsm/file.c:280: undefined reference to
>> `generic_setup_basedir'
>> | collect2: error: ld returned 1 exit status
>>
>> * After the logic of commit[dbb643e Removed missing-prototypes
>> warnings.]
>> introduced, there comes below error when run
>> "make -C tests/nsm_client nsm_client"
>> | nlm_sm_inter_svc.c:20:1: error: no previous prototype for
>> 'nlm_sm_prog_3' [-Werror=missing-prototypes]
>>
>> It is because rpcgen doesn't generate -Wmissing-prototypes
>> free code for nlm_sm_inter_svc.c with below logic
>> in tests/nsm_client/Makefile.am
>> [snip]
>> GENFILES_SVC = nlm_sm_inter_svc.c
>> [snip]
>> $(GENFILES_SVC): %_svc.c: %.x $(RPCGEN)
>> test -f $@ && rm -rf $@ || true
>> $(RPCGEN) -m -o $@ $<
>> So add the patch to not fatalize -Wmissing-prototypes.
>
> Fails on musl:
Will send out V2 to fix it.
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/104
>
> Cheers,
>
> Richard
>
>
next prev parent reply other threads:[~2018-12-18 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 8:47 [PATCH] nfs-utils: fix build error under tests folder mingli.yu
2018-12-17 17:16 ` richard.purdie
2018-12-18 2:31 ` Yu, Mingli [this message]
2018-12-18 5:21 ` [PATCH v2] " mingli.yu
2018-12-27 6:53 ` Yu, Mingli
2019-01-03 2:22 ` Yu, Mingli
2019-01-11 6:51 ` Yu, Mingli
-- strict thread matches above, loose matches on Subject: below --
2018-07-12 8:46 [PATCH] " mingli.yu
2018-07-30 2:15 ` Yu, Mingli
2018-07-30 14:20 ` Burton, Ross
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=5C185C1E.5030009@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@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
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