GNU bug report logs - #64984
call to date(1) uses non-portable flag

Previous Next

Package: guile;

Reported by: Sevan Janiyan <venture37 <at> geeklan.co.uk>

Date: Tue, 1 Aug 2023 01:24:02 UTC

Severity: normal

To reply to this bug, email your comments to 64984 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guile <at> gnu.org:
bug#64984; Package guile. (Tue, 01 Aug 2023 01:24:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Sevan Janiyan <venture37 <at> geeklan.co.uk>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Tue, 01 Aug 2023 01:24:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sevan Janiyan <venture37 <at> geeklan.co.uk>
To: bug-guile <at> gnu.org
Subject: call to date(1) uses non-portable flag
Date: Tue, 1 Aug 2023 02:23:13 +0100

Hi,
In libguile/Makefile there is a call to date(1) for recording the build 
stamp as so:
  @BUILD_DATE="$${SOURCE_DATE_EPOCH:-`date '+%s'`}" ; \
   echo ' { "buildstamp",    "'`date -u +'%Y-%m-%d %T' -d 
@$$BUILD_DATE`'" }, \' >> libpath.tmp

The -d flag doesn't necessarily mean the same thing across different 
operating systems, e.g on macOS it means "Set the kernel's value for 
daylight saving time." vs the coreutils version which means "display 
time described by STRING, not 'now'"

The command errors but the build continues so it is non-fatal which is 
perhaps why it has gone undetected?



Sevan
This bug report was last modified 1 year and 150 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.