Well, this is getting quite fun - but then again, I signed up for it
happy and willing so you won't hear me complain. ;)
Anyway, I had the same problem with compiling evas as stated earlier on
my RH9 system, but not on my Fedora system at work. I opted for the
"comment out the conditional check in
On Thu, 11 Mar 2004 08:09:01 -0500 Kyle Gonzales <[EMAIL PROTECTED]> babbled:
(B
(B> -BEGIN PGP SIGNED MESSAGE-
(B> Hash: SHA1
(B>
(B> I'm using a RH9 box, and I got the same error.
(B>
(B> There is a line that checks for C++ usage within an if statement in the
(B> code. apparen
On Thu, 11 Mar 2004 12:41:18 - Ant Allen <[EMAIL PROTECTED]>
(Bbabbled:
(B
(B>
(B>
(B> On Thu, 11 Mar 2004 08:02:11 +0900, Carsten Haitzler
(B> <[EMAIL PROTECTED]> wrote:
(B>
(B> > yes. sorry about all this but evas, ecore etc. all changed dramatically
(B> > since
(B> > the prese
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because I do not think the same check is made with imlib2 or edb or eet.
In fact, the problem in evas was in the Qtopia section, which I don't
even use.
Chema Ollés wrote:
Thanks but I can't understand why if I have the same "check" when
compiling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chema Ollés escribió:
| Kyle Gonzales escribió:
| | I'm using a RH9 box, and I got the same error.
| |
| | There is a line that checks for C++ usage within an if statement in the
| | code. apparently, some versions of the auto tools don't like that. M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kyle Gonzales escribió:
| I'm using a RH9 box, and I got the same error.
|
| There is a line that checks for C++ usage within an if statement in the
| code. apparently, some versions of the auto tools don't like that. My
| solution was to remove the t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm using a RH9 box, and I got the same error.
There is a line that checks for C++ usage within an if statement in the
code. apparently, some versions of the auto tools don't like that. My
solution was to remove the test from the if statement.
If
On Thu, 11 Mar 2004 08:02:11 +0900, Carsten Haitzler
<[EMAIL PROTECTED]> wrote:
yes. sorry about all this but evas, ecore etc. all changed dramatically
since
the presentation and documentation you have, there's explanations in the
new
evas docs u'll find in the evas src if u have doxygen inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody:
I obtain this error when I try compiled cvs evas lib --->>>
configure: error: conditional "am__fastdepCXX" was never defined.
Usually this means the macro was only invoked conditionally.
Any idea?
I use automake 1.7 autoconf 2.57 with make
