har försökt instalera itask i E17 men får det inte att funka
kör från svn
svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
sen
cd ~/itask-module/itask_ng/ng/
sen
./autogen.sh
Running aclocal...
Running autoheader...
Running autoconf...
Running libtoolize...
Running automake...
Generating gettext ng.pot.template
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... 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 dependency style of gcc... gcc3
checking for library containing strerror... none required
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 dependency style of gcc... (cached) gcc3
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 dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... 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
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for edje-config... /opt/e17/bin/edje-config
checking for enlightenment-config... /usr/bin/enlightenment-config
checking for efreet-config... /opt/e17/bin/efreet-config
configure: creating ./config.status
config.status: creating Makefile
config.status: creating data/Makefile
config.status: creating data/themes/Makefile
config.status: creating po/Makefile
config.status: creating src/Makefile
config.status: creating module.desktop
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing po-directories commands
config.status: executing default commands
john@ubuntu:~/itask-module/ng$ make
cd . && /bin/bash /home/john/itask-module/ng/missing --run autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/bash ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make all-recursive
make[1]: Entering directory `/home/john/itask-module/ng'
Making all in src
make[2]: Entering directory `/home/john/itask-module/ng/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/john/itask-module/ng/src'
Making all in data
make[2]: Entering directory `/home/john/itask-module/ng/data'
Making all in themes
make[3]: Entering directory `/home/john/itask-module/ng/data/themes'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/john/itask-module/ng/data/themes'
make[3]: Entering directory `/home/john/itask-module/ng/data'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/john/itask-module/ng/data'
make[2]: Leaving directory `/home/john/itask-module/ng/data'
Making all in po
make[2]: Entering directory `/home/john/itask-module/ng/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/john/itask-module/ng/po'
make[2]: Entering directory `/home/john/itask-module/ng'
make[2]: Leaving directory `/home/john/itask-module/ng'
make[1]: Leaving directory `/home/john/itask-module/ng'
john@ubuntu:~/itask-module/ng$ sudo make install
Password:
Making install in src
make[1]: Entering directory `/home/john/itask-module/ng/src'
make[2]: Entering directory `/home/john/itask-module/ng/src'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/home/john/.e/e/modules/ng/linux-gnu-i686" || mkdir -p -- "/home/john/.e/e/modules/ng/linux-gnu-i686"
/bin/bash ../libtool --mode=install /usr/bin/install -c 'module.la' '/home/john/.e/e/modules/ng/linux-gnu-i686/module.la'
/usr/bin/install -c .libs/module.so /home/john/.e/e/modules/ng/linux-gnu-i686/module.so
/usr/bin/install -c .libs/module.lai /home/john/.e/e/modules/ng/linux-gnu-i686/module.la
/usr/bin/install -c .libs/module.a /home/john/.e/e/modules/ng/linux-gnu-i686/module.a
chmod 644 /home/john/.e/e/modules/ng/linux-gnu-i686/module.a
ranlib /home/john/.e/e/modules/ng/linux-gnu-i686/module.a
PATH="$PATH:/sbin" ldconfig -n /home/john/.e/e/modules/ng/linux-gnu-i686
----------------------------------------------------------------------
Libraries have been installed in:
/home/john/.e/e/modules/ng/linux-gnu-i686
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[2]: Leaving directory `/home/john/itask-module/ng/src'
make[1]: Leaving directory `/home/john/itask-module/ng/src'
Making install in data
make[1]: Entering directory `/home/john/itask-module/ng/data'
Making install in themes
make[2]: Entering directory `/home/john/itask-module/ng/data/themes'
make[3]: Entering directory `/home/john/itask-module/ng/data/themes'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/home/john/.e/e/modules/ng" || mkdir -p -- "/home/john/.e/e/modules/ng"
/usr/bin/install -c -m 644 'fonts/VeraBd.ttf' '/home/john/.e/e/modules/ng/VeraBd.ttf'
/usr/bin/install -c -m 644 'ng.edc' '/home/john/.e/e/modules/ng/ng.edc'
/usr/bin/install -c -m 644 'ng.edj' '/home/john/.e/e/modules/ng/ng.edj'
make[3]: Leaving directory `/home/john/itask-module/ng/data/themes'
make[2]: Leaving directory `/home/john/itask-module/ng/data/themes'
make[2]: Entering directory `/home/john/itask-module/ng/data'
make[3]: Entering directory `/home/john/itask-module/ng/data'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/home/john/itask-module/ng/data'
make[2]: Leaving directory `/home/john/itask-module/ng/data'
make[1]: Leaving directory `/home/john/itask-module/ng/data'
Making install in po
make[1]: Entering directory `/home/john/itask-module/ng/po'
make[2]: Entering directory `/home/john/itask-module/ng/po'
make[2]: Nothing to be done for `install-exec-am'.
for L in it sv; do \
/home/john/itask-module/ng/install-sh -d /home/john/.e/e/locale/$L/LC_MESSAGES; \
/usr/bin/install -c -m 644 \
$L.mo /home/john/.e/e/locale/$L/LC_MESSAGES/ng.mo; \
done
make[2]: Leaving directory `/home/john/itask-module/ng/po'
make[1]: Leaving directory `/home/john/itask-module/ng/po'
make[1]: Entering directory `/home/john/itask-module/ng'
make[2]: Entering directory `/home/john/itask-module/ng'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/home/john/.e/e/modules/ng" || mkdir -p -- "/home/john/.e/e/modules/ng"
/usr/bin/install -c -m 644 'module_icon.png' '/home/john/.e/e/modules/ng/module_icon.png'
/usr/bin/install -c -m 644 'module.desktop' '/home/john/.e/e/modules/ng/module.desktop'
/usr/bin/install -c -m 644 'e-module-ng.edj' '/home/john/.e/e/modules/ng/e-module-ng.edj'
make[2]: Leaving directory `/home/john/itask-module/ng'
make[1]: Leaving directory `/home/john/itask-module/ng'
itask lägger sig o module listan men går inte att "enabla" det
nån som kan se om d blir nån errors lr om jag fattas några filer lr nått för det vill verklgen inte funka
o jag e inte så där hajj på att se sånt när man complimerar själv.
e17 itask?
Kategoriregler
Varning! Det som diskuteras här är inte alltid enkelt och det kan hända att vissa installationer/modifieringar kan göra ditt system oanvändbart. Inget för nybörjare. Gör alltid backup av känslig data innan du experimenterar.
Varning! Det som diskuteras här är inte alltid enkelt och det kan hända att vissa installationer/modifieringar kan göra ditt system oanvändbart. Inget för nybörjare. Gör alltid backup av känslig data innan du experimenterar.
- invaderjohn
- Inlägg: 560
- Blev medlem: 07 aug 2006, 01:27
- Ort: kristianstad
- Kontakt:
SV: e17 itask?
Ser utt att ha kompilerat som den ska. Modulerna i E17 funkar lite som dom vill. Det kan vara så att itask inte funkar just nu
- invaderjohn
- Inlägg: 560
- Blev medlem: 07 aug 2006, 01:27
- Ort: kristianstad
- Kontakt:
SV: e17 itask?
mjo d e ju sant som du säger. men d står inge nånstans om det. aja får väl fortsätta min letan o se om man kan komma underfull me nått. 

SV: e17 itask?
lite installations guider:
http://e17blog.tuxfamily.org/e17blog-fe ... eisty-Fawn
och
http://ubuntuos.wordpress.com/2007/03/1 ... t-desktop/
First, install subversion.
Then:
svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
And:
cd ~/itask-module/itask_ng/itask_ng
./autogen.sh
make
sudo make install
Screenshot:
http://perso.orange.fr/pinguSODalon/screens/itask.png
See also:
http://marc.info/?l=enlightenment-devel ... 908189&w=2
annan guide:
1) sudo apt-get install subversion
2) sudo apt-get install e17-devel
3) cd ~
4) svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
5) cd ~/itask-module/itask_ng/itask_ng
6) ./autogen.sh
7) make
make install
Edit: e17 itask kanske var nåt annat, trodde först du hade problem med installationen av E17. Sorry
http://e17blog.tuxfamily.org/e17blog-fe ... eisty-Fawn
och
http://ubuntuos.wordpress.com/2007/03/1 ... t-desktop/
First, install subversion.
Then:
svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
And:
cd ~/itask-module/itask_ng/itask_ng
./autogen.sh
make
sudo make install
Screenshot:
http://perso.orange.fr/pinguSODalon/screens/itask.png
See also:
http://marc.info/?l=enlightenment-devel ... 908189&w=2
annan guide:
1) sudo apt-get install subversion
2) sudo apt-get install e17-devel
3) cd ~
4) svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
5) cd ~/itask-module/itask_ng/itask_ng
6) ./autogen.sh
7) make
make install
Edit: e17 itask kanske var nåt annat, trodde först du hade problem med installationen av E17. Sorry

Senast redigerad av 1 TForsman, redigerad totalt 3 gånger.
- invaderjohn
- Inlägg: 560
- Blev medlem: 07 aug 2006, 01:27
- Ort: kristianstad
- Kontakt:
SV: e17 itask?
hehe tack iaf. men har kört igenom båda dom guidernaZinden skrev: lite installations guider:
http://e17blog.tuxfamily.org/e17blog-fe ... eisty-Fawn
och
http://ubuntuos.wordpress.com/2007/03/1 ... t-desktop/
First, install subversion.
Then:
svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
And:
cd ~/itask-module/itask_ng/itask_ng
./autogen.sh
make
sudo make install
Screenshot:
http://perso.orange.fr/pinguSODalon/screens/itask.png
See also:
http://marc.info/?l=enlightenment-devel ... 908189&w=2
annan guide:
1) sudo apt-get install subversion
2) sudo apt-get install e17-devel
3) cd ~
4) svn co http://itask-module.googlecode.com/svn/trunk/ itask-module/itask_ng
5) cd ~/itask-module/itask_ng/itask_ng
6) ./autogen.sh
7) make
make install
Edit: e17 itask kanske var nåt annat, trodde först du hade problem med installationen av E17. Sorry![]()

SV: e17 itask?
länkarna var också guider, tror dem var helt annorlunda....