Paul Eggert ([EMAIL PROTECTED]) wrote: > > The question remains: how to easily solve the problem of invoking custom > > 'configure' script in one of the sub-package directories? > > What I'd do is put the sub-package one level further down, and > use my own configure.ac that generates a configure that invokes > the sub-configure with the proper arguments.
Well, sub-package (clisp) is already down enough, and its configure script is invoked with a simple hand-written 'configure' script (656 bytes), and at the moment everything works, but I have to manually invoke the sequence: automake && autoconf && configure && ... (actually I put it in the script, but that's what autoreconf is supposed to do.) So, the build process works, but I'm interested whether the error message from th Subject: is autoreconf bug or its limitation? Sincerely, Gour -- Registered Linux User | #278493 GPG Public Key | 8C44EDCD
