Re: [Pan-users] Re: Pan 0.122 won't 'make'

[Charles Kerr]

Per Hedeland wrote:
> Charles Kerr <address@hidden> wrote:
> > Rhialto wrote:
> > > On Sun 04 Feb 2007 at 04:12:47 +0000, walt wrote:
> > > > Are you compiling on a non-linux system?  I'm wondering if you need to
> > > > use 'gmake' instead of 'make'.  Just a wild guess.
> > > Before, as I reported, it always worked with standard make rather than
> > > gmake.
> > For what it's worth, nothing's been changed in the autoconf parts, or in
> > the po directory (except for updated translations).
>
> Sorry, but this is clearly not the case: po/Makefile.in.in now uses the
> gmake-specific $(shell ...) construct:
>
> $ grep shell pan-0.121/po/Makefile.in.in
> $ grep shell pan-0.122/po/Makefile.in.in
> PO_LINGUAS=$(shell if test -r $(srcdir)/LINGUAS; then grep -v "^\#" 
> $(srcdir)/LINGUAS; fi)
> POFILES=$(shell if test -n "$(PO_LINGUAS)"; then LINGUAS="$(PO_LINGUAS)"; else 
> LINGUAS="$(ALL_LINGUAS)"; fi; for lang in $$LINGUAS; do printf "$$lang.po "; done)
> CATALOGS=$(shell if test -n "$(PO_LINGUAS)"; then LINGUAS="$(PO_LINGUAS)"; else 
> LINGUAS="$(ALL_LINGUAS)"; fi; for lang in $$LINGUAS; do printf "$$lang.gmo "; done)
>
> The toplevel configure still sets POFILES and CATALOGS in .122, but
> these settings are apparently thrown away; PO_LINGUAS seems to be new in
> .122.

Makefile.in.in isn't in Pan's svn tree; it's added by autoconf.
Hence the rest of my mail which wondered if my fedora updates
had introduced changes in autoconf.

Thanks for detailing the problem.  I'll roll a new
tarball tomorrow on a less bleeding-edge machine.

cheers,
Charles