From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libtahu: Change CFLAGS to use 64-bit system time
Date: Fri, 24 Feb 2023 09:55:12 +0000 [thread overview]
Message-ID: <3cbe455b-9922-87bc-aa8e-60588d3b8e3e@mev.co.uk> (raw)
In-Reply-To: <Y/eJfXcDv0Q4W+0n@pengutronix.de>
On 23/02/2023 15:42, Michael Olbrich wrote:
> On Mon, Feb 20, 2023 at 01:41:05PM +0000, Ian Abbott wrote:
>> diff --git a/rules/libtahu.make b/rules/libtahu.make
>> index 26c064c6d..3e392216d 100644
>> --- a/rules/libtahu.make
>> +++ b/rules/libtahu.make
>> @@ -37,11 +37,12 @@ LIBTAHU_CONF_TOOL := NO
>> # Compile
>> # ----------------------------------------------------------------------------
>>
>> -#LIBTAHU_MAKE_ENV := $(CROSS_ENV)
>> -
>> +LIBTAHU_CPPFLAGS := -Iinclude -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
>> +LIBTAHU_CFLAGS := -O2 -g -g3 -fPIC
>
> No need to mess with the existing CFLAGS. You can inject extra CFLAGS
> though the toolchain wrappers. And for correctness, make it conditional:
>
> ifdef PTXCONF_GLOBAL_LARGE_FILE
> LIBTAHU_CFLAGS := -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
> endif
>
> nothing else is needed.
libtahu does not actually use files, large or otherwise. It's the
64-bit time support that I want, not the large file support. However
glibc does not support _TIME_BITS=64 unless _FILE_OFFSET_BITS=64, so
that needs to come along for the ride.
--
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company )=-
-=( registered in England & Wales. Regd. number: 02862268. )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-
next prev parent reply other threads:[~2023-02-24 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 13:41 Ian Abbott
2023-02-23 15:42 ` Michael Olbrich
2023-02-24 9:55 ` Ian Abbott [this message]
2023-02-24 14:43 ` Michael Olbrich
2023-02-24 12:03 ` Ian Abbott
2023-02-24 14:45 ` Michael Olbrich
2023-02-24 16:10 ` Ian Abbott
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=3cbe455b-9922-87bc-aa8e-60588d3b8e3e@mev.co.uk \
--to=abbotti@mev.co.uk \
--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