This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch/rfc] Enable PO files.


"Andrew" == Andrew Cagney <cagney@gnu.org> writes:


Andrew> - the output is put in the _build_ directory (instead of RO srcdir)

The only issue with this, I think, is how releases are made -- but I
see from the patch that you already dealt with this.

Andrew> - insisted on using ../intl/
Andrew> I didn't borrow that - GDB will still use an installed intl/ (I'm
Andrew> wondering if its time to boot intl/ out of GDB's distro).

Hmm, I thought the point of doing this is that the stuff in intl,
while readily available on Linux boxes, isn't so available elsewhere.
I could be behind the times, though, I haven't looked at the nuts and
bolts of gettext building in years.

GCC appears to insist on using intl/ instead of using the installed stuff when available?


Do we [gdb] also want to be in the business of maintaining a local intl/?

Andrew> +      find * \
Andrew> +	  -name '*-stub.c' -prune -o \
Andrew> +	  -name 'testsuite' -prune -o \
Andrew> +	  -name 'init.c' -prune -o \
Andrew> +	  -name '*.[hc]' -print

I never liked using find for things like this, since I tend to push
files out of the way by "mv foo.c hacked-foo.c", but I can understand
why you'd do it this way.  I suppose it could only negatively affect
some subset of "real gdb developers" anyway, provided releases are
always done from a pristine checkout.

yes, and yes.


Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]