Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kamil Rytarowski <n54@gmx.com>
To: Andreas Schwab <schwab@suse.de>, Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org, Sergio Durigan Junior <sergiodj@sergiodj.net>
Subject: Re: gettext.m4 update
Date: Wed, 13 Sep 2017 13:37:00 -0000	[thread overview]
Message-ID: <107afdd8-1dae-f89d-e762-2e83314a75bf@gmx.com> (raw)
In-Reply-To: <mvmlgliag4q.fsf@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]

On 13.09.2017 15:21, Andreas Schwab wrote:
> On Sep 13 2017, Pedro Alves <palves@redhat.com> wrote:
> 
>> Maybe the bot should be doing a recursive touch(1) of all files
>> after checkout, forcing the same mtime on all checked-out files,
>> with 'touch -d ..' or 'touch -p ..' or
>> 'touch -r .git/FETCH_HEAD' or something like that.
> 
> Or touch each file to the ctime of the last commit that modified it.
> 
> Andreas.
> 


There are available some workarounds on stackoverflow:

https://stackoverflow.com/a/39192796

I've touch(1)ed plural.c for the bot's checkout and the NetBSD bot can
accomplish the build!

https://gdb-build.sergiodj.net/builders/NetBSD-x86_64-m64/


Long term it's best to switch to newer tools, but I imagine it's not
doable as-is.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 850 bytes --]

      reply	other threads:[~2017-09-13 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 13:34 Kamil Rytarowski
2017-09-13 11:53 ` Kamil Rytarowski
2017-09-13 13:15   ` Pedro Alves
2017-09-13 13:21     ` Andreas Schwab
2017-09-13 13:37       ` Kamil Rytarowski [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=107afdd8-1dae-f89d-e762-2e83314a75bf@gmx.com \
    --to=n54@gmx.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=schwab@suse.de \
    --cc=sergiodj@sergiodj.net \
    /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