In article <19118.1705868...@jacaranda.noi.kre.to>, Robert Elz <k...@munnari.oz.au> wrote: > Date: Sun, 21 Jan 2024 18:16:28 -0000 (UTC) > From: chris...@astron.com (Christos Zoulas) > Message-ID: <uojn1s$kid$1...@ciao.gmane.io> > > | I think this is the yacc used by the build process, not the yacc > | to build tools with? I.e. will this yacc produce c files usable in > | the host compilation environment? > >I was also looking at that problem, but in a different direction. >Rather than making -d work in the tools date (either by somehow >making parsedate work - which really isn't worth the effort for >this, or via your hack) but by using -j and specifying the date >in canonincal form instead of parsedate random form. > >That is, it is trivial to make > > date -j '+whatever format you like' 202401220314 > >work (including in the tools date), provided you can convert the date >string you're starting with into that canonical form - that takes make >magic, a topic of which I am barely aware exists, let alone competant, >so that was as far as I took it...
I should have thought of that, duh. This means adding 4 0's in the Makefile... christos
