Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kamil Rytarowski <n54@gmx.com>
To: gdb@sourceware.org, Pedro Alves <palves@redhat.com>,
	Sergio Durigan Junior <sergiodj@sergiodj.net>
Subject: Re: gettext.m4 update
Date: Wed, 13 Sep 2017 11:53:00 -0000	[thread overview]
Message-ID: <fef2835a-427f-8217-a357-9397410d96fc@gmx.com> (raw)
In-Reply-To: <7925cdff-cd6d-2242-0c4b-55daa9e53664@gmx.com>


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

On 11.09.2017 15:36, Kamil Rytarowski wrote:
> Hello,
> 
> The current gettext.m4 bundled into GDB is too old for the NetBSD case.
> 
> We mark GDB as BROKEN_GETTEXT_DETECTION and comment that it fails to add
> -lintl to the linker command line.
> 
> Could we please update it to a newer version?
> 
> gettext.m4 is located in https://ftp.gnu.org/pub/gnu/gettext/
> 

I know what breaks the NetBSD buildbot [1].

The following rule (intl/Makefile.in) [2] breaks:

.c.o:
	$(COMPILE) $<

.y.c:
	$(YACC) $(YFLAGS) --output $@ $<
	rm -f $*.h

This means that if plural.y is newer than plural.c it will be regenerated.

There is required Bison < 3.0 (the last one used for regeneration was
1.35), which is already too old to keep it around.

Git does not track mtime in files, and this enforces regeneration of
plural.c, at least in random checkouts. The NetBSD buildbot was
unfortunate to get plural.y newer:

$ stat -f %Fm ./binutils-gdb-master/intl/plural.c
1477324070.931854837
$ stat -f %Fm ./binutils-gdb-master/intl/plural.y
1477324070.931949821


The cleanest and newfangled solution would be to upgrade to newer
gettext and enforce regeneration always.

A kludge would be to insert touch(1) call before execution of intl/Makefile.

I don't know about any good solutions in the middle.

[1]
https://gdb-build.sergiodj.net/builders/NetBSD-x86_64-m64/builds/2456/steps/compile%20gdb/logs/stdio

[2]
https://github.com/wallento/binutils-gdb/blob/master/intl/Makefile.in#L135


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

  reply	other threads:[~2017-09-13 11:53 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 [this message]
2017-09-13 13:15   ` Pedro Alves
2017-09-13 13:21     ` Andreas Schwab
2017-09-13 13:37       ` Kamil Rytarowski

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=fef2835a-427f-8217-a357-9397410d96fc@gmx.com \
    --to=n54@gmx.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --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