From: Ian Kent <raven@themaw.net>
To: Waldemar Brodkorb <wbx@openadk.org>, autofs@vger.kernel.org
Subject: Re: [PATCH v3] use pkg-config to search for libtirpc to fix cross-compilation
Date: Fri, 7 Jul 2017 08:56:21 +0800 [thread overview]
Message-ID: <cc2a1c58-56d4-a3f3-2e8b-09d357ae9a92@themaw.net> (raw)
In-Reply-To: <20170706210947.GG2081@waldemar-brodkorb.de>
On 07/07/17 05:09, Waldemar Brodkorb wrote:
> Hi,
>
> friendly ping?
Oh right, I didn't say what's happening.
The patch is in my patch queue.
I'll get to committing what I have in the queue fairly soon.
There were a couple of bugs in the 5.1.3 release that need to be fixed.
So another release will be done sooner rather than later as well, can't
say exactly when but I'd like to do it fairly soon.
>
>> When trying to cross-compile autofs for example with a buildsystem
>> like buildroot, the compilation fails in case the user wants to use
>> libtirpc library as RPC implementation. A hard coded include path
>> in aclocal.m4 is used. Other opensource software like rpcbind or
>> nfs-utils are suing autotools pkgconfig infrastructure to find
>> the libtirpc headers and to pass the correct linker flags.
>>
>> Convert configure.in to use PKG_CHECK_MODULES and remove the
>> hand written autoconf macros from aclocal.m4. Move aclocal.m4
>> to m4 directory, so that autoconf does not skip global
>> directories, otherwise pkg.m4 (pkg-config macros) are not found.
>>
>> This fixes cross-compilation of autofs and allows to use
>> alternative C libraries as uClibc-ng without internal RPC
>> support to be used in cross-compiling environments.
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
prev parent reply other threads:[~2017-07-07 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 8:54 [PATCH v3] use pkg-config to search for libtirpc to fix cross-compilation Waldemar Brodkorb
2017-07-06 21:09 ` Waldemar Brodkorb
2017-07-07 0:56 ` Ian Kent [this message]
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=cc2a1c58-56d4-a3f3-2e8b-09d357ae9a92@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=wbx@openadk.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 read-only IMAP folder(s) and NNTP newsgroup(s).