The spec.in was using the autofuck macro @MODULE_ARCH@ to determine the installation path for the .so's, @MODULE_ARCH@ is defined as MODULE_ARCH="$host_os-$host_cpu", which is fine and dandy so long as your building packages for the same arch as the host CPU, but not fine and dandy if you're building for another one ( i.e. building i586 packages on an i686) :P

On 1/25/06, Michael Jennings <[EMAIL PROTECTED]> wrote:
On Tuesday, 24 January 2006, at 19:37:17 (-0800),
E CVS List wrote:

> Enlightenment CVS committal
>
> Author  : quan74
> Project : e17
> Module  : libs/evas
>
> Dir     : e17/libs/evas
>
>
> Modified Files:
>       evas.spec.in
>
>
> Log Message:
> fixed arch problem in spec

Care to elaborate?  It worked properly for me.

Michael

--
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <[EMAIL PROTECTED]>
n + 1, Inc., http://www.nplus1.net/       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
"Temper is the one thing you can't get rid of by losing it."
                                 -- Jack Nicholson, "Anger Management"


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to