[E-devel] Problems with building engage from cvs

Didier Casse <didier.casse <at> gmail.com>
2005-03-01 03:13:54 GMT

It's the first time that I get these errors:
==================================================================
[SNIP]
checking for evas-config... /usr/local/bin/evas-config
checking for evas - version >= 1.0.0... ./configure: line 22076: test:
0.001: in
teger expression expected
yes
checking for ewl-config... /usr/local/bin/ewl-config
checking for ewl - version >= 0.0.1... ./configure: line 22237: test:
0.001: int
eger expression expected
yes
checking for enlightenment-config... no
checking for enlightenment - version >= 0.0.1... no
*** The enlightenment-config script installed by enlightenment could
not be foun
d
*** If enlightenment was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the ENLIGHTENMENT_CONFIG environment variable to the
*** full path to enlightenment-config.
configure: error: Cannot find ewl: Is enlightenment-config in path?
error: Bad exit status from /var/tmp/rpm-tmp.39651 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.39651 (%build)
==================================================================
Hmm.. and I've installed and build ewl version:

Re: [E-devel] Problems with building engage from cvs

Michael Jennings <e-devel <at> kainx.org>
2005-03-01 03:51:23 GMT

On Tuesday, 01 March 2005, at 11:13:54 (+0800),
Didier Casse wrote:
> It's the first time that I get these errors:
>
> ==================================================================
> [SNIP]
> checking for evas-config... /usr/local/bin/evas-config
> checking for evas - version >= 1.0.0... ./configure: line 22076: test:
> 0.001: in
> teger expression expected
> yes
> checking for ewl-config... /usr/local/bin/ewl-config
> checking for ewl - version >= 0.0.1... ./configure: line 22237: test:
> 0.001: int
> eger expression expected
> yes
> checking for enlightenment-config... no
> checking for enlightenment - version >= 0.0.1... no
> *** The enlightenment-config script installed by enlightenment could
> not be foun
> d
> *** If enlightenment was installed in PREFIX, make sure PREFIX/bin is in
> *** your path, or set the ENLIGHTENMENT_CONFIG environment variable to the
> *** full path to enlightenment-config.
> configure: error: Cannot find ewl: Is enlightenment-config in path?
> error: Bad exit status from /var/tmp/rpm-tmp.39651 (%build)
What, you mean that silly .001 thing that was supposed to be a magical
cure actually *wasn't*? But that can't be! It was for the good of

Re: [E-devel] Problems with building engage from cvs

Mike Frysinger <vapier <at> gentoo.org>
2005-03-01 04:22:17 GMT

On Monday 28 February 2005 10:13 pm, Didier Casse wrote:
> All other stuff have compiled except for engage. Let me get this
> straight, does that mean that E 0.16.999 should be installed first?
it would look that way :)
previous versions of engage did not have this requirement, but i guess that's
been changed (havent been tracking engage dev myself)
-mike
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [E-devel] Problems with building engage from cvs

Mike Frysinger <vapier <at> gentoo.org>
2005-03-01 05:43:28 GMT

On Monday 28 February 2005 10:51 pm, Michael Jennings wrote:
> What, you mean that silly .001 thing that was supposed to be a magical
> cure actually *wasn't*? But that can't be! It was for the good of
> the code!
this little rant is unrelated to the actual bug mentioned ... the fact that
there's ugly 'test: integer expression expected' doesnt affect the missing
e17 config script (the real cause of build failure)
and really, that ugly output is a moot point ... the old versioning schema had
the same problem, except it'd complain about '_pre'/'_alpha'/whatever not
being an integer expression
-mike
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [E-devel] Problems with building engage from cvs

Andrew Elcock <andy <at> elcock.org>
2005-03-01 10:21:39 GMT

Didier Casse wrote:
> It's the first time that I get these errors:
> *** The enlightenment-config script installed by enlightenment could
> not be foun
> d
>
> All other stuff have compiled except for engage. Let me get this
> straight, does that mean that E 0.16.999 should be installed first?
>
Apologies this should have been optional - and has been fixed (also it
was a typo, looking for enlightenment > 16.999, not ewl > 0.0.1
Andy
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [E-devel] Problems with building engage from cvs

Michael Jennings <e-devel <at> kainx.org>
2005-03-01 15:39:18 GMT

On Tuesday, 01 March 2005, at 15:56:33 (+0900),
Carsten Haitzler wrote:
> no one said it was a magical cure. it was a fixup of doing hack of
> _preX after the version to turn it into a raw numeric.
Okay, then explain to me why you added the .001 to 18 packages in CVS
when ONLY THREE of them had _pre in the version.
> no u didn't :) this is irrelevant. i repeat - the .001 REPLACED _preXX
Again...see above. You still have not responded to this even though
I've asked twice.
> now purely numeric which makes it easier/possible to compare trivially
You still haven't solved the fundamental problem of comparing
non-integers. .001 is no more of an integer than .pre_XX
> allows for automated snapshots. people accuse us of never releasing
> anything - but a big reason is that making a release is a PAIN IN
> THE ARSE because its 20 different packages that all need
> bumping. this is a step in trying to fix that.
I don't understand how changing 18 different snapshot numbers on a
weekly (or more) basis is easier than changing 18 different version
numbers on a bi-monthly or tri-monthly basis.
Michael

Re: [E-devel] Problems with building engage from cvs

Michael Jennings <e-devel <at> kainx.org>
2005-03-01 15:43:11 GMT

On Tuesday, 01 March 2005, at 06:44:19 (+0100),
Cristalle Azundris Sabon wrote:
> Not to mention that in my last checkout, the .spec files did not
> reflect these changes. Can we establish the rule that (collective)
> you DON'T change the version number UNLESS you also fix the spec?
> Thanks.
As I was going to tell that other guy (Richard?), I haven't updated
the spec files because I'm still trying to understand the logic behind
changing 18 packages to fix 3.
The spec files already had the "snapshot" functionality in them, so I
just reverted the change on the 15 packages that didn't need it.
Some discussion of this BEFORE the change was made would've been
nice. But then, I guess that's not the way things happen around here.
Michael
--
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <mej <at> kainx.org>
n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
"As your attorney, it is my duty to inform you that it is not
important that you understand what I'm doing or why you're paying
me so much money. What's important is that you continue to do so."
-- Hunter S. Thompson's Attorney
-------------------------------------------------------