Package description for 'ewl'

The Enlightenment Widget Library

 The Enlightenment Widget Library, a simple-to-use general purpose widget
 library based on the Evas canvas.

Various other information for package 'ewl'   (Repository 'e17')

URL: http://www.enlightenment.org

Author: Nathan Ingersoll <rbdpngn@users.sourceforge.net>
Maintainer: Mathieu Doidy <mdoidy@roulaize.net>

License: BSD
Status: Alpha
Version: 2005-09-11

Download: cvs://pserver:anonymous@enlightenment.cvs.sourceforge.net:/cvsroot/enlightenment::e17/libs/ewl/!2005-09-11/ ewl-2005-09-11.tar.bz2

Buildtime: 3401 (5) ERROR seconds (on reference hardware)
Buildtime: 3386 (9) ERROR seconds (on reference hardware)
Buildtime: 3383 (5) ERROR seconds (on reference hardware)
Buildtime: 3290 (9) ERROR seconds (on reference hardware)
Buildtime: 3315 (5) ERROR seconds (on reference hardware)
Buildtime: 3293 (9) ERROR seconds (on reference hardware)

ROCK Sources:  ewl.cacheewl.confewl.desc

Error Logs

[5-ERROR] checking dynamic linker characteristics... GNU/Linux ld.so
[5-ERROR] checking how to hardcode library paths into programs... immediate
[5-ERROR] checking whether stripping libraries is possible... yes
[5-ERROR] checking if libtool supports shared libraries... yes
[5-ERROR] checking whether to build shared libraries... yes
[5-ERROR] checking whether to build static libraries... yes
[5-ERROR] configure: creating libtool
[5-ERROR] appending configuration tag "CXX" to libtool
[5-ERROR] checking for ld used by g++-42... ld
[5-ERROR] checking if the linker (ld) is GNU ld... yes
[5-ERROR] checking whether the g++-42 linker (ld) supports shared libraries... yes
[5-ERROR] checking for g++-42 option to produce PIC... -fPIC
[5-ERROR] checking if g++-42 PIC flag -fPIC works... yes
[5-ERROR] checking if g++-42 static flag -static works... yes
[5-ERROR] checking if g++-42 supports -c -o file.o... yes
[5-ERROR] checking whether the g++-42 linker (ld) supports shared libraries... yes
[5-ERROR] checking dynamic linker characteristics... GNU/Linux ld.so
[5-ERROR] checking how to hardcode library paths into programs... immediate
[5-ERROR] appending configuration tag "F77" to libtool
[5-ERROR] checking if libtool supports shared libraries... yes
[5-ERROR] checking whether to build shared libraries... yes
[5-ERROR] checking whether to build static libraries... yes
[5-ERROR] checking for f77 option to produce PIC... -fPIC
[5-ERROR] checking if f77 PIC flag -fPIC works... no
[5-ERROR] checking if f77 static flag -static works... no
[5-ERROR] checking if f77 supports -c -o file.o... no
[5-ERROR] checking whether the f77 linker (ld) supports shared libraries... yes
[5-ERROR] checking dynamic linker characteristics... ./configure: line 1: f77: command not
 found
[5-ERROR] GNU/Linux ld.so
[5-ERROR] checking how to hardcode library paths into programs... immediate
[5-ERROR] checking for __attribute__... yes
[5-ERROR] checking for evas-config... no
[5-ERROR] checking for evas - version >= 0.9.9... no
[5-ERROR] *** The evas-config script installed by evas could not be found
[5-ERROR] *** If evas was installed in PREFIX, make sure PREFIX/bin is in
[5-ERROR] *** your path, or set the EVAS_CONFIG environment variable to the
[5-ERROR] *** full path to evas-config.
[5-ERROR] ERROR:
[5-ERROR] The evas-config development script was not found in your execute
[5-ERROR] path. This may mean one of several things
[5-ERROR] 1. You may not have installed the evas-devel (or evas-dev)
[5-ERROR]    packages.
[5-ERROR] 2. You may have evas installed somewhere not covered by your path.
[5-ERROR] 
[5-ERROR] If this is the case make sure you have the packages installed, AND
[5-ERROR] that the evas-config script is in your execute path (see your
[5-ERROR] shell's manual page on setting the $PATH environment variable), OR
[5-ERROR] alternatively, specify the script to use with --with-evas-config.
[5-ERROR] configure: error: Fatal Error: no evas-config detected.
[5-ERROR] --- BUILD ERROR ---

[9-ERROR] checking dynamic linker characteristics... GNU/Linux ld.so
[9-ERROR] checking how to hardcode library paths into programs... immediate
[9-ERROR] checking whether stripping libraries is possible... yes
[9-ERROR] checking if libtool supports shared libraries... yes
[9-ERROR] checking whether to build shared libraries... yes
[9-ERROR] checking whether to build static libraries... yes
[9-ERROR] configure: creating libtool
[9-ERROR] appending configuration tag "CXX" to libtool
[9-ERROR] checking for ld used by g++-42... ld
[9-ERROR] checking if the linker (ld) is GNU ld... yes
[9-ERROR] checking whether the g++-42 linker (ld) supports shared libraries... yes
[9-ERROR] checking for g++-42 option to produce PIC... -fPIC
[9-ERROR] checking if g++-42 PIC flag -fPIC works... yes
[9-ERROR] checking if g++-42 static flag -static works... yes
[9-ERROR] checking if g++-42 supports -c -o file.o... yes
[9-ERROR] checking whether the g++-42 linker (ld) supports shared libraries... yes
[9-ERROR] checking dynamic linker characteristics... GNU/Linux ld.so
[9-ERROR] checking how to hardcode library paths into programs... immediate
[9-ERROR] appending configuration tag "F77" to libtool
[9-ERROR] checking if libtool supports shared libraries... yes
[9-ERROR] checking whether to build shared libraries... yes
[9-ERROR] checking whether to build static libraries... yes
[9-ERROR] checking for f77 option to produce PIC... -fPIC
[9-ERROR] checking if f77 PIC flag -fPIC works... no
[9-ERROR] checking if f77 static flag -static works... no
[9-ERROR] checking if f77 supports -c -o file.o... no
[9-ERROR] checking whether the f77 linker (ld) supports shared libraries... yes
[9-ERROR] checking dynamic linker characteristics... ./configure: line 1: f77: command not
 found
[9-ERROR] GNU/Linux ld.so
[9-ERROR] checking how to hardcode library paths into programs... immediate
[9-ERROR] checking for __attribute__... yes
[9-ERROR] checking for evas-config... no
[9-ERROR] checking for evas - version >= 0.9.9... no
[9-ERROR] *** The evas-config script installed by evas could not be found
[9-ERROR] *** If evas was installed in PREFIX, make sure PREFIX/bin is in
[9-ERROR] *** your path, or set the EVAS_CONFIG environment variable to the
[9-ERROR] *** full path to evas-config.
[9-ERROR] ERROR:
[9-ERROR] The evas-config development script was not found in your execute
[9-ERROR] path. This may mean one of several things
[9-ERROR] 1. You may not have installed the evas-devel (or evas-dev)
[9-ERROR]    packages.
[9-ERROR] 2. You may have evas installed somewhere not covered by your path.
[9-ERROR] 
[9-ERROR] If this is the case make sure you have the packages installed, AND
[9-ERROR] that the evas-config script is in your execute path (see your
[9-ERROR] shell's manual page on setting the $PATH environment variable), OR
[9-ERROR] alternatively, specify the script to use with --with-evas-config.
[9-ERROR] configure: error: Fatal Error: no evas-config detected.
[9-ERROR] --- BUILD ERROR ---