public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/13485] New: [3.4 regression] Generated files no longer get messages extracted
Date: Wed, 24 Dec 2003 20:39:00 -0000	[thread overview]
Message-ID: <20031224202101.13485.jsm28@gcc.gnu.org> (raw)

With generated files no longer in the source directory, the messages from
them no longer get extracted by exgettext for gcc.pot (unless old generated
files were lying around in the build directory).

A proper fix probably involves each Make-lang.in listing the generated files
in that language from which messages should be extracted (so that the
dependencies on those files, which never were right, can be correct) and
Makefile.in then passing the list of all those files (and options.c, currently
handled specially) to exgettext.

-- 
           Summary: [3.4 regression] Generated files no longer get messages
                    extracted
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jsm28 at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,kcook at gcc dot gnu dot
                    org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13485


             reply	other threads:[~2003-12-24 20:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 20:39 jsm28 at gcc dot gnu dot org [this message]
2003-12-24 20:42 ` [Bug other/13485] " pinskia at gcc dot gnu dot org
2004-01-14 13:57 ` steven at gcc dot gnu dot org
2004-01-14 14:16 ` jsm at polyomino dot org dot uk
2004-01-14 17:04 ` kcook at gcc dot gnu dot org
2004-01-14 17:22 ` jsm at polyomino dot org dot uk
2004-02-06  2:47 ` [Bug other/13485] [3.4/3.5 " pinskia at gcc dot gnu dot org

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=20031224202101.13485.jsm28@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).