search for: oic

Hi, Is there a way to use swissvoice IP10 in MGCP mode behind NAT. I already use this fonctionnality with a PBX other then asterisk, and it work very well. In fact, I need to use this settings in the IP10 telnet session set xgcp rgw_name MAC_ADDR set tcid 0 notify_entity ca@[@IP PBX]:2427 In fact, the phone register with the MAC@ a...

...-vectorize/builds/220/steps/lnt.nightly-test > > I believe there are: > > http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL > > They are just automatically XFAILED after they occur a second > time. ;-) OIC... then that's not good... So it seems that prior the build 108 the testing process always timed out (it looks like it had a timeout of 20 minutes which was not long enough). At build 108, it lists those applications as failing. I am pretty sure that there were no x86 test-suite failures when...

...eve there are: > >> > >> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL > >> > >> They are just automatically XFAILED after they occur a second > >> time. ;-) > > > > OIC... then that's not good... > > > > So it seems that prior the build 108 the testing process always > > timed out (it looks like it had a timeout of 20 minutes which was > > not long enough). At build 108, it lists those applications as > > failing. > > Yes....

...t; http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL > >>>> > >>>> They are just automatically XFAILED after they occur a second > >>>> time. ;-) > >>> > >>> OIC... then that's not good... > >>> > >>> So it seems that prior the build 108 the testing process always > >>> timed out (it looks like it had a timeout of 20 minutes which was > >>> not long enough). At build 108, it lists those applications as &gt...

...ghtly-test >> >> I believe there are: >> >> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL >> >> They are just automatically XFAILED after they occur a second >> time. ;-) > > OIC... then that's not good... > > So it seems that prior the build 108 the testing process always timed > out (it looks like it had a timeout of 20 minutes which was not long > enough). At build 108, it lists those applications as failing. Yes. > I am pretty sure that there were n...

...lvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL >>>>>> >>>>>> They are just automatically XFAILED after they occur a second >>>>>> time. ;-) >>>>> >>>>> OIC... then that's not good... >>>>> >>>>> So it seems that prior the build 108 the testing process always >>>>> timed out (it looks like it had a timeout of 20 minutes which was >>>>> not long enough). At build 108, it lists those applica...

...t;>> >>>> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL >>>> >>>> They are just automatically XFAILED after they occur a second >>>> time. ;-) >>> >>> OIC... then that's not good... >>> >>> So it seems that prior the build 108 the testing process always >>> timed out (it looks like it had a timeout of 20 minutes which was >>> not long enough). At build 108, it lists those applications as >>> failing. &...

...t; this is only when building like the testsuite > does > (i.e. with link-time optimization + llc): if you directly do: > clang tsc.c dummy.c -std=gnu99 -O3 > then you get 16000. > > > > > This is all on Darwin, right? > > No, this is on x86-64 (ubuntu) linux. OIC, interesting! > > > > > I would certainly tend to suspect an 80-bit-intermediate issue, > > but, both gcc and clang give 16000 on PowerPC (which has no > > 80-bit). > > Not sure what you are saying here. The issue is the x86 internally > uses 80 bits > for...

...t; this is only when building like the testsuite > does > (i.e. with link-time optimization + llc): if you directly do: > clang tsc.c dummy.c -std=gnu99 -O3 > then you get 16000. > > > > > This is all on Darwin, right? > > No, this is on x86-64 (ubuntu) linux. OIC, interesting! > > > > > I would certainly tend to suspect an 80-bit-intermediate issue, > > but, both gcc and clang give 16000 on PowerPC (which has no > > 80-bit). > > Not sure what you are saying here. The issue is the x86 internally > uses 80 bits > for...

Hi, I would like to know if it is possible to change the IP address of a Samba NT4 PDC? So far I could only find the guide regarding Samba AD DCs. What do I need to take into account, and what are the general steps apart from re-configuring networking? Thank you very much, Benjamin

On Wed, 29 Sep 2004, Reid Spencer wrote: > > On Tue, 28 Sep 2004, Paolo Invernizzi wrote: > >>The next major problem is that VC has only > >> > >>int rand(void) > >>void srand( int seed ) > >> > >>So I donno how to compile the > >>ExecutionEngine/Interpreter/ExternalFunctions.cpp that refers to the > >>drand48 srand48

Hmm, I guess I need a sys::Math::getRandom() function that uses a "good" random number generator on the given platform. I'll make a note of this and tuck it away for future implementation. Reid. Chris Lattner wrote: > On Tue, 28 Sep 2004, Paolo Invernizzi wrote: > > >>The next major problem is that VC has only >> >>int rand(void) >>void srand(

Now it's a good time to introduce the new tool 'o2info' since kernel part of OCFS2_IOC_INFO ioctl has been pulld upstream by linus. The following 6 patches have already got sunil's SOBs, and now they're trying to attract more reviewers before it goes to central repo with a modification of getting manual pages being introduced.

On 06/20/2012 11:07 PM, Hal Finkel wrote: > On Tue, 12 Jun 2012 11:15:12 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 02/05/2012 02:42 PM, Hal Finkel wrote: >>> I think that it would be a good idea to have a buildbot set up to >>> run the test suite with -vectorize. Could one of the existing >>> machines do this also? >>

On Tue, 12 Jun 2012 11:15:12 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 02/05/2012 02:42 PM, Hal Finkel wrote: > > I think that it would be a good idea to have a buildbot set up to > > run the test suite with -vectorize. Could one of the existing > > machines do this also? > > It took some time, but we have this now: > >

...ng-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL > >>>>>> > >>>>>> They are just automatically XFAILED after they occur a second > >>>>>> time. ;-) > >>>>> > >>>>> OIC... then that's not good... > >>>>> > >>>>> So it seems that prior the build 108 the testing process always > >>>>> timed out (it looks like it had a timeout of 20 minutes which > >>>>> was not long enough). At build 108, it...

...to change to make this happen. Here is the relevant portion of /var/log/messages when I plug in the card reader: Sep 4 16:31:11 bargainhunter kernel: usb 7-6: new high speed USB device using e hci_hcd and address 12 Sep 4 16:31:11 bargainhunter kernel: usb 7-6: configuration #1 chosen from 1 ch oice Sep 4 16:31:11 bargainhunter kernel: scsi11 : SCSI emulation for USB Mass Stora ge devices Sep 4 16:31:16 bargainhunter kernel: Vendor: Generic Model: USB SD Reader Rev: 1.00 Sep 4 16:31:16 bargainhunter kernel: Type: Direct-Access ANSI SCSI revision: 00 Sep...

...ng-x86_64-darwin10-nt-O3-vectorize/builds/220/steps/lnt.nightly-test/logs/tests.XFAIL > >>>>>> > >>>>>> They are just automatically XFAILED after they occur a second > >>>>>> time. ;-) > >>>>> > >>>>> OIC... then that's not good... > >>>>> > >>>>> So it seems that prior the build 108 the testing process always > >>>>> timed out (it looks like it had a timeout of 20 minutes which > >>>>> was not long enough). At build 108, it...

Hi Hal, On 05/10/12 20:32, Hal Finkel wrote: > ----- Original Message ----- >> From: "Duncan Sands" <duncan.sands at gmail.com> >> To: "Hal Finkel" <hfinkel at anl.gov> >> Cc: llvmdev at cs.uiuc.edu >> Sent: Friday, October 5, 2012 12:10:03 PM >> Subject: Re: TSVC/Equivalencing-dbl >> >> Oops, I ran the testsuite wrong:

Before you jump ahead, yes I do have chan_zap.so loaded.. Call Flow: Asterisk 1 --IAX2--> Asterisk 2 ---> PRI -- Accepting AUTHENTICATED call from 22.22.22.22: > requested format = ulaw, > requested prefs = (), > actual format = ulaw, > host prefs = (ulaw|alaw|gsm), > priority = mine -- Executing