config.status: error: cannot find input file: `po/Makefile.in.in'

2013-05-19 Thread Kip Warner
Hey list, I have my message catalogues in a directory in my project other than in the usual po/. I ran gettextize --po-dir=folder. I also updated Makevars's subdir to point to the new directory. The SUBDIRS variable in my Makefile.am also points to the right location. However, the error I am rece

Re: config.status: error: cannot find input file: `po/Makefile.in.in'

2013-05-19 Thread Gavin Smith
On Sun, May 19, 2013 at 9:57 AM, Kip Warner wrote: > Hey list, > > I have my message catalogues in a directory in my project other than in > the usual po/. I ran gettextize --po-dir=folder. I also updated > Makevars's subdir to point to the new directory. The SUBDIRS variable in > my Makefile.am a

Re: config.status: error: cannot find input file: `po/Makefile.in.in'

2013-05-19 Thread Kip Warner
On Sun, 2013-05-19 at 10:38 +0100, Gavin Smith wrote: > Do you still have a reference to "po" in configure.ac? Sections 13.4 > and 13.4.5 in the gettext manual look relevant to your problem. Hey Gavin. I already went through the manual, but I'm guessing I must have missed something. Indeed, I had.

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-19 Thread Pavel Raiskup
+cc config-patc...@gnu.org, Ben Elliston > IME, it is much better when any override mechanism make use of > environment variables. Yes, it was mentioned multiple times in this thread already and it was always forgotten. Please consider this approach. One thing was not mentioned here - if there

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-19 Thread Paul Wise
On Mon, 2013-05-20 at 07:40 +0200, Pavel Raiskup wrote: > Yes, it was mentioned multiple times in this thread already and it was > always forgotten. Please consider this approach. The patches I've posted include environment variables too. > One thing was not mentioned here - if there was a CONF

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-19 Thread Pavel Raiskup
> > pros: we are able to easily patch also old packages (no-need to > > autoreconfigure) > > There would still be a long bootstrap period where old tarballs would > not have any way of running a modern config.sub/guess other than copying > them in from the system versions. I meant that you are ab

Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems

2013-05-19 Thread Paul Wise
On Mon, 2013-05-20 at 08:43 +0200, Pavel Raiskup wrote: > I meant that you are able to patch the very small part of > config.guess/config.sub with checking for environmental variables and > thats all -> you don't have to touch this package in future. The patched > config.sub is able to call syste