Displaying 20 results from an estimated 756 matches for "bitten".
Did you mean:
bitte
2005 Aug 23
0
Fixtures: pluraly bitten
With my functional tests (on PgSQL) I get strange errors like this
1) Error:
test_create(AufgabeControllerTest):
ActiveRecord::StatementInvalid: ERROR: duplicate key violates unique
constraint "aufgaben_pkey"
Tracking this down, I found that sequences are only reset for some of
the tables I''m using. The reason? Inconsistent singularization.
I won''t go so far as
2008 Mar 20
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner:
> Its not just a matter of checking major/minor versions. It also depends on
> the target and in some cases the OS.
> http://llvm.org/docs/GettingStarted.html#brokengcc
>
> So for example, GCC 3.3.3 on Suse or GCC 3.4.0 on linux/x86
> (32-bit) has issues. Is it easy to check these kinds of things?
uname
2008 Mar 21
1
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Joachim Durchholz wrote:
> Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner:
>
>> Its not just a matter of checking major/minor versions. It also depends on
>> the target and in some cases the OS.
>> http://llvm.org/docs/GettingStarted.html#brokengcc
>>
>> So for example, GCC 3.3.3 on Suse or GCC 3.4.0 on linux/x86
>> (32-bit) has
2008 Mar 21
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
> I guess it could be done for things like 4.1.1 or a couple of others on
> the list.
This gcc version always worked fine for me on ubuntu linux (though it
might have been 4.1.2, I don't recall).
Ciao,
Duncan.
2008 Mar 21
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Freitag, den 21.03.2008, 13:03 +0100 schrieb Duncan Sands:
> Hi Joachim,
>
> > I have to report that the Ubuntu gcc-4.1 will fail. 'make' would run
> > without giving more than a few warnings, but 'make install' will
> > complain that it doesn't know how to build one of the intermediate
> > targets and error out (some VMCore/tablegen file IIRC,
2008 Mar 20
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Donnerstag, den 20.03.2008, 15:27 -0700 schrieb Shantonu Sen:
> llvm's ./configure already does that for gcc < 3.
>
> What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2?
There's a list at http://llvm.org/docs/GettingStarted.html#brokengcc so
there is a reasonable basis.
The list isn't comprehensive, of course, and will likely grow in the
future. OTOH
2008 Mar 20
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
On Mar 20, 2008, at 3:00 PM, Joachim Durchholz wrote:
> Hi all,
>
> I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the
> (broken-for-LLVM) gcc-4.1 as a compiler.
> The error message that I got was this:
> make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore'
> make[1]: *** No rule to make target
> `/home/jo/llvm-wrk/Release/bin/tblgen',
2004 Apr 15
7
all(logical(0)) and any(logical(0))
Dear R-help,
I was bitten by the behavior of all() when given logical(0): It is TRUE!
(And any(logical(0)) is FALSE.) Wouldn't it be better to return logical(0)
in both cases?
The problem surfaced because some un-named individual called randomForest(x,
y, xtest, ytest,...), and gave y as a two-level factor, but ytest...
2008 Mar 20
4
[LLVMdev] Just got bitten by accidentally using the wrong gcc
>> I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the
>> (broken-for-LLVM) gcc-4.1 as a compiler.
>> The error message that I got was this:
>> make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore'
>> make[1]: *** No rule to make target
>> `/home/jo/llvm-wrk/Release/bin/tblgen', needed by
>>
2008 Mar 20
3
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Hi all,
I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the
(broken-for-LLVM) gcc-4.1 as a compiler.
The error message that I got was this:
make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore'
make[1]: *** No rule to make target
`/home/jo/llvm-wrk/Release/bin/tblgen', needed by
`/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop.
2008 Mar 20
3
[LLVMdev] Just got bitten by accidentally using the wrong gcc
llvm's ./configure already does that for gcc < 3.
What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2?
dnl Verify that GCC is version 3.0 or higher
if test "$GCC" = "yes"
then
AC_COMPILE_IFELSE([[#if !defined(__GNUC__) || __GNUC__ < 3
#error Unsupported GCC version
#endif
]], [], [AC_MSG_ERROR([gcc 3.x required, but you have a lower
version])])
fi
2006 Apr 11
3
fun/flamebait: Java Web Devel Stacks
...to survive the pain of the day job. It''s
for the professional J2EE developer converts out there.
Let''s say someone hired you to write a Basecamp clone, but it has to
be done in Java, say on the Tomcat or JBoss platform. What does your
stack look like now that you''ve been bitten by the Ruby/Rails
rhetoric?
Cheers,
Ed
2013 Apr 17
3
[LLVMdev] make check rebuilds the project?
Because almost no other piece of software out there doesn't have
'check' depend on rebuilding the target it's testing and it's bitten
people whereas other than the lameness of our build system needing to
recurse all the directories to figure out that all has already been
rebuilt there's no penalty to requiring the dependency. :)
-eric
On Wed, Apr 17, 2013 at 9:35 AM, Bob Wilson <bob.wilson at apple.com> wrote:
> Er...
2006 Mar 17
1
[RFC] mke2fs with DIR_INDEX, RESIZE_INODE by default
I've been thinking recently that we should re-enable DIR_INDEX in mke2fs
by default. When it first came out, we had done this and were bitten by
a few bugs in the code. However, this code has been in heavy use for
several thousand filesystem years in Lustre, if not elsewhere, and I'm
inclined to think it is pretty safe these days.
Likewise, RHEL/FC have had RESIZE_INODE as a standard feature for a good
time now, and this should pro...
2008 Mar 21
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Freitag, den 21.03.2008, 06:56 -0700 schrieb Shantonu Sen:
> I recommend you don't parse version strings. In fact I switch the
> check to use AC_COMPILE precisely for the reason that gcc --version is
> totally unreliable and vendor specific. For example, what's the
> regular expression that tells you what the GCC version is:
> i686-apple-darwin9-gcc-4.0.1 (GCC)
2005 Jun 02
2
Caution on the use of model.matrix.
I have just been bitten by a quirk in the behaviour of model.matrix.
I used model.matrix inside a function, and passed to it a formula
that was built elsewhere.
The formula was of the form ``y ~ x + w + z''. Now, model.matrix
cheerfully accepts formulae of this form, although it only
***needs*** the right hand s...
2012 Jun 04
2
[LLVMdev] Big endian ARM?
...sign is that the frontend (if it attaches a TD string)
>> is *required* to match the code generator:
>> http://llvm.org/docs/LangRef.html#datalayout
>
> Chris,
>
> Do we actually verify this anywhere?
No. This has been on my todo list for a long time - people regularly get bitten
by it.
Ciao, Duncan.
2010 Jun 09
2
is the xenconsoled crash solved?
One of our machines are being bitten by that bug, once every 2-4 weeks or so xenconsoled dies and all the VMs stop responding intil xenconsoled is restarted.
I googled for it and I saw many people reporting it but no solution for it.
Does anyone know if it is solved in 5.5? I can't upgrade the box (it's a production box) unl...
2009 Nov 17
2
Workaround for RH #502499?
I have a workstation with a Gigbyte board and an Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) that's apparently getting bitten by https://bugzilla.redhat.com/show_bug.cgi?id=502499
It's running CentOS 5.4 32 bit, and the user is suffering from high load and sluggish response whenever a disk write of more than a few MB is made. iostat shows the disk at 100%.
[root at marge ~]# uname -a
Linux marge.gizmopartners.com 2...
2008 Mar 21
3
[LLVMdev] Just got bitten by accidentally using the wrong gcc
I recommend you don't parse version strings. In fact I switch the
check to use AC_COMPILE precisely for the reason that gcc --version is
totally unreliable and vendor specific. For example, what's the
regular expression that tells you what the GCC version is:
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5470)
(Aspen 5470.3)
Per the rest of this thread, you can't