date:20080123

[e-users] easy_17.sh successful on Fedora 8, fails on RHWS 4

2008-01-23 Thread Geoffrey

Thanks to all for the assistance with easy_17.sh.  I was able to 
successfully build e using it on my fedora 8 box.  I'm now trying to run 
it on my Red Hat Workstation 4 box and when compiling imlib2, I receive 
the following error:

./configure: line 22512: syntax error near unexpected token `libpng12,'
./configure: line 22512: `  PKG_CHECK_EXISTS(libpng12,'

Looking at the configure code I see the following:

if test $png_loader != no ; then
   PKG_CHECK_EXISTS(libpng12,
  PKG_CHECK_MODULES(PNG, libpng12, [ png_ok=yes ], [ png_ok=no]),

   PKG_CHECK_EXISTS(libpng10,
 [ PKG_CHECK_MODULES(PNG, libpng10, [ png_ok=yes ], [ 
png_ok=no]) ],
 [ PKG_CHECK_MODULES(PNG, libpng, [ png_ok=yes ], [ 
png_ok=no]) ]
   )

   )
fi

Pretty complex scripting there, but at first glance, I don't see the 
syntactical error.

I can't find where PKG_CHECK_EXISTS is defined though.

Any suggestions would be appreciated.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Problem with temperature module

2008-01-23 Thread Andreas Volz

Am Wed, 23 Jan 2008 12:45:46 +1100 schrieb Carsten Haitzler (The
Rasterman):

 On Tue, 22 Jan 2008 22:55:58 +0100 giggz [EMAIL PROTECTED]
 babbled:
 
 is tempget running? you can actually run it by hand 
 
 ${PREFIX}/enlightenment/modules/temperature/${ARCH}/tempget 0 -null-
 128
 
 first arg is sensor type:
 
 0   SENSOR_TYPE_NONE,
 1   SENSOR_TYPE_FREEBSD,
 2   SENSOR_TYPE_OMNIBOOK,
 3   SENSOR_TYPE_LINUX_MACMINI,
 4   SENSOR_TYPE_LINUX_I2C,
 5   SENSOR_TYPE_LINUX_ACPI,
 6   SENSOR_TYPE_LINUX_PBOOK,
 7   SENSOR_TYPE_LINUX_INTELCORETEMP
 
 2nd arg is sensor name (-null- is when no sensor name is
 set). /sys/bus/i2c/devices/ is scanned for sensor names here. the
 name is a path to the file
 in /sys/bus/i2c/devices/${DEV}/temp${}_input file - if it exists
 (i.e. a i2c temperature sensor).
 
 3rd arg is tick time between polls (8 ticks per second by default-
 can be changed, but isn't right now).
 
 it will output results to stdout.
 
 the default is 0 -null- for the first 2 args - the same as it has
 always been, in whihc case known sensors are scanned for in order of
 acpi thermal zone, monibook, other temp devices
 (devices/temperatures/*_temperature), platform temp input and finally
 i2c. see the code. if on bsd this is different.

Not sure if I executed it correct:

 /opt/e17/lib/enlightenment/modules/temperature/linux-gnu-i686/tempget
0 -null- 8

ERROR

or

/opt/e17/lib/enlightenment/modules/temperature/linux-gnu-i686/tempget 0
null 8 

ERROR


Does this help?

regards
Andreas

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

[e-users] Problem with compiling E with easy_e17.sh

2008-01-23 Thread Brian Howe

Here is the last bits of the output from the e compile any suggestions?
This is Ubuntu 7.10 on intel dell laptop.

Thanks

test -z bg.gmo de.gmo eo.gmo es.gmo fi.gmo fr.gmo ja.gmo ru.gmo zh_CN.gmo
hu.gmo sl.gmo it.gmo zh_TW.gmo ko.gmo pt_BR.gmo ca.gmo fr_CH.gmo || make
bg.gmo de.gmo eo.gmo es.gmo fi.gmo fr.gmo ja.gmo ru.gmo zh_CN.gmo hu.gmo
sl.gmo it.gmo zh_TW.gmo ko.gmo pt_BR.gmo ca.gmo fr_CH.gmo
make[3]: Entering directory `/home/bhowe/e17_cvs/e17/apps/e/po'
make[3]: `bg.gmo' is up to date.
make[3]: `de.gmo' is up to date.
make[3]: `eo.gmo' is up to date.
make[3]: `es.gmo' is up to date.
make[3]: `fr.gmo' is up to date.
make[3]: `ja.gmo' is up to date.
rm -f fi.gmo  /usr/bin/msgfmt -c --statistics -o fi.gmo fi.po
rm -f ru.gmo  /usr/bin/msgfmt -c --statistics -o ru.gmo ru.po
/usr/bin/msgfmt: (null): warning: PO file header fuzzy
 warning: older versions of msgfmt will give an
error on this
fi.po:3760: number of format specifications in 'msgid' and 'msgstr' does not
match
fi.po:3782: number of format specifications in 'msgid' and 'msgstr' does not
match
/usr/bin/msgfmt: found 2 fatal errors
1164 translated messages, 68 fuzzy translations, 31 untranslated messages.
make[3]: *** [fi.gmo] Error 1
make[3]: *** Waiting for unfinished jobs
1120 translated messages, 105 fuzzy translations, 38 untranslated messages.
make[3]: Leaving directory `/home/bhowe/e17_cvs/e17/apps/e/po'
make[2]: *** [stamp-po] Error 2
make[2]: Leaving directory `/home/bhowe/e17_cvs/e17/apps/e/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bhowe/e17_cvs/e17/apps/e'
make: *** [all] Error 2
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] e16: NeverUseArea

2008-01-23 Thread Dennis Nezic

 On Mon, 21 Jan 2008 19:19:28 +0100,
 Kim Woelders [EMAIL PROTECTED] wrote:

 Dennis Nezic wrote:
  Maybe I'm not understanding how the NeverUseArea window toggle flag
  works, but shouldn't it force e16 to /never/ place windows in the
  specified area? If so, it doesn't seem to be working at the moment
  (v0.16.8.11).
  
 never is a bit strong. It's more like normally. Windows may get 
 placed over NeverUseArea windows e.g. if you place manually, if a new 
 window cannot be placed at all otherwise, or if you do an 
 absolute/xinerama window maximization.
 It looks to me like things work properly in 0.16.8.11.
 
 I did add an option to make the default maximization policy
 configurable (Move  Resize Settings...). Could that explain
 something? If not please specify in more detail how you see the
 NeverUseArea behavior has changed.

Just playing with a bunch of xterms, in an otherwise empty virtual
desktop -- if I set the first one to NeverUseArea, then subsequently
open a bunch of normal others, although I do see an avoidance of the
area in the beginning, it covers the NeverUseArea sooner (even sooner
if it's placed along the right edge of the screen) than I think it
should -- in fact, it should never use that xterm's area :) (There is
plenty of room for adjacent windows, and they can be overlapped.

There is very little difference between the behaviour with and without
the flag set. I think it should be strongly enforced :).

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Problem with temperature module

2008-01-23 Thread The Rasterman

On Tue, 22 Jan 2008 22:55:58 +0100 giggz [EMAIL PROTECTED] babbled:

is tempget running? you can actually run it by hand 

${PREFIX}/enlightenment/modules/temperature/${ARCH}/tempget 0 -null- 128

first arg is sensor type:

0   SENSOR_TYPE_NONE,
1   SENSOR_TYPE_FREEBSD,
2   SENSOR_TYPE_OMNIBOOK,
3   SENSOR_TYPE_LINUX_MACMINI,
4   SENSOR_TYPE_LINUX_I2C,
5   SENSOR_TYPE_LINUX_ACPI,
6   SENSOR_TYPE_LINUX_PBOOK,
7   SENSOR_TYPE_LINUX_INTELCORETEMP

2nd arg is sensor name (-null- is when no sensor name is
set). /sys/bus/i2c/devices/ is scanned for sensor names here. the name is a
path to the file in /sys/bus/i2c/devices/${DEV}/temp${}_input file - if it
exists (i.e. a i2c temperature sensor).

3rd arg is tick time between polls (8 ticks per second by default- can be
changed, but isn't right now).

it will output results to stdout.

the default is 0 -null- for the first 2 args - the same as it has always been,
in whihc case known sensors are scanned for in order of acpi thermal zone,
monibook, other temp devices (devices/temperatures/*_temperature), platform
temp input and finally i2c. see the code. if on bsd this is different.

 Andreas Volz a écrit :
  Am Mon, 21 Jan 2008 11:36:42 +1100 schrieb Carsten Haitzler (The
  Rasterman):
  
  On Sat, 19 Jan 2008 09:07:44 +0100 Andreas Volz [EMAIL PROTECTED]
  babbled:
 
  Hello,
 
 
 Hi,
 
  since some time the temperature module isn't longer working on my
  system. I don't remember what I've changed. It simply shows N/A.
  In .xsession-errors is an entry:
 
  Sending TERM signal
  to /opt/e17/lib/enlightenment/modules/temperature/linux-gnu-i686/tempget
  0 (null) 128 (8067).
 
 
  Any ideas where I should start to search for the problem? Did I
  perhaps miss to start a system service?
  a week ago i committed changes to put the temperature polling/reading
  into a separate process - but this just moved the code there and
  should do exactly what it did before - it just has slaved out the
  work to a sub-proc to avoid blocking-reads of temp sensor data that
  seemed to make e jerky whenever the temperature was polled (e would
  pause for like 200ms or so whole waiting on the kernel to respond to
  the read). if it changed in the last week then i may have made a
  mistake - otherwise its likely something else. changed kernels?
  modules not loaded?
  
  Maybe I changed a kernel version, but not a relevant jump. See the
  output of sensors executed by the same user who started e17.
  
  sensors 
  w83697hf-isa-0290
  Adapter: ISA adapter
  VCore: +1.52 V  (min =  +0.08 V, max =  +2.11 V)  
  +3.3V: +3.34 V  (min =  +2.05 V, max =  +2.05 V)   ALARM  
  +5V:   +4.95 V  (min =  +0.00 V, max =  +0.00 V)   ALARM  
  +12V: +11.55 V  (min =  +3.89 V, max =  +3.89 V)   ALARM  
  -12V:  +0.72 V  (min =  -4.38 V, max = -14.75 V)   ALARM  
  -5V:   +1.84 V  (min =  -0.48 V, max =  -7.11 V)   ALARM  
  V5SB:  +5.48 V  (min =  +0.00 V, max =  +0.97 V)   ALARM  
  VBat:  +0.27 V  (min =  +0.10 V, max =  +0.64 V)  
  fan1: 2149 RPM  (min =   -1 RPM, div = 4)  ALARM  
  fan2:0 RPM  (min = 5273 RPM, div = 4)  ALARM  
  temp1:   +42°C  (high =   +72°C, hyst =+8°C)   sensor =
  diode temp2: +42.5°C  (high =  +120°C, hyst =  +120°C)   sensor =
  diode alarms:   
  beep_enable:
Sound alarm enabled
  
  So the kernel interface seems to work. Perhaps a problem with the API.
  I know Gentoo is often bad with unresolved symbols. Perhaps I missed to
  recompile a library.
 
 I have e17 through the debian packages of edevelop and the temperature
 module doesn't work anymore on my computer too. I don't have change my
 kernel. And acpi -V gives me always the results...
 
  
  regards
 
 Cheers
 GiGGz
 
  Andreas
  
  -
  This SF.net email is sponsored by: Microsoft
  Defy all challenges. Microsoft(R) Visual Studio 2008.
  http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 
 
 -
 This SF.net email is sponsored by: Microsoft
 Defy all challenges. Microsoft(R) Visual Studio 2008.
 http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
 ___
 enlightenment-users mailing list
 enlightenment-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/enlightenment-users
 


-- 
- Codito, ergo sum - I code, therefore I am --
The Rasterman (Carsten Haitzler)[EMAIL PROTECTED]


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net

Re: [e-users] Problem with compiling E with easy_e17.sh

2008-01-23 Thread Massimo Maiurana

Brian Howe, il 23/01/2008 20:44, scrisse:

 fi.po:3760: number of format specifications in 'msgid' and 'msgstr' does not
 match
 fi.po:3782: number of format specifications in 'msgid' and 'msgstr' does not
 match

uhmm, here I don't get any error running msgfmt on fi.po, nor I see
format strings on lines 3760 and 3782 of fi.po.

can you please update from cvs and try again (a new fi.po has just
been committed), and in case you're still getting errors, can you
please show relevant lines from fi.po?

-- 
   Massimo Maiurana massimoatragusa.linux.it
   http://massimo.solira.org   GPG keyID #7044D601

Articolo 11 - L'Italia ripudia la guerra come strumento di offesa
alla libertà degli altri popoli e come mezzo di risoluzione delle
controversie internazionali


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] Problem with temperature module

2008-01-23 Thread The Rasterman

On Wed, 23 Jan 2008 18:54:54 +0100 Andreas Volz [EMAIL PROTECTED] babbled:

 Am Wed, 23 Jan 2008 12:45:46 +1100 schrieb Carsten Haitzler (The
 Rasterman):
 
  On Tue, 22 Jan 2008 22:55:58 +0100 giggz [EMAIL PROTECTED]
  babbled:
  
  is tempget running? you can actually run it by hand 
  
  ${PREFIX}/enlightenment/modules/temperature/${ARCH}/tempget 0 -null-
  128
  
  first arg is sensor type:
  
  0   SENSOR_TYPE_NONE,
  1   SENSOR_TYPE_FREEBSD,
  2   SENSOR_TYPE_OMNIBOOK,
  3   SENSOR_TYPE_LINUX_MACMINI,
  4   SENSOR_TYPE_LINUX_I2C,
  5   SENSOR_TYPE_LINUX_ACPI,
  6   SENSOR_TYPE_LINUX_PBOOK,
  7   SENSOR_TYPE_LINUX_INTELCORETEMP
  
  2nd arg is sensor name (-null- is when no sensor name is
  set). /sys/bus/i2c/devices/ is scanned for sensor names here. the
  name is a path to the file
  in /sys/bus/i2c/devices/${DEV}/temp${}_input file - if it exists
  (i.e. a i2c temperature sensor).
  
  3rd arg is tick time between polls (8 ticks per second by default-
  can be changed, but isn't right now).
  
  it will output results to stdout.
  
  the default is 0 -null- for the first 2 args - the same as it has
  always been, in whihc case known sensors are scanned for in order of
  acpi thermal zone, monibook, other temp devices
  (devices/temperatures/*_temperature), platform temp input and finally
  i2c. see the code. if on bsd this is different.
 
 Not sure if I executed it correct:
 
  /opt/e17/lib/enlightenment/modules/temperature/linux-gnu-i686/tempget
 0 -null- 8
 
 ERROR
 
 or
 
 /opt/e17/lib/enlightenment/modules/temperature/linux-gnu-i686/tempget 0
 null 8 
 
 ERROR
 
 
 Does this help?

well it says that tmepget has an error reading anything - beyond that you will
need to trace its code and see why - put in printfs or gdb step through it.


-- 
- Codito, ergo sum - I code, therefore I am --
The Rasterman (Carsten Haitzler)[EMAIL PROTECTED]


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

[e-users] easy_17.sh successful on Fedora 8, fails on RHWS 4

Re: [e-users] Problem with temperature module

[e-users] Problem with compiling E with easy_e17.sh

Re: [e-users] e16: NeverUseArea

Re: [e-users] Problem with temperature module

Re: [e-users] Problem with compiling E with easy_e17.sh

Re: [e-users] Problem with temperature module

7 matches

Site Navigation

Mail list logo

Footer information