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 16:10:22 +0000 [thread overview]
Message-ID: <b40008a9-3146-e22b-cc32-3c3ea473a1fd@mev.co.uk> (raw)
In-Reply-To: <20230224144513.GV11263@pengutronix.de>
On 24/02/2023 14:45, Michael Olbrich wrote:
> On Fri, Feb 24, 2023 at 12:03:14PM +0000, Ian Abbott wrote:
>> Hi Michael,
>>
>> Sorry to be a pain. I'm attempting to inject extra CFLAGS through the
>> toolchain wrappers, but I'm not sure how to do it. Here is one of my
>> attempts that does not work:
>>
>> #
>> ----------------------------------------------------------------------------
>> # Prepare
>> #
>> ----------------------------------------------------------------------------
>>
>> LIBTAHU_CONF_TOOL := NO
>>
>> #
>> ----------------------------------------------------------------------------
>> # Compile
>> #
>> ----------------------------------------------------------------------------
>>
>> # -D_TIME_BITS=64 requires -D_FILE_OFFSET_BITS=64
>> LIBTAHU_CPPFLAGS := -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
>> LIBTAHU_CFLAGS := -O2
>> LIBTAHU_MAKE_ENV := $(CROSS_ENV)
>> # Just build the dynamic library.
>> LIBTAHU_MAKE_OPT := \
>> $(CROSS_ENV_PROGS) \
>> lib/libtahu.so
>>
>> $(STATEDIR)/libtahu.compile:
>> @$(call targetinfo)
>> @$(call world/compile, LIBTAHU)
>> @$(call touch)
>>
>> I'm obviously missing something to pass the properly wrapped CC and CPP
>> variables (incorporating the extra flags) to 'make'. Could you provide a
>> clue how to fix it?
>
> Are you sure it does not work? It will not be visible in the regular make
> output. Run PTXdist with '-v' and then check platform-XXX/logfile.
>
> You should find a 'wrapper: ...' line for each compiler run and the extra
> flags should be visible here.
Oops, so they are! I never noticed. I understand what is going on now!
--
-=( 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 )=-
prev parent reply other threads:[~2023-02-24 16:10 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
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 [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=b40008a9-3146-e22b-cc32-3c3ea473a1fd@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