Re: [E-devel] CVS eas

[Lyle K. <te...@ke...>]

* Robin Van Loock (she...@ho...) wrote:
> >Let's start with, a) distro, b) version of distro, c) version of config
> >tools (autoconf, automake, libtool), etc. Warnings from config.log about
> >unfound stuff..
> Ok, I may have been giving the wrong idea here. It has improved a lot, and 
> the config script hacking required was many times related to the quirks of 
> my system (like dropping gtk support because the 'which' command for finding 
> gtk-config doesn't exist) than to the libs themselves.
> 
> I did check out the evas problem, and it was indeed the 
> 'else-block-problem', happened exactly in the same line the original poster 
> said. Happens once again after that, and both seem to be part of a GL/GLU 
> check.
> 
> I currently don't use a distro as I threw something together from scratch 
> (www.linuxfromscratch.org), which again proves that many of the problems may 
> indeed be system-related. If it would help for the problem above, autoconf 
> was 2.5, automake was 1.4-p4 and libtool was 1.4.

I didn't want to leave you hanging unanswered.. from elsewhere on the
list, autoconf 2.5 appears to be the culprit, in that something in the
interface, at least, changed between 2.13 and 2.5. Anyone that wants to
submit a patch to make 2.5 work is welcome to, as long as they realize
that we're going to make sure it works with 2.13 for ourselves (I'm
still running 2.13, for instance) before it gets committed, and if we
have to make changes, we'll want to continue to verify it works for
both. :) But there seems to be something going on here.

> The big problems I once had were all under Slackware 7, and by seeing how 
> much better it works under a from-scratch system, I do suspect many of the 
> problems were due to Slackware subtleties (perhaps someone using slack could 
> check that out).

We've gotten several reports of problems configuring things on
slackware. I'm not exactly sure why, as each of the people I've spoken
to seems to have hacked up their installation of it to the point where
it could be pretty much anything. But it seems to be particular to
slackware users.

Anyway, if someone has a patch, feel free to send it to me. I'll try to
find a few minutes to test it against 2.13 and commit it.

term