Stupid question, but did you run ldconfig after building evas?Originally Posted by KageKeeper
Stupid question, but did you run ldconfig after building evas?Originally Posted by KageKeeper
-- UDSF | Tango Desktop Project --
-- openSUSE 11.3 / Ubuntu 10.04 --
Not if he was using the script, unless the script calls ldconfig after each build.Originally Posted by darkmatter
My sole duty is to my own happiness and well-being. I recognize no other.
He had stated in his post that he was trying the MANUAL build, which is why I asked...Originally Posted by Stormy Eyes
-- UDSF | Tango Desktop Project --
-- openSUSE 11.3 / Ubuntu 10.04 --
Not a stupid question, but yes, I ran sudo ldconfig after building evas.Originally Posted by darkmatter
Attempted fr0om script and came to this. I searched for some indication of how to fix this but came up with nothing.
Any suggestions as to what I should do?Code:=== Building: e17/libs/engrave... === make: *** No rule to make target `clean'. Stop. => Autofoo: e17/libs/engrave Running aclocal... Running autoheader... configure.in:17: warning: AC_PROG_LEX invoked multiple times autoconf/programs.m4:438: AC_DECL_YYTEXT is expanded from... aclocal.m4:7017: AM_PROG_LEX is expanded from... configure.in:17: the top level Running autoconf... configure.in:17: warning: AC_PROG_LEX invoked multiple times autoconf/programs.m4:438: AC_DECL_YYTEXT is expanded from... aclocal.m4:7017: AM_PROG_LEX is expanded from... configure.in:17: the top level Running libtoolize... Running automake... Makefile.am:2: require version 1.5, but have 1.4-p6 src/bin/Makefile.am:1: require version 1.5, but have 1.4-p6
I wonder how many years E17 will be "bleeding edge"?
I wonder if it'll make the decade mark?
I don't remember what the first E17/EFM announcement was, or when, but the oldest I could find was more than five years ago, and I could have sworn I'd read about e17 code in '99, which would make it more like 6 years, which means we're more than halfway to the decade point.
Can't wait until 2009, when the next e17 rewrite goes pre-alpha!
Do a:Originally Posted by elpresidente
And you should be ok I think.Code:sudo apt-get install automake1.5
Just tried it and got:Originally Posted by KageKeeper
Code:Package automake1.5 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package automake1.5 has no installation candidate
Oops...I meant automake1.7Originally Posted by elpresidente
Same command, but 1.7. That is what is required anyway.
Sorry.
Originally Posted by KageKeeperHmmm. Doesn't quite make sense to me.Code:Reading package lists... Done Building dependency tree... Done automake1.7 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
Bookmarks