Displaying 20 results from an estimated 14816 matches for "incorrect".
2008 May 22
2
1501-511 Compilation failed for file ch2inv.f - R on AIX 5.2.
...ot;Makedeps" is up to date.
Target "libpcre.a" is up to date.
Target "Makedeps" is up to date.
Target "libz.a" is up to date.
Target "Makedeps" is up to date.
f95 -g -c ch2inv.f -o ch2inv.o
"ch2inv.f", line 1.2: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 2.1: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 3.4: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 4.4: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 5.4: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 6.1: 15...
2006 Feb 07
0
[R] R compile on AIX 5.2
...is 2.
Stop.
make: The error code from the last command is 1.
Stop.
make: The error code from the last command is 1.
Stop.
Running make with R-devel_2006-02-05:
/home/mbeason/work/R-devel/src/appl
f95 -g -c ch2inv.f -o ch2inv.o
"ch2inv.f", line 1.2: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 2.1: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 3.4: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 4.4: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 5.4: 1515-019 (S) Syntax is incorrect.
"ch2inv.f", line 6.1: 15...
2009 Jan 09
5
grep : escape "*"
...t;, "4-4"))
[1] 3
> grep("/", c("/3", "2*3", "4-4"))
[1] 1
> grep("*", c("/3", "2*3", "4-4"))
Erreur dans grep("*", c("/3", "2*3", "4-4")) :
expression régulière incorrecte '*'
De plus : Warning message:
In grep("*", c("/3", "2*3", "4-4")) :
erreur rgcomp : 'Expression régulière précédente incorrecte'
> grep("\*", c("/3", "2*3", "4-4"))
Erreur dans grep("*",...
2019 Dec 15
0
[vhost:linux-next 12/12] drivers/vhost/vhost.c:1968:25: sparse: sparse: incompatible types in comparison expression (different type sizes):
...ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp at intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/vhost/vhost.c:763:17: sparse: sparse: incorrect type in return expression (different address spaces)
drivers/vhost/vhost.c:763:17: sparse: expected void [noderef] <asn:1> *
drivers/vhost/vhost.c:763:17: sparse: got void *
drivers/vhost/vhost.c:763:17: sparse: sparse: incorrect type in return expression (different address spa...
2004 Aug 26
0
Slow Samba share--why?
...SMB Read AndX Request, FID: 0x174a, 61440 bytes at offset 184320
230 1.479628 Sarge XP SMB Read AndX Response, FID: 0x174a, 61440 bytes
231 1.479654 Sarge XP TCP [Continuation to #230] netbios-ssn > 1121 [ACK] Seq=191515 Ack=1574 Win=27872 [CHECKSUM INCORRECT] Len=1460
233 1.479683 Sarge XP TCP [Continuation to #230] netbios-ssn > 1121 [ACK] Seq=194435 Ack=1574 Win=27872 [CHECKSUM INCORRECT] Len=1460
234 1.479693 Sarge XP TCP [Continuation to #230] netbios-ssn > 1121 [ACK] Seq=195895 Ack=1574 Win=27872 [CHECKS...
2009 Dec 16
1
[LLVMdev] incorrect x86 instruction size calculation
...I'm trying to write some backends for LLVM that generate code that complies
with SFI validation rules by re-implementing SFI for the LLVM x86 backend
based on the Google NaCl project.
However, in trying to implement 32-byte code alignment,
X86InstrInfo::GetInstSizeInBytes() is returning incorrect instruction sizes
for certain instructions (that I have seen so far): MOV32mi, LEA32r,
MOV32mr, and MOV32rm.
MOV32mi is always calculated incorrectly while the remaining 3 are sometimes
calculated incorrectly. Just to illustrate:
8d 9c 24 30 0a 00 00 LEA32r
cal...
2019 Jun 26
3
LAA behavior on Incorrect #pragma omp simd.
Hi All,
I have a doubt regarding the behavior of LoopAccessAnalysis on
incorrect #pragma omp simd with -fopenmp-simd flag.
How should the compiler behave if the #pragma omp simd on a loop is
incorrect and can be proved by Loop Access Analysis.
Here is the sample code.
#pragma omp simd
for (dim_t p = 0; p < m; ++p)
#pragma unroll
for (dim_t i = 0; i < 6; ++i...
2008 Mar 01
2
Newbie: Incorrect number of dimensions
...<- (1-pt(abs(data.sub),50))*2
diff<- mt.rawp2adjp(two_side)
all_differ<-diff[[1]][37211:10000,]
all_differ
#####list of differentially expressed genes##########
> probe.names<-
+ all_differ[[2]][all_differ[[1]][,"BY"]<=0.01]
Error in all_differ[[1]][, "BY"] : incorrect number of dimensions
Hi,
I am pretty new with R. What i am trying to do is to find all differentially
express genes and list of differentially expressed genes. Am i doing
something wrong?
I keep getting incorrect number of dimensions. How do i find out the correct
dimensions?
thanks,
Keizer
-...
2016 Oct 20
2
Correcting "incorrect userParameters value on object...." ???
sernet-samba-4.2.14-23.el6.x86_64
Errors [on all DCs] related to incorrect userParameters values - on
user's that are working. How does one go about rebuilding/correcting
this value?
[root at larkin28 ~]# samba-tool dbcheck --reset-well-known-acls --fix -
-yes
Checking 1743 objects
ERROR: incorrect userParameters value on object
CN=darrell,OU=Industries Users,DC=exa...
2020 Sep 23
2
Incorrect Cortex-R4/R4F/R5 ProcessorModel in ARM.td
In ARM.td, I see that the ProcessorModel for cortex-r4, cortex-r4f, and cortex-r5 (as well as r7 and r8) is based on "CortexA8Model", which seems incorrect. When this was added in 2015, there were also comments associated with this configuration, such as "// FIXME: R5 has currently the same ProcessorModel as A8" (later removed). The processor model for Cortex-r52 appears to be correct and corresponds to an associated "CortexR52Model&q...
2003 Sep 08
1
Double dialing with asterisk and Grandstream BudgeTone-100
Has anyone seen/dealt with the Grandstream BudgeTone-100 producing double
dialing with asterisk?
Thanks
JDT
Example: (password input = 101)
-- Playing 'vm-password'
-- Incorrect password '11001' for user '101' (context = <any>)
-- Playing 'vm-incorrect'
-- Playing 'vm-password'
-- Incorrect password '110011' for user '101' (context = <any>)
-- Playing 'vm-incorrect'
-- Playing 'vm-p...
2005 May 14
2
[LLVMdev] Cygwin llvm-gcc build error
...reference in Info; reword to avoid that.
../../../src/llvm-gcc/gcc/doc//cppopts.texi:341: warning: @strong{Note...}
produ
ces a spurious cross-reference in Info; reword to avoid that.
../../../src/llvm-gcc/gcc/doc/cpp.texi:3203: Cross reference to nonexistent
node
Predefined Macros' (perhaps incorrect sectioning?).
../../../src/llvm-gcc/gcc/doc/cpp.texi:1405: Cross reference to nonexistent
node
Prescan' (perhaps incorrect sectioning?).
../../../src/llvm-gcc/gcc/doc/cpp.texi:1063: Cross reference to nonexistent
node
Headers' (perhaps incorrect sectioning?).
../../../src/llvm-gcc/gcc/d...
2012 Oct 03
1
Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8
After updating our Samba4 server from alpha17 to beta8 "samba-tool dbcheck" shows 24 "incorrect GUID" errors.
What does it mean and what should i do to fix this?
Thx
2009 Nov 24
0
[LLVMdev] X86InstrInfo::GetInstSizeInBytes() calculating incorrect size
I'm noticing the X86InstrInfo::GetInstSizeInBytes() function returning
incorrect sizes for some instructions. I looked through the llvm-dev
archives and noticed that a patch was submitted once in April 2009 for
instruction length calculation on amd-64. I'm using Intel Core 2 Duo (64
bit) so maybe there is a similar issue? I don't have another computer I can
test this...
2008 Oct 29
3
Incorrect order
I am using the order function and the result seems to be incorrect:
> a<-c(20,30,15,40)
> order(a)
[1] 3 1 2 4
Any suggestions?
Thanks,
Laura
--
View this message in context: http://www.nabble.com/Incorrect-order-tp20224993p20224993.html
Sent from the R help mailing list archive at Nabble.com.
2014 May 22
2
[LLVMdev] GVN incorrectly handling readnone parameter attribute?
...et i32* %p
>> }
>>
>> define void @store(i32* nocapture readnone %p) {
>> entry:
>> store i32 10, i32* %p, align 4, !tbaa !1
>> ret void
>> }
>>
> Further to my first post, based on the definition of readnone on an
> argument, this is also incorrect. After get_pntr() has been inlined
> into store(), we are dereferencing %p, but it is still marked
> readnone.
>
> So we seem to have a couple of issues. First GVN seems to be making
> incorrect assumptions based on argument attributes, and secondly
> inlining can invalidate exi...
2006 Aug 04
1
incorrect checksum for freed object?
...application environment (I can''t get it to fail
in my unit tests).
The error always occurs AFTER my controller method returns (not when I make
the calls). Also, the error does not always look the same. Sometimes it
ends in a Bus Error, other times a Segmentation Fault, but always "incorrect
checksum for freed object".
This started when I migrated to 0.9.4 from 0.3.2
Thoughts?
Thanks,
Shad
----
ruby(1895,0xa000ed98) malloc: *** error for object 0x266b1f0: incorrect
checksum for freed object - object was probably modified after being freed,
break at szone_error to debug
ruby(1...
2008 Feb 19
3
Incorrect paste() output (PR#10801)
Hello,
I am writing this message because of an incorrect output by paste().
Please try the following script to see if the evidence I collected is
reproducible:
x <- c(10152, 28177);
y <- c(9576, 26625);
d <- y - x;
d;
[1] -576 -1552
paste(d, collapse = ", ");
[1] "-576, -1552"
x <- x / 1000;
y <- y / 1000;
d <...
2002 Jun 12
3
Repost : Incorrect Reporting of Drive Space from the Windows 2000 Explorer on SAMBA shares
...> -----Original Message-----
>
> Hi,
>
> In Windows 2000 I have noticed that when you connect to a SAMBA share and
> use the Windows 2000 explorer, the properties for the drive shows the free
> space as the maximum capacity of the drive and that the used space is 0.
> This incorrect reporting of the drive space is always the same, no matter
> how full the disk of the SAMBA share is.
>
> Has anyone seen this before. Anyone have any ideas if there is a work
> around.
>
> The SAMBA servers I tested with are running SAMBA 2.2.3a on HP-UX 11.00
>
>
>...
2006 Jan 28
1
Can''t freeze rails on a windows box
Hi,
I''m trying to freeze rails on a windows box and get this message(test is
an rails app):
C:\rails\test>rake freeze_gems
(in C:/rails/test)
Freezing to the gems for Rails 1.0.0
rm -rf vendor/rails
mkdir -p vendor/rails
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The system cannot find the pat...