gdavis7 at umbc.edu
Tue Oct 23 09:37:45 PDT 2001
Try also cleaning out the directory and its config.cache after you
downgrade autoconf. In fact, just untar the tarball all over again and
start fresh, after the downgrade of course. It is always helpful to do a
make clean before you acutally start to build your programs. It is always
possible that the person who tarred the ball left some object files in,
though cleaning them out would be more of an optimization benefit rather
than to overcome compiler errors.
Aside: KDE and many programs written for its libraries do not use autoconf
2.x well. KDE even states on their website that you should not use
autoconf 2.x for compiling their stuff. What is the benefit of the newer
autoconf major version? Why won't KDE developers bump up their code to use
it? Why is it used in LFS?
> On Thursday 18 October 2001 13:12, you wrote:
>> IIRC, I've fixed problems of this nature by up- or down-grading
>> autoconf. Generally, the latest version does _not_ play well with KDE
>> stuff; fall back to 1.4 or 1.4p and see if the problem goes away.
> Thanks John,
> did it, but the error remains the same.
"I will share all with you whenever you wish
and do so without ambition, from which I am more exempt
and more distant than any man in the world"
Pierre de Fermat
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-support' in the subject header of the message
More information about the blfs-support