search for: sorri

Displaying 20 results from an estimated 45807 matches for "sorri".

Did you mean: sorry
2004 Jul 29
0
cross-compile R darwin2win, almost there
I'm trying to cross-compile R on a Mac OS X box to target Win32. It works quite well, everything works, except for one fortran file ppr.f in the stats package: ---------- Making package stats ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and metadata making DLL ... i386-mingw32-g77 -O2 -Wall -c ppr.f -o ppr.o ppr.f:803: sorry, unimplemented: data
2004 Jul 29
0
cross-compile R darwin2win, almost there
I'm trying to cross-compile R on a Mac OS X box to target Win32. It works quite well, everything works, except for one fortran file ppr.f in the stats package: ---------- Making package stats ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and metadata making DLL ... i386-mingw32-g77 -O2 -Wall -c ppr.f -o ppr.o ppr.f:803: sorry, unimplemented: data
2007 Jul 02
0
trying to get vpb to compile
So I've got a Voicetronix card and it looks like the kernel driver works. Other than the 0's for ID info. vpb: Driver Version = 4.0 vpb: major = 251 vpb: tmp [0xfc8fec00] dev->res3 [0xfc8fec00] vpb: tmp [0xfc8c0000] dev->res2 [0xfc8c0000] vpb: 1WS Write cycle vpb: Manufactured 00/00/0000 vpb: Card version 00.00 vpb: Serial number 00000000 vpb: Setting up udev... vpb:1 V4PCI's
2004 Dec 31
1
FC3 compile with new 2.6.10 fails
All, I have FC3 fedora core 3 and just installed and compiled 2.6.10. after rebooting I attempted to recompile zaptel-1.0.3. I did a make clean then make. I got the following errors. Any suggestions? ------------------------------- /usr/src/digium/zaptel-1.0.3/torisa.c:1139: warning: 'set_tor_base' defined but not used CC [M] /usr/src/digium/zaptel-1.0.3/wcusb.o CC [M]
2015 Jul 26
4
Fedora change that will probably affect RHEL
On Sat, 25 Jul 2015 11:16:18 -0600 Chris Murphy <lists at colorremedies.com> wrote: > On Sat, Jul 25, 2015 at 9:40 AM, Scott Robbins <scottro at nyc.rr.com> wrote: > > This might show up twice, I think I sent it from a bad address previously. > > If so, please accept my apologies. > > > > > > In Fedora 22, one developer (and only one) decided that if
2012 May 05
1
f951.exe: sorry, unimplemented: 64-bit mode not compiled
Hello: Under my Windows 7 system, "R CMD check DiercxkSpline_1.1-5.tar.gz" fails because: f951.exe: sorry, unimplemented: 64-bit mode not compiled in make: *** [bispev.o] Error 1 gfortran -m64 -O2 -mtune=core2 -c bispev.f -o bispev.o f951.exe: sorry, unimplemented: 64-bit mode not compiled in make: *** [bispev.o] Error 1 ERROR: compilation failed for package
2003 Jan 01
1
iso 2.00 isolinux: Checksum error, sorry...
Hi, I tried to install redhat 8.0 on a laptop and ran into the following problem. ISOLINUX 1.75 2002-06-14 isolinux failed to get sector size, assuming 0800 isolinux: Image checksum error, sorry... At that point, I followed the advice on the isolinux webpage, and reburned a CD using isolinux 2.00 with debug. The error message was: ISOLINUX 2.00 2002-10-25 Copyright (C) 1994-2002 H. Peter
2006 May 17
65
BACKPACK: There was a problem processing your email
We''re sorry, but there was an error processing your recent email to a Backpack page: Subject: Re: [Rails] Knowing id before a call to save To: rails@lists.rubyonrails.org There''re a variety of things that can cause you to see this error, but it''s OUR fault, NOT YOURS. Often times this is a temporary glitch that will be fixed within a few seconds or minutes.
2005 Jan 21
0
Problem compiling zaptel-1.0.3
I am having a problem compiling zaptel on my Arch Linux (linux 2.6.10) system: CC [M] /home/sbn/src/zaptel-1.0.3/wcfxs.o /home/sbn/src/zaptel-1.0.3/wcfxs.c: In function `wcfxs_interrupt': /home/sbn/src/zaptel-1.0.3/wcfxs.c:473: sorry, unimplemented: inlining failed in call to 'wcfxs_proslic_check_hook': function body not available /home/sbn/src/zaptel-1.0.3/wcfxs.c:810: sorry,
2006 Oct 17
1
1.4 gsm files changed??
I like to use zgsmplay to preview Asterisk's gsm files. Works like a charm in 1.2. But something changed in 1.4- they play at the wrong speed, very slowly. They sound fine in the normal course of using the Asterisk server. The file sizes seem wacko. The first example is from 1.2, the second from 1.4: $ ls -l im-sorry.gsm -rw-r--r-- 1 1000 1000 1419 Dec 5 2005 im-sorry.gsm $ ls -l
2013 Apr 18
0
Sorry
Sorry to all if i sned varipous time the same mail thunderbird report me that i didnt send it. like reindl that is angry and furious telling me that im a idiot. * there where FIVE replies to your post yesterday * independent of what TB says, you got your own message from the list * independent of what TB says, you got the replies from the list * so you are an idiot Am 18.04.2013 21:05, schrieb
2010 Feb 15
1
moved from ruby 1.8.6 to 1.8.7 and "We're sorry, but something went wrong."
I''m a windows user, and I was using ruby 1.8.6 installer over at RubyInstaller.org. All was working well, but I decided to give ruby 1.8.7 a try. I uninstalled 1.8.6, downloaded and installed ruby 1.8.7 from rubyinstaller, reinstalled rails and all of my gems, and copied over sqlite3.def and sqlite3.dll to the Ruby/bin. I then my start my server (just using webrick for now, same as
2014 May 16
1
Sorry
Sorry for the messed up replies. ?The web based icloud interface forces the writer to reply at the top of the email and if you try to write at the bottom by deleting a few lines of the message or selecting the whole message, deleting it, adding some spaces and then pasting back and go to the end it and adding a reply, it kills the indentation. -wes
2005 Feb 09
2
Re: problems with 2.4.28 + Julian''s patch
I am using kernel 2.6.9 (gentoo,AMD64 version) + routes-2.6.9-11.diff If compile kernel with gcc 3.4.3, then the similar error comes out: ------------------ net/ipv4/fib_frontend.c: In function `fib_validate_source'': include/net/ip_fib.h:181: sorry, unimplemented: inlining failed in call to ''fib_result_table'': function body not available net/ipv4/fib_frontend.c:204:
2017 Apr 28
3
[Patch] Non-diegetic support for channel mapping 254
Hey Jean-Marc, sorry about that... extra lines... was it whitespace? If so, sorry about that. Thanks! Cheers, Drew Cheers, Drew On Fri, Apr 28, 2017 at 2:43 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Oops, looks like we both should have been more careful. The patch had > some extra lines that shouldn't have been there. > > Jean-Marc > > On
2005 Jan 08
1
problems with 2.4.28 + Julian''s patch
With 2.4.28 and Julian Anastasov''s http://www.ssi.bg/~ja/routes-2.4.27-9.diff patch, I get the following when I attempt to build my kernel. Any ideas? Thanks! gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-unit-at-a-time -nostdinc
2006 Feb 08
35
BACKPACK: There was a problem processing your email
We''re sorry, but there was an error processing your recent email to a Backpack page: Subject: [Rails] RJS templates before, during and after To: rails@lists.rubyonrails.org There''re a variety of things that can cause you to see this error, but it''s OUR fault, NOT YOURS. Often times this is a temporary glitch that will be fixed within a few seconds or minutes.
2003 Sep 05
3
Dovecot not starting
Hello everybody, sorry for stupid qustion, but I have following problem: I succesfully installed Dovecot on Debian (from source). Now I want to run it. I tryed: # /usr/local/dovecot/sbin/dovecot # but nothing happened: # ps -Af | grep dove ....... ps -Af | grep dove # What is wrong? I want Dovecot to serve POP3 over SSL. Many thanks and sorry again :o)
2008 Mar 13
15
using norfc1918
Hello Tom. Sorry, don't answer on my previouse letter, i forget to set subject. I fix this in current. And now about my question. I ask you before about method of stopping RFC1918 traffic on external interface and you advised me follow rule: REJECT! all net:$RFC1918_NETS Can i replace this rule by 'norfc1918' option in 'interfaces' file for this interface?
2015 Jul 25
4
Fedora change that will probably affect RHEL
This might show up twice, I think I sent it from a bad address previously. If so, please accept my apologies. In Fedora 22, one developer (and only one) decided that if the password chosen during installation wasn't of sufficient strength, the install wouldn't continue. A bug was filed, and there was also a great deal of aggravation about it on the Fedora testing list. So, it was