From: Bastian Stender <bst@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] avahi: set FILE_OFFSET_BITS to work with 64 bit inodes
Date: Mon, 24 Jul 2017 14:16:24 +0200 [thread overview]
Message-ID: <a3b803d5-e0c6-8a57-49e9-8a1360ac2926@pengutronix.de> (raw)
In-Reply-To: <20170719101940.yrhp7tobhlxsl242@pengutronix.de>
On 07/19/2017 12:19 PM, Uwe Kleine-König wrote:
> On Wed, Jul 19, 2017 at 11:59:19AM +0200, Bastian Stender wrote:
>> In case of 64 bit inodes calls to 32 bit variants of stat() will cause
>> EOVERFLOW and avahi will terminate with
>>
>> Value too large for defined data type
>>
>> FILE_OFFSET_BITS=64 makes the code receive 64 bit values.
>>
>> Signed-off-by: Bastian Stender <bst@pengutronix.de>
>> ---
>> rules/avahi.make | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/rules/avahi.make b/rules/avahi.make
>> index 8a10d15ea..2e796bce4 100644
>> --- a/rules/avahi.make
>> +++ b/rules/avahi.make
>> @@ -83,6 +83,8 @@ AVAHI_CONF_OPT := \
>> --with-autoipd-group=$(PTXCONF_AVAHI_AUTOIP_GROUP) \
>> --with-systemdsystemunitdir=/usr/lib/systemd/system
>>
>> +AVAHI_CFLAGS:= -D_FILE_OFFSET_BITS=64
>> +
>
> I say this should better be done in the configure script of avahi. You
> want to add the macro AC_SYS_LARGEFILE there.
Yes, it would be best to fix this upstream. Simply adding the macro does
not work with avahi 0.7. I'd say we use this patch for now until someone
finds time to fix this upsteam.
Bastian
--
Pengutronix e.K.
Industrial Linux Solutions
http://www.pengutronix.de/
Peiner Str. 6-8, 31137 Hildesheim, Germany
Amtsgericht Hildesheim, HRA 2686
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-07-24 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 9:59 Bastian Stender
2017-07-19 9:59 ` [ptxdist] [PATCH 2/2] iptables: " Bastian Stender
2017-07-19 10:19 ` [ptxdist] [PATCH 1/2] avahi: " Uwe Kleine-König
2017-07-24 12:16 ` Bastian Stender [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=a3b803d5-e0c6-8a57-49e9-8a1360ac2926@pengutronix.de \
--to=bst@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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