Another thing you can do, if you don't mind not having latest code and don't want to compile everything, usign E's debian repos in http://packages.enlightenment.org/
deb http://packages.enlightenment.org/debian/ squeeze main extras On Mon, May 3, 2010 at 11:55 PM, Danny <dannydeb...@gmail.com> wrote: > Hi guys, > > I have been using DR17 a few years ago, maybe almost 2 years. The last time I > downloaded DR17 all the files I needed was at > download.enlightenment.org/snapshots/LATEST. > > A few days ago I went there again and downloaded the files as I used to do. I > also compiled it in the wy I used to. > > I have: (not in compilation order) > ?e_core-0.9.9.063 > ?e_dbus-0.5.0.063 > ?edje-0.9.93.063 > ?efreet-0.5.0.063 > ?eina0.9.9.063 > ?elementary-0.6.0.63 > ?embryo-0.9.9.063 > ?enlightenment-0.16.999.063 > ?evas-0.9.9.063 > > I have a clean Debian 5.04 installation and I have been using DR16 for many > years now. > > Everything goes well until I get to edje. I get this from edje's configure > script: > ############################################################################ > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for library containing strerror... none required > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for fgrep... /bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 98304 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking for /usr/bin/ld option to reload object files... -r > checking how to recognize dependent libraries... pass_all > checking for ar... ar > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking how to run the C preprocessor... gcc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking whether to build edje_cc... yes > checking for location of Vim data files... /usr/share/vim > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking whether to build documentation... yes > checking for doxygen... no > WARNING: > The doxygen program was not found in your execute path. > You may have doxygen installed somewhere not covered by your path. > > If this is the case make sure you have the packages installed, AND > that the doxygen program is in your execute path (see your > shell manual page on setting the $PATH environment variable), OR > alternatively, specify the program to use with --with-doxygen. > checking for a Python interpreter with version >= 2.5... python > checking for python... /usr/bin/python > checking for python version... 2.5 > checking for python platform... linux2 > checking for python script directory... ${prefix}/lib/python2.5/site-packages > checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for LUA... no > checking for LUA... yes > checking for EDJE... configure: error: Package requirements ( > ?eina-0 > ?eet >= 1.0.1 > ?evas >= 0.9.9 > ?ecore >= 0.9.9 > ?ecore-job >= 0.9.9 > ?ecore-file >= 0.9.9 > ?embryo >= 0.9.1 > ?) were not met: > > No package 'eet' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively you may set the environment variable EDJE_CFLAGS > and EDJE_LIBS to avoid the need to call pkg_config. > See the pkg-config man page for more details. > > ############################################################################ > > I also tried the script at the bottom of svn.enlightenment.org to try and > download all the required files for DR17, but it downloads A LOT OF STUFF not > needed, or am I wrong? > > Can you please tell me how to get the latest DR17 snapshots on svn without > downloading all the other stuff, and in which order am I required to build DR17? > > Thank You > > Danny > > ------------------------------------------------------------------------------ > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- Wido ------------------------------------------------------------------------------ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
