On Wed, 31 Mar 2010, Dave Ray wrote:
>>
>> if you just configured with
>>
>> LUA_CFLAGS="-I/my/prefix/include" LUA_LIBS="-L/my/prefix/lib" ./configure
>>
>> then it's normal.
>>
>> Try
>>
>> LUA_CFLAGS="-I/my/prefix/include" LUA_LIBS="-L/my/prefix/lib -llua"
>> ./configure
did you read **carefully** the above line. See the
-llua
that i have added
Vincent
>>
>> I prefer at least adding some options to configure rather than doing that.
>>
>> Vincent
>
> You are correct, that's exactly how I did it.
>
> As I mentioned in my last post, the original problem I posted about was
> resolved. Adding those env variables allowed EDJE to find LUA and I can run
> ./autogen.sh without errors. EDJE found LUA.
>
> bash> export LUA_CFLAGS="-I/usr/local/include"
> bash> export LUA_LIBS="-L/usr/local/lib"
> bash> env | grep LUA
> LUA_LIBS=-L/usr/local/lib
> LUA_CFLAGS=-I/usr/local/include
> bash>
>
> I am now having a different problem. "make" fails with hundreds of unresolved
> symbols containing "LUA" in their names. I feel it's safe to assume that the
> problem ("make" failing) is still related to the relationship between EDJE
> and LUA on a MacOS-X environment.
>
> There may be a real problem with the liblua.a file, although "make test" in
> lua was successful. Or EDJE is getting something unexpected from LUA during
> "make".
>
> If anyone cares I can post some of the error messages.
>
> Dave
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
