Re: [Wengophone-devel] Wengophone no longer in Debian testing

2007-02-15 Thread Didier Link 
Le Wed, 14 Feb 2007 23:20:37 +0100,
Andreas Schneider <[EMAIL PROTECTED]> a écrit :

> Andreas Schneider wrote:
> > Philippe BERNERY wrote:
> >> Zanfib put a comment today on Trac: it seems the problem has been
> >> fixed since the update of osip/eXosip. Anyone can confirm?
> >>
> > 
> > Hi Philippe,
> > 
> > no I can't at the moment. It doesn't work for me here with latest
> > 2.1 svn, but it could be the company's firewall. I have to try it
> > at home tonight.
> 
> I'm not able to connect to my wengo sip account with the latest
> wengophone 2.1 version. I've tried the precompiled i586 binary from
> the web page and it doesn't work too.
> 
> Something is completely wrong.
> 
>   -- andreas
> 

Hi wengonautes,

I think your configuration isn't correctly setup because with svn
version 9734 I've this lines :

(debug) 08:58:03 void
SipAccount::setConnected(bool): XD_SIP_ _isConnected = 0 -> connected =
1
(debug) 08:58:03 void
UserProfile::loginStateChangedEventHandler(SipAccount&,
EnumSipLoginState::SipLoginState): XD_SIP_ [EMAIL PROTECTED]
(debug) 08:58:03 virtual void
PhoneLine::setState(EnumPhoneLineState::PhoneLineState): line state
changed lineId=1 state=PhoneLineStateOk (debug) 08:58:03 void
UserProfile::loginStateChangedEventHandlerThreadSafe(SipAccount&,
EnumSipLoginState::SipLoginState): XD_SIP_ [EMAIL PROTECTED]
(debug) 08:58:03 void
UserProfile::loginStateChangedEventHandlerThreadSafe(SipAccount&,
EnumSipLoginState::SipLoginState): XD_SIP_ CONNECTED (debug) 08:58:03
void PresenceHandler::connectedEventHandler(ConnectHandler&,
std::string): an account is connected, login=didierlink protocol=8

This lines show the connected state with a 64bits client on Gentoo Linux
amd64 ;)

Andreas maybe your firewall setup isn't "complete" at home too ??

Cheers

Didier

ps: my pseudo on trac is Zanfib ;)


-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]
SIP : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: PGP signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Linux Audio presentation au Linux.conf.au

2007-01-31 Thread Didier LINK 
Le jeudi 25 janvier 2007 à 10:16 +0100, Dave Neary a écrit :
> Hi all,

Hi all,

> 
> Lennart Poettering of PulseAudio (formerly polypaudio) gave a
> presentation on the state of audio on Linux, including an overview of
> PulseAudio - definitely worth a listen (Matthieu and Didier, required
> reading for you, I think ;) - the archive is online:
> http://mirror.linux.org.au/pub/linux.conf.au/2007/video/talks/211.ogg

Thanks for the links, very interesting talk on Linux sound.

Since Alsa is only available on Linux maybe the use of pulseaudio can
solve the sound problem on Linux and abstract in the meantime the win32
sound system. If one day pulseaudio support MacOSX, it will completely
replace portaudio ;)

The API looks good, It have 2 APIs, one "simple" with blocking
operations, and one "asynchronous" but more complex to implement.

The simple API seems to looks good for a test, maybe I can develop a new
driver for phapi, if you have time of course because I'm not at full
time on it ;)

Anyway, just tell me if I can start to play with pulseaudio and
wengophone :)

Cheers.

Didier Link

ps: thanks Aurélien and Dave for the photos of the summit, very nice, a
great time for me to remember !



___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-30 Thread Didier LINK 
Hello,

> > 
> > Minh and Julien have integrated your patches in REV 9451.
> 
> Thanks for this,
> 

After investigation on my software configuration and some headaches I've
found that the code is not completely correct. The CAPTURE part is
parsed correctly but not PLAYBACK part, that's why I don't hear any
sound.

I've attached my correction for the code.

With the default parameters (PH_FORCE_AUDIO_DEVICE="alsa:in=hw:0,0
out=hw:0,0") the test session (333) is ok but with an annoying echo.

This echo seems to be the same as with the OSS driver.

So, after all it's a good news to have some echo :)

Another good news is that I can confirm the absence of segfault in the
resample part with the Alsa native driver activated :)

Now I can go to more tests :)

Thanks for your attention.

Didier Link

Index: wengophone-2.1/wifo/phapi/phmedia-alsa.c
===
--- wengophone-2.1/wifo/phapi/phmedia-alsa.c	(révision 9509)
+++ wengophone-2.1/wifo/phapi/phmedia-alsa.c	(copie de travail)
@@ -113,11 +124,13 @@
   {
 *nmend = 0;
   }
+
+  name += 3;
 }
   }
   else if ((s = strstr(name, "out=")) != NULL)
   {
-nmend = strchr(name+4, ' ');
+nmend = strchr(s+4, ' ');
 if (nmend)
 {
   *nmend = 0;
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-26 Thread Didier LINK 
Le jeudi 25 janvier 2007 à 23:50 +0100, Jerome WAGNER a écrit :
> Hello,

Hello,

> 
> Minh and Julien have integrated your patches in REV 9451.

Thanks for this,

> 
> I patched something in 9452 that might correct the rctx == NULL problem.
> (old refactoring that was not ported to the pure alsa backend)

Very good, this particular issue is solved but the alsa portaudio always
segfault like in ticket #1271.

> 
> I hope this can help (and I hope it will compile under Linux as I don't have
> one under my hands right now)

It compile and run, that's the first time that I can launch, test the
333, quit the application without a segfault ! Very interesting !

But I've no sound during the test. For the moment I search for a mixer
problem on my computer and without success I will investigate in the
Alsa code of wengophone.

> 
> Jerome
> Ps: rev 9452 compiles under windows. If I break anything under linux, I am
> very sorry.

It's ok !!

Cheers.

Didier


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-24 Thread Didier LINK 

> (DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi
> /phmedia-alsa.c:316) alsa_stream_open: (name: alsa: in=0 out=0, rate: 16000,
> framesize: 640)
> 
> (confirming that the alsa driver is given an alsa name)
> 
> After that you should look on line (122) of phmedia-alsa:
>   rc = snd_pcm_open(&handle, name, type, 0);
> 
> It seems to me that using "name" is a bug here
> And this would be why it tells you
> "unable to open < in=0 out=0> pcm device"

Thats true, with a little bit of debugging I've found some improvements
to the code (file is attached). Now it parse correctly the in= and out=
options. The syntaxes that work for me are :

*  PH_FORCE_AUDIO_DEVICE="alsa:in=hw:0 out=hw:0"
*  PH_FORCE_AUDIO_DEVICE="alsa:in=default out=default"

This accept only some specific value. See [1] for some examples, close
to the end of the page (PCM naming conventions).

The device initialization works like a charm. The phlogger debug
informations file is attached.

But, yes sorry ..., the session ending abruptly by a segfault. I've
paste the backtrace in the ticket #1271 [2].

For the moment Alsa is broken by a problem in ph_downsample or
ph_upsample problem. The same "rctx" param is null and lead to a
segfault.

I hope my try help you and I'm open to all suggestions and test
cases/patches etc etc.

Best regards.

Didier Link


[1] http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html

[2] http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1271

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39) registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39) registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39) registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39) registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58) ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:314) alsa_stream_open: (name: alsa:in=hw:0 out=hw:0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94) alsa_dev_open: (name: alsa:in=hw:0 out=hw:0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:206) PCM handle name = 'hw:0'
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:207) PCM state = PREPARED
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:209) access type = RW_INTERLEAVED
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:211) format = 'S16_LE' (Signed 16 bit Little Endian)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:213) subformat = 'STD' (Standard)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:217) channels = 1
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:219) rate = 16000 bps
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:221) period time = 2 us
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:223) period size = 320 frames
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:225) buffer time = 204 us
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:227) buffer size = 32640 frames
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:229) periods per buffer = 102 frames
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:231) exact rate = 16000/1 bps
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:233) significant bits = 16
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:235) tick time = 1000 us
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:237) is batch = 0
(DBG_DYN

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-24 Thread Didier LINK 
Le mercredi 24 janvier 2007 à 02:08 +0100, Jerome WAGNER a écrit :
> Hello,

Hello all,

> 
> Yes I think you are right ; forcing the audio device in your case leads to a
> bug.
> 
> select_audio_device is supposed override the deviceId when it is forced, but
> I guess that the "const char *" stops this from working.

The "const" is not the main problem here, the pointer is not the same
after the function call and we need to copy the good string with strcpy.

> 
> Maybe you can try and patch it this way (making sure that when we get out of
> select_audio_device, the deviceId has been changed)

See attached a little patch to solve this case. It works for me, can you
review it and commit to the svn if it looks good ?

I can begin to go further with the alsa support now ;)

Thanks.

Didier Link


Index: wengophone-2.1/wifo/phapi/phmedia.c
===
--- wengophone-2.1/wifo/phapi/phmedia.c (révision 9392)
+++ wengophone-2.1/wifo/phapi/phmedia.c (copie de travail)
@@ -59,18 +59,23 @@
 int ph_msession_start(struct ph_msession_s *s, const char *deviceid)
 {
   int ret1,ret2 = -1;
+  char *devName;
 
+  devName = strdup(deviceid);
+
   DBG_MEDIA_ENGINE("MEDIA_ENGINE: entering ph_msession_start\n");
 
   g_mutex_lock(s->critsec_mstream_init);
 
-  ret1 = ph_msession_audio_start(s, deviceid);
+  ret1 = ph_msession_audio_start(s, devName);
 #ifdef PHAPI_VIDEO_SUPPORT
   ret2 = ph_msession_video_start(s, deviceid);
 #endif
 
   g_mutex_unlock(s->critsec_mstream_init);
 
+  free(devName);
+
   if (!ret1 && !ret2)
   {
 return 0;
Index: wengophone-2.1/wifo/phapi/phmedia-audio.c
===
--- wengophone-2.1/wifo/phapi/phmedia-audio.c   (révision 9392)
+++ wengophone-2.1/wifo/phapi/phmedia-audio.c   (copie de travail)
@@ -2081,7 +2081,17 @@
 
   if (forcedDeviceId)
   {
-deviceId = forcedDeviceId;
+   // Ensure that the destination buffer has the good size sor strcpy
+   if (strlen(forcedDeviceId) > strlen(deviceId))
+   {
+   if ((realloc(deviceId, 
+   strlen(forcedDeviceId) * sizeof(char))) == NULL)
+   {
+   DBG_DYNA_AUDIO_DRV("error in realloc() ; phmedia-audio.c:2085\n");
+   }
+   }
+
+ strcpy(deviceId, forcedDeviceId);
   }
 
   if (!deviceId || !deviceId[0])


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Didier LINK 
Le mardi 23 janvier 2007 à 20:03 +0100, Jerome WAGNER a écrit :
> Hello Didier,
> 
> >(debug) 18:07:01 static std::list >std::allocator > AudioDeviceManager::getOutputDeviceList():
> >output device found=(default) /dev/dsp OSS
> 
> Means that the GUI is binded on OSS.

Ok, I see, it's disturbing to initialize all the devices type at once.

> 
> Do you have DBG_DYNA_AUDIO_DRV logs when you start a call ? They should
> mention the usage of the ALSA backend because of the FORCE_xxx thing.

The tests with portaudio works with a call, not a very good sound at all
but it work. With the Alsa backend I've no sound and the log is:

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:310)
 alsa_stream_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94)
 alsa_dev_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:132)
 unable to open  pcm device: Aucun fichier ou répertoire de ce 
type
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:310)
 alsa_stream_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94)
 alsa_dev_open: (name: pa:IN=0 OUT=0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:132)
 unable to open  pcm device: Aucun fichier ou répertoire de ce 
type

It's a problem in the name of the device, I've used "alsa: in=0 out=0"
in the variable PH_FORCE_AUDIO_DEVICE but the result is a mix between
initialization of Alsa with portaudio parameters.

In a gdb session I see that the deviceId is picked from a phcfg
structure:

ph_msession_start(s, phcfg.audio_dev) in wifo/phapi/phapi-old.c:3395

I think in this context of forcing the device driver it's a bug :)

I've tried the attached patch but it's just a step further, the
phlogger.log contain :

(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:316)
 alsa_stream_open: (name: alsa: in=0 out=0, rate: 16000, framesize: 640)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:94)
 alsa_dev_open: (name: alsa: in=0 out=0, rate: 16000, framesize: 320)
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phmedia-alsa.c:132)
 unable to open < in=0 out=0> pcm device: Aucun fichier ou répertoire de ce type

I think the change will be made in the function
select_audio_device(const char *deviceId) in phmedia-audio.c:2070

If this function return the deviceId after test the env vars, I think
the use of this vars can be more transparent for all drivers.

What do you think about this enhancement ?

Sorry for the long message and thanks for your attention.

Best regards.

Didier Link

Index: wifo/phapi/phmedia-alsa.c
===
--- wifo/phapi/phmedia-alsa.c(révision 9392)
+++ wifo/phapi/phmedia-alsa.c(copie de travail)
@@ -306,7 +306,13 @@
 int alsa_stream_open(phastream_t *as, char *name, int rate, int framesize, ph_audio_cbk cbk)
 {
   struct alsa_dev *ad = 0;
+  char *forceDeviceId;
 
+  forceDeviceId = getenv("PH_FORCE_AUDIO_DEVICE");
+
+  if(forceDeviceId)
+ name = forceDeviceId;
+
   DBG_DYNA_AUDIO_DRV("alsa_stream_open: (name: %s, rate: %d, framesize: %d)\n", name, rate, framesize);
   ad = calloc(sizeof(*ad), 1);
   if (!ad)


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Didier LINK 
Le mardi 23 janvier 2007 à 14:18 +0100, Jerome WAGNER a écrit :
> Hello Didier,

Hi Jerome and all wengonautes,

> 
> What result did you have for direct ALSA support ?

Thanks for the wiki page I've tried to use the env variable and the
debug define but without success.

The debug log say that Alsa is loaded :

"(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "alsa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "pa" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "null" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:39)
 registering audio driver of kind "file" ...
(DBG_DYNA_AUDIO_DRV:/home/didier/temp/openwengo-ng/wengophone-2.1/wifo/phapi/phaudiodriver.c:58)
 ...registration ok"

But with 
PH_FORCE_AUDIO_DEVICE="alsa: in=0 out=0" wengophone always use the OSS
driver of portaudio :

(debug) 18:07:01 int main(int, char**): WengoPhone started
(debug) 18:07:01 static std::list > AudioDeviceManager::getOutputDeviceList():
output device found=(default) /dev/dsp OSS
(debug) 18:07:01 static std::list > AudioDeviceManager::getInputDeviceList():
input device found=(default) /dev/dsp OSS
(debug) 18:07:01 static std::list > AudioDeviceManager::getOutputDeviceList():
output device found=(default) /dev/dsp OSS

Maybe there is another place to force the use of direct Alsa driver ?

Thanks for your help.

Didier



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] Native Alsa support on Linux

2007-01-23 Thread Didier LINK 
Hi all,

We have discussed during the openwengo summit about the native support
of Alsa by the wengophone. For testing this feature I need some
informations : how to enable direct Alsa using by phapi ? I've found the
PH_FORCE_AUDIO_DEVICE environment variable but no luck in my tests.

For reference, I found this on dmix support [1] related on our
discussion on this subject:

"NOTE: For ALSA 1.0.9rc2 and higher you don't need to setup dmix. Dmix
is enabled as default for soundcards which don't support hw mixing."

Thanks for your help and for the nice summit last week !!

Didier Link

[1] http://alsa.opensrc.org/DmixPlugin




signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] spam on the wiki ?

2007-01-16 Thread Didier LINK 
Hi all,

Sorry for the noise but some changes on the trac wiki made by the user
ku75 today and sunday are more than suspect ... a fragment look like
"pills - Safe Weight Loss with No Side Effects" !

I see a lot of spam in my mailbox, can you help the wiki to be not
polluted by this please ?

Thanks for your attention.

Best regards and see you soon !! ;)

Didier Link



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] config.h problem

2007-01-09 Thread Didier LINK 
Hi all,

I face to a conflict between (BUILD_DIR)/wifo/srtp/config.h[1] and
wengophone-2.1/wifo/srtp/include/config.h[2]

The two files were in theory generated but [1] by cmake (that I use) and
[2] by scons.

During the compilation, after a cmake configuration, gcc use the [2]
that was not configured for a linux plateform but a windows one by
default and lead to a compilation error (see tickets #1181 and #1194)
due to the [1]'s masking.

The revision 9169 committed by jbossart today readd [2] that mask the
good one.

I don't want to use scons because of the future complete switch to cmake
system, so anyone can solve this conflict problem please ?

A temporary workaround is to delete [2].

Thanks for your attention.

Didier Link

-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] compilation error on rev 9139

2007-01-08 Thread Didier LINK 
Le lundi 08 janvier 2007 à 10:08 +0100, Nicolas Lécureuil a écrit :
> Le lundi 8 janvier 2007 09:44, Tanguy Krotoff a écrit :
> > thx for the patch, just commited it, check out rev 9140
> thanks this fix my problem, but after i have a new one:
> 

Hi,

Have you tried the quick fix in this bug report :

http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1194

This configuration error is solved in the trunk but not in the 2.1
branche for the moment (see ticket #1181).

Didier



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] compilation error on rev 9139

2007-01-06 Thread Didier LINK 
Hi and happy new year !!

Le samedi 06 janvier 2007 à 20:13 +0100, Nicolas Lécureuil a écrit :
> On x86_64 , i obtain : 
> 
> + sh build_make.sh 
> release '-DCMAKE_C_FLAGS=-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions' 
> -DFFMPEG_INTERNAL=OFF '-DCMAKE_CXX_FLAGS=-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 
> -fexceptions' -DQT_QMAKE_EXECUTABLE=/usr/lib/qt4/bin/qmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DLIB_SUFFIX=64
> -- Check for working C compiler: /usr/bin/gcc
> -- Check for working C compiler: /usr/bin/gcc -- works
> -- Check size of void*
> -- Check size of void* - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> CMake Error: Error in cmake code at
> /export/home/neoclust/BUILD/wengophone-2.1/owbuild/owbuild/OWDefaultCompilerFlags.cmake:12:
> Unknown CMake command "ow_check_cxx_compiler_flag".
> 

Same for me.

> 
> 
> someone have an idea ?

The attached patch work for me. Like the header comment said "order
matters" !! ;)

Cheers.

Didier

-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE
Index: wengophone-2.1/owbuild/owbuild/CMakeLists.txt
===
--- wengophone-2.1/owbuild/owbuild/CMakeLists.txt   (révision 9139)
+++ wengophone-2.1/owbuild/owbuild/CMakeLists.txt   (copie de travail)
@@ -1,5 +1,6 @@
 # Warning!!! order matters
 
+include(OWCheckCXXCompilerFlag)
 include(OWDefaultCompilerFlags)
 include(OWDefaultConfig)
 
@@ -22,7 +23,6 @@
 include(OWAddSources)
 include(OWAutoconf)
 include(OWChangeInstallName)
-include(OWCheckCXXCompilerFlag)
 include(OWCheckProject)
 include(OWCopyDir)
 include(OWCopyFile)


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Compiling Wengo NG : config.h ?

2006-12-19 Thread Didier LINK 
Hi

Le mardi 19 décembre 2006 à 18:09 +0100, Gorka Pinillos a écrit :
> I continue trying to compile wengo and now it reports me this error:
> 
> c:\dev\trunk\wifo\srtp\include\err.h(49) : fatal error C1083: No se 
> puede abrir
> el archivo incluir: 'config.h': No such file or directory
> scons: *** [release-symbols\wifo\sVoIP\src\crypto.obj] Error 2
> scons: building terminated because of errors.
> 
> What's the problem
> Thank you all.

The problem is from the rev 8909 I think.

You use scons for compilation and this changeset introduce the
generation of the config.h in the srtp library by the cmake construct
system.

Cmake generate this file from a template with correct values for all
plateform supported by openwengo. This remplace a static config.h file
only suitable for Windows plateform.

So if you really need scons it's a bug that you can report, if not use
cmake instead.

Regards.

Didier Link

-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Build problem of WengoPhone 2.1 branch on x86_64

2006-12-18 Thread Didier LINK 
Le lundi 18 décembre 2006 à 14:25 +0100, Nicolas Lécureuil a écrit :
> hi,

Hi Nicolas,

> 
> on x86_64, wengophone doesn't compile and i obtain this error:
> 
> [ 40%] Building C object wifo/sVoIP/CMakeFiles/svoip.dir/src/crypto.o
> In file included 
> from 
> /export/home/neoclust/BUILD/wengophone-2.1/wifo/srtp/crypto/include/datatypes.h:50,
>  
> from 
> /export/home/neoclust/BUILD/wengophone-2.1/wifo/srtp/crypto/include/rand_source.h:50,
>  
> from 
> /export/home/neoclust/BUILD/wengophone-2.1/wifo/srtp/crypto/include/crypto_kernel.h:49,
>  
> from /export/home/neoclust/BUILD/wengophone-2.1/wifo/srtp/include/srtp.h:49,
>  
> from /export/home/neoclust/BUILD/wengophone-2.1/wifo/sVoIP/src/crypto.c:37:
> /export/home/neoclust/BUILD/wengophone-2.1/wifo/srtp/crypto/include/integers.h:83:
>  
> error: conflicting types for 'uint64_t'
> /usr/include/stdint.h:56: error: previous declaration of 'uint64_t' was here
> In file included 

You can see the ticket #1194 [1] for the problem and a temporary
solution.

Best regards.

Didier Link

[1] http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1194


-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] [linux] bad REGISTER request with 64 bits system

2006-12-17 Thread Didier LINK 
Le dimanche 17 décembre 2006 à 01:39 +0100, Didier LINK a écrit :
> > It is a bug in phapi or maybe in exosip.
> 
> I've finally build the "trunk" of wengophone and the wireshark session
> show me that all work fine in 64 bits !

Seen this I've worked on porting the complete update of libosip2 in the
2.0 branche, I've not attached the file because of his size (about 1 MO)
but if someone want it to review I can send it ;)

The only "doubt" I have is in the file
wengophone-2.0/wifo/eXosip/src/jrequest.c where some changes exists
between 2.0 and trunk.

Thanks for your good work on wengophone.

Best regards.

Didier Link

-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] [linux] bad REGISTER request with 64 bits system

2006-12-16 Thread Didier LINK 

> It is a bug in phapi or maybe in exosip.

I've finally build the "trunk" of wengophone and the wireshark session
show me that all work fine in 64 bits !

I think it's the recent update of libosip in the changeset 8836.

I've see in the Changelog of libosip2 this line :

libosip2 (2.2.3)
* fix 64-bit (amd64) issue with hash.

What is the version of this library in the 2.0 and 2.1 branches ?

If they are before this 2.2.3 I think this is the main problem in the
bug I see this day ;)

I've see some changes in the "md5" part of osip2, notably a typedef
change from "long int UINT4" to "int UINT4"
(wengophone-ng/trunk/wifo/libosip2/include/osipparser2/osip_md5.h) that
is common in errors with 64 bits porting ... interessant no ? ;)

Cheers.

Didier




signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] [linux] bad REGISTER request with 64 bits system

2006-12-16 Thread Didier LINK 
Le samedi 16 décembre 2006 à 23:17 +0100, Andreas Schneider a écrit :
> Didier LINK wrote:
> > Hi all,
> Hi Didier,
> 
> > 
> > If you need it, I can send to you all the wireshark records I have.
> > 
> > Thanks for comment(s), I can also open a new ticket on trac if you want.
> 
> You are looking for
> 
> http://dev.openwengo.org/trac/openwengo/trac.cgi/ticket/999
> 
> :)
> 

Yes I know, I've write two of the comments, my pseudo is Zanfib ;)

Without more comments I've tried the mailing-list, thanks to your
attention !

I think the problem is maybe in the md5 digest code or something
similar. Anybody have an idea how to look for a more accurate
debugging ? I'm completely new in the openwengo code and I need a "big
picture" to point in the right direction ;)

Regards.

Didier Link


-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] [linux] bad REGISTER request with 64 bits system

2006-12-16 Thread Didier LINK 
Hi all,

I face a big problem of authentification with wengophone.

On my Gentoo 2006.1 64 bits distribution, the launch of qtwengophone-2.0
from the nightly builds (rev 8883) works very well, the SIP session
looks normal with a wireshark record.

With the rev 8886 from the svn repository of branche-2.0, the
compilation is ok, the launch too but the SIP session finally abort with
a "403 wrong password" answer from the voip.wengo.fr server.

The wiresharks records looks the same until the REGISTER request, the
packet is wellformed and looks normal but certainly there is a problem
with the digest exchange between server and wengophone.

If you need it, I can send to you all the wireshark records I have.

Thanks for comment(s), I can also open a new ticket on trac if you want.

Best regards.

Didier Link


-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]
SIP : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Avoid gcc 4.1: it makes wengophone crash!

2006-12-14 Thread Didier LINK 
Le mercredi 13 décembre 2006 à 23:45 +, Ludovico Cavedon a écrit :
> Hi!
> 
Hi,

> I noticed that gcc 4.1 is producing bad code with boost libraries, so 
> WengoPhone
> is crashing very often.
> 
> In particular automatic slot disconnection upon object destruction is not
> working right.
> 
> To test if your compiler is broken, you can try to compile and run this file:
> http://netgroup.polito.it/~cavedon/test-gcc-boost.cc
> this should be the correct output
> http://netgroup.polito.it/~cavedon/test-gcc-boost.out
> 
> I have tried under Ubuntu edgy:
> BAD: gcc-4.1 (GCC) 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)
> OK: gcc-4.0 (GCC) 4.0.4 20060630 (prerelease) (Ubuntu 4.0.3-4)
> OK: gcc-3.4
> 

On Gentoo 2006.1 (up to date) amd64 (64bits distribution) I've tested
this versions of gcc :

BAD: gcc-4.1.1 [gcc (GCC) 4.1.1 (Gentoo 4.1.1-r3)]
BAD: gcc-4.1.0 [gcc-4.1.0 (GCC) 4.1.0 (Gentoo 4.1.0-r1)]
OK: gcc-3.4.6 [gcc-3.4.6 (GCC) 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0,
pie-8.7.9)]

Thanks for the test case.

Do you think that the ticket #1199 is related to this problem ?

Regards.

Didier Link



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Windows & QTCommercial Flags

2006-12-07 Thread Didier LINK 
Le jeudi 07 décembre 2006 à 22:24 +, Christopher Jimenez a écrit :
> Hi Wengo Comunity.

Hi Christopher,

> Searching the code i see this line a couple of times
> #if (defined OS_WINDOWS) && (defined QT_COMMERCIAL)
> 
> I was wondering how do you define in the client that is using QT_COMMERCIAL?
> Where is this flag located? and how can i Change it? It this located in some 
> python script?
> Or i should defined in the soptions or in the compile line?
> Something like?
> scons mode=release qtwengophone qtcommercial=1

This define is located in the QT headers that's used during compile time
(like in qt/qglobal.h). The only way to have it defined is to have the
commercial version of QT, not the GPL one (open source).

So if you paid for a commercial license of QT you have the headers and
the define ;)

Why do you want it defined ?

Best regards.

Didier Link



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] [linux] amd64 configuration/compilation problems

2006-11-29 Thread Didier LINK 
Le mercredi 29 novembre 2006 à 17:23 +0100, Didier LINK a écrit :
> Le mardi 28 novembre 2006 à 23:46 +0100, Didier LINK a écrit :
> > For the lack of -fPIC during compilation on linux amd64, I've forced the
> > flag in the CMakeCache.txt and rebuild the Makefiles. It seems to work
> > but it's not the good way ...
> > 
> > I don't know why the amd64 is missed in the configuration step, anyone
> > that known cmake can look at this problem or point me to a good cmake
> > documentation ? (not the book please, to expensive for just a bugfix ;))
> 
> After some investigation I found that cmake don't work as expected on my
> computer. With complete listing of cmake variables[1], the variable
> CMAKE_SYSTEM_PROCESSOR is set to "unknown" ! :(
> 
> It's a bug in cmake that prevent a working compilation of openwengo
> project on my Gentoo. Anybody have an account on cmake bug tracker to
> create a new bug report please ?

Last update I hope,

I just create the bug #4090 on the cmake bug tracker because after more
tests they use "uname -p" in place of "uname -m" in processor
architecture detection, I think it's wrong. I make the change of uname
option in the detection routine of cmake and now the -fPIC flag is
correctly detected and added to the compilation on my system.

I hope cmake will consider this change or wengophone needs another macro
to include -fPIC on 64 bits processors ...

Regards.

Didier LINK



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] [linux] amd64 configuration/compilation problems

2006-11-29 Thread Didier LINK 
Le mardi 28 novembre 2006 à 23:46 +0100, Didier LINK a écrit :
> For the lack of -fPIC during compilation on linux amd64, I've forced the
> flag in the CMakeCache.txt and rebuild the Makefiles. It seems to work
> but it's not the good way ...
> 
> I don't know why the amd64 is missed in the configuration step, anyone
> that known cmake can look at this problem or point me to a good cmake
> documentation ? (not the book please, to expensive for just a bugfix ;))

After some investigation I found that cmake don't work as expected on my
computer. With complete listing of cmake variables[1], the variable
CMAKE_SYSTEM_PROCESSOR is set to "unknown" ! :(

It's a bug in cmake that prevent a working compilation of openwengo
project on my Gentoo. Anybody have an account on cmake bug tracker to
create a new bug report please ?

Thanks and regards.

Didier Link

[1] see
http://www.cmake.org/Wiki/CMake_Useful_Variables/Get_Variables_From_CMake_Dashboards
 for a good script


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] [linux] amd64 configuration/compilation problems

2006-11-28 Thread Didier LINK 

For the lack of -fPIC during compilation on linux amd64, I've forced the
flag in the CMakeCache.txt and rebuild the Makefiles. It seems to work
but it's not the good way ...

I don't know why the amd64 is missed in the configuration step, anyone
that known cmake can look at this problem or point me to a good cmake
documentation ? (not the book please, to expensive for just a bugfix ;))

Thanks and regards.

Didier Link



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] [linux] amd64 configuration/compilation problems

2006-11-28 Thread Didier LINK 
PLUGIN_DLL
-- ** phamrplugin_PRIVATE_COMPILE_FLAGS=-funroll-loops
-- ** phamrplugin_PUBLIC_LINK_FLAGS=
-- ** phamrplugin_PRIVATE_LINK_FLAGS=
-- ** phamrplugin_BUILD_VERSION=
-- ** phamrplugin_API_VERSION=
-- **
CMake Error: Error in cmake code at
Path to a file.:17:
MESSAGE phspeexplugin: speex_INCLUDE_DIRS and speex_INCLUDE_DIR empty
Current CMake
stack: 
/home/didier/temp/openwengo-latest/trunk/wifo/phapi/phspeexplugin/CMakeLists.txt
-- Configuring done


With this errors I can't test further the programm on my amd64 box. Can
you tell me what version/revision I can use for a deeper testing
please ?

Regards.

Didier Link



signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

RE: [Wengophone-devel] [linux] - a review

2006-11-27 Thread Didier LINK 
Le lundi 27 novembre 2006 à 12:34 +0100, Jérôme WAGNER a écrit :
> Hello Didier,

Hello Jérôme,

> 
> Thank you for your report,

Your welcome, it's a pleasure and because I need your software and I
have somme skills in linux configuration/development/etc..., I need to
participate to your effort ;)

> 
> It is necessary now that we squash all those (longstanding?) issues on the
> GNU/Linux platform.

Sure, I feel some linux users discouraged by this bugs, sad.

> 
> Do you agree to participate in tests on this subject while they are being
> debugged ?

All you want if I have the time !!

Best regards.

Didier

-- 
Didier Link <[EMAIL PROTECTED]>
Jabber : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]
SIP : [EMAIL PROTECTED]

Clé GPG : 75BAC9EE


signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] [linux] - a review

2006-11-25 Thread Didier LINK 
ion/qt/QtBrowserWidget.h:29: erreur: forward
declaration of ‘struct QtBrowser’
scons: *** [debug/wengophone/src/presentation/qt/QtBrowserWidget.o]
Error 1
scons: building terminated because of errors.


Sorry for the long post but if I can help you to test the amd64 linux
port of the wengophone-2, I will be happy :)

Thanks and regards.

Didier Link




signature.asc
Description: Ceci est une partie de message	numériquement signée
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel