Ok, ecore is compiled on both systems now. ;)
Here's what the config.log said:
--
configure:1916: $? = 1
configure:1940: checking for C compiler default output
configure:1943: gcc -liconv conftest.c >&5
configure:1946: $? = 0
configure:1992: resul
On Fri, 2004-03-12 at 09:26 -0800, Philip Snyder wrote:
> checking whether the C compiler works... configure: error: cannot run C
> compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
>
Did you check config.log to see what it said about that err
Well, that worked for my RH9 box at home... so I was all excited.
However, it didn't work for my Fedora box here at work. Any other ideas?
:)
On my Fedora box, it won't even let me run ./configure with the LDFLAGS
set... here's what it says to that:
[EMAIL PROTECTED] ecore]$ LDFLAGS="-liconv" ./c
On Thu, 2004-03-11 at 22:09 -0800, Philip Snyder wrote:
>
> I've got libiconv-1.9.1 installed. Error listed below.
>
> /home/philip/cvs/e17/libs/ecore/src/lib/ecore_txt/.libs/libecore_txt.so:
> undefined reference to `libiconv_clos
> e'
> /home/philip/cvs/e17/libs/ecore/src/lib/ecore_txt/.libs/l
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
