Re: PATCH: Put .gmo files in the build directory

[Andrew Cagney <ac131313 at ges dot redhat dot com>]

Has this been resolved?

Andrew

--- Begin Message ---

• From: Andrew Cagney <ac131313 at cygnus dot com>
• To: Ulrich Drepper <drepper at redhat dot com>, "H. J. Lu" <hjl at lucon dot org>
• Cc: binutils at sources dot redhat dot com
• Date: Mon, 24 Jun 2002 22:20:28 -0400
• Subject: Re: PATCH: Put .gmo files in the build directory
• References: <20020622215932.A27735@lucon.org> <1024809597.3437.86.camel@myware.mynet> <20020623083912.A11027@lucon.org> <1024847971.3437.93.camel@myware.mynet>

On Sun, 2002-06-23 at 08:39, H. J. Lu wrote:

I have some news for you. Please do this in the binutils build
directory:

It doesn't matter. Arguing with something that is wrong won't help. Beside, the intl/Makefile comes from the gettext package and you don't
want to diverge.

H.J. is right here. For GDB and BINUTILS, generated files are created in the BUILD tree - see c-exp.tab.c et.al. in GDB. The release process then uses smoke and mirrors to get those generated files bundled into a distro.

Given that this has all worked for longer than I remember - GDB also gets complaints about .gmo files being put in the [ro] src tree - I can't think why these files should be handled differently.

Which reminds me, gdb/394.

Andrew



--- End Message ---

--- Begin Message ---

• From: "H. J. Lu" <hjl at lucon dot org>
• To: Ulrich Drepper <drepper at redhat dot com>
• Cc: binutils at sources dot redhat dot com
• Date: Sun, 23 Jun 2002 08:39:12 -0700
• Subject: Re: PATCH: Put .gmo files in the build directory
• References: <20020622215932.A27735@lucon.org> <1024809597.3437.86.camel@myware.mynet>

On Sat, Jun 22, 2002 at 10:19:56PM -0700, Ulrich Drepper wrote:
> On Sat, 2002-06-22 at 21:59, H. J. Lu wrote:
> > This patch puts .gmo files in the build directory. It is useful for
> > read-only source.
> 
> This is completely against what the .gmo files are for.  Only
> maintainers are supposed to generate these files since they must be
> distributed.  And maintainers are not supposed to work with read-only
> sources for other reasons.

I have some news for you. Please do this in the binutils build
directory:

# find -name "*.[ch]"

There are quite a few files which are supposed to be distributed. It
is't even the complete list. The way we do it is:

# make binutils.tar.bz2 -f Makefile.in

in the source tree.


H.J.

--- End Message ---