From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] package/exim: remove libnsl linking and fix native tools build
Date: Sat, 19 May 2018 21:01:48 +0200 [thread overview]
Message-ID: <775bdd3d-e233-0347-8a02-d5ee2c08d3ca@gmail.com> (raw)
In-Reply-To: <20180517072627.wkekm5mbofgjo36h@tarshish>
Hi Baruch,
Le 17/05/2018 ? 09:26, Baruch Siach a ?crit?:
> Hi Romain,
>
> On Thu, May 17, 2018 at 09:21:39AM +0200, Romain Naour wrote:
>
> [snip]
>
>> -# only glibc provides libnsl, remove -lnsl for all other toolchains
>> +# Only Exim's nis.so and nisplus.so lookup modules require libnsl,
>> +# but they are not build by default.
>> +# libnsl has been deprecated from Glibc and no other libc provide it.
>> +# There is no libnsl package in Buildroot yet.
>> +# Remove -lnsl for all toolchains.
>> # http://bugs.exim.org/show_bug.cgi?id=1564
>> -ifeq ($(BR2_TOOLCHAIN_USES_GLIBC),)
>> +# This also fixes a host build issue on recent distributions where
>> +# libnsl is not installed by default.
>> define EXIM_REMOVE_LIBNSL_FROM_MAKEFILE
>> $(SED) 's/-lnsl//g' $(@D)/OS/Makefile-Linux
>> endef
>> -endif
>
> It only occurred to me now. Since this is now unconditional we should use a
> regular patch. sed is used here only because the modification used to be
> conditional, and we don't do conditional patching. But this no longer holds.
Ok, It's done in the v4.
Thanks for the review!
Best regards,
Romain
>
>> # musl does not provide struct ip_options nor struct ip_opts (but it is
>> # available with both glibc and uClibc)
>
> baruch
>
next prev parent reply other threads:[~2018-05-19 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 7:21 [Buildroot] [PATCH v3 1/2] package/exim: remove libnsl linking and fix native tools build Romain Naour
2018-05-17 7:21 ` [Buildroot] [PATCH v3 2/2] Revert "glibc: install the obsolete libnsl" Romain Naour
2018-05-17 7:26 ` [Buildroot] [PATCH v3 1/2] package/exim: remove libnsl linking and fix native tools build Baruch Siach
2018-05-19 19:01 ` Romain Naour [this message]
2018-05-17 20:19 ` Thomas Petazzoni
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=775bdd3d-e233-0347-8a02-d5ee2c08d3ca@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@busybox.net \
/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