Displaying 20 results from an estimated 1000 matches similar to: "Is it okay?"
2011 Jan 16
9
Troubles for an non-IT beginner
hello,
I am absolutely new, means from non-IT sector but have attraction (developed
recently) towards linux and have chosen the centos distro  for the
installation as an OS in my home PC for personal use. I went to the page:
http://isoredirect.centos.org/centos/5/isos/i386/
But don't understand amongst the variety of options there. I also don't know
the technical terms like md5,
2011 Jan 15
1
Installation question
Hi,
I am new in the world of CentOS and Linux. I am not a computer professional
but want to do work in Linux, for which I am trying to learn the Linux
basics. Having a PC at home and somebody told me CentOS is a great Linux
distro for stability.
I am having some basic queries which are as follows:
1. I am having the PC and already installed is Fedora Core 11 as well as
Windows XP (dual boot).
2005 Jul 04
1
compare two lists with differents levels
Hi,
I would like to compare 2 lists resulted from a sql query! bu there are different levels, so when I want to do:
 
release1<-sqlQuery(channel,paste("select distinct c.ID,c.Title TitleCrit from category cat, category_criteria cc, criteria c, question_criteria qc, question q, form_question fq, form f, release_form rf, release r, product_release pr, product p where cat.ID=cc.category and
2010 Feb 12
2
[LLVMdev] Reminder: 2.7 code freeze in 1.5 weeks
Just a reminder that the 2.7 code freeze is on Feb 21st. 
All major changes should be committed approximately 1 week before the code freeze to ensure adequate testing. Please do your part to keep the tree stable in the days leading up to the code freeze.
Thanks!
-Tanya
2/21 - Code Freeze (9PM PST)
2/27 - Pre-release1 released & community testing begins
3/6   - Pre-release1 testing ends
3/13
2010 Feb 15
0
[LLVMdev] [cfe-dev] Reminder: 2.7 code freeze in 1.5 weeks
On Feb 12, 2010, at 3:02 PM, Douglas Gregor wrote:
> 
> On Feb 12, 2010, at 8:25 AM, David Greene wrote:
> 
>> On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote:
>>> Just a reminder that the 2.7 code freeze is on Feb 21st.
>>> 
>>> All major changes should be committed approximately 1 week before the code
>>> freeze to ensure adequate
2010 Apr 20
1
[LLVMdev] 2.7 Pre-Release2 Available!
The 2.7 pre-release2 is available for testing:
http://llvm.org/pre-releases/2.7/pre-release2/
Please complete all testing by April 23rd EOD. We are shortening this testing period a bit to get the release out soon since its been delayed so far. The release team has done our qualifications and we think its of high quality and ready to go.
As this is the last pre-release, we only accept fixes for
2010 Feb 13
1
[LLVMdev] [cfe-dev] Reminder: 2.7 code freeze in 1.5 weeks
I am definitely in favor of this if it is ok with Tanya.
I hope to spend some time in the next few weeks on tracking down
miscompiles, and it would be great to get Clang to the
"early-but-usable-beta" stage so it makes sense to roll binaries for
2.7.
Tanya, I can also do the x86-32-pc-linux release testing if no one
else steps up.
 - Daniel
On Fri, Feb 12, 2010 at 3:02 PM, Douglas
2010 Feb 12
8
[LLVMdev] Reminder: 2.7 code freeze in 1.5 weeks
On Feb 12, 2010, at 8:25 AM, David Greene wrote:
> On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote:
>> Just a reminder that the 2.7 code freeze is on Feb 21st.
>> 
>> All major changes should be committed approximately 1 week before the code
>> freeze to ensure adequate testing. Please do your part to keep the tree
>> stable in the days leading up to the
2009 Feb 20
7
[LLVMdev] 2.5 Pre-release2 available for testing
LLVMers,
The 2.5 pre-release2 is finally available for testing:
http://llvm.org/prereleases/2.5/
If you have time, I'd appreciate anyone who can help test the release.  
Please do the following:
1) Download/compile llvm source, and either compile llvm-gcc source or  
use llvm-gcc binary (please compile llvm-gcc with fortran if you can).
2) Run make check, send me the testrun.log
3) Run
2009 Feb 24
0
[LLVMdev] 2.5 Pre-release2 available for testing
On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote:
> LLVMers,
>
> The 2.5 pre-release2 is finally available for testing:
> http://llvm.org/prereleases/2.5/
>
> If you have time, I'd appreciate anyone who can help test the release.
> Please do the following:
>
> 1) Download/compile llvm source, and either compile llvm-gcc source or use
2010 Feb 13
0
[LLVMdev] [cfe-dev] Reminder: 2.7 code freeze in 1.5 weeks
On Fri, Feb 12, 2010 at 5:48 PM, Daniel Dunbar <daniel at zuster.org> wrote:
> I am definitely in favor of this if it is ok with Tanya.
>
> I hope to spend some time in the next few weeks on tracking down
> miscompiles, and it would be great to get Clang to the
> "early-but-usable-beta" stage so it makes sense to roll binaries for
> 2.7.
>
> Tanya, I can
2009 Oct 21
2
[LLVMdev] 2.6 pre-release2 testing ends today
Just a reminder that today is the last day for pre-release2 testing.
Thanks,
Tanya
2010 Aug 04
3
[LLVMdev] Announcing: LLVM 2.8 Release Schedule
Good news, everybody!
It's that time of year again. We are going to release LLVM 2.8! I'm taking over for Tanya to give her a much needed break. I can only hope to perform as well as she has. This is my first time as release manager, so bear with me if things don't go smoothly.
This message is mostly to give you an idea of the schedule we're planning on. It's an aggressive
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
> 2.6 pre-release2 is ready to be tested by the community.
Excellent! Would you care to update the "LLVM 2.6 release schedule" on
the front page of the web site?
Thanks,
Jay.
2009 Feb 21
0
[LLVMdev] 2.5 Pre-release2 available for testing
On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote:
>  LLVMers,
>
> The 2.5 pre-release2 is finally available for testing:
> http://llvm.org/prereleases/2.5/
>
> If you have time, I'd appreciate anyone who can help test the release.
> Please do the following:
>
> 1) Download/compile llvm source, and either compile llvm-gcc source or
2009 Oct 21
0
[LLVMdev] 2.6 pre-release2 ready for testing
Is there are chance to get http://llvm.org/bugs/show_bug.cgi?id=5081 fixed in 
2.6? The affected application did compile with with LLVM 2.5. I haven't yet 
checked whether TOT fixed this already, however, but will do this if necessary.
Thanks,
Torvald
On Saturday 17 October 2009 20:51:05 Tanya Lattner wrote:
> LLVMers,
> 
> 2.6 pre-release2 is ready to be tested by the community.
2009 Feb 22
2
[LLVMdev] 2.5 Pre-release2 available for testing
On Sat, Feb 21, 2009 at 9:54 PM, Aaron Gray <aaronngray.lists at googlemail.com
> wrote:
>  On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote:
>
>>  LLVMers,
>>
>> The 2.5 pre-release2 is finally available for testing:
>> http://llvm.org/prereleases/2.5/
>>
>> If you have time, I'd appreciate anyone who can help
2009 Oct 18
0
[LLVMdev] 2.6 pre-release2 ready for testing
Hi Tanya,
glad to see that 2.6 release is coming. :)
After doing some testing with valgrind on this release, I have find a little
"undefined memory" error in DefaultJITMemoryManager related to the
PoisonMemory field.
This bug has been corrected in trunk with revision r80192.
Attached is a patch which cleanly apply same correction on the release-2.6
branch.
Thanks,
Olivier.
On Sat,
2009 Oct 22
0
[LLVMdev] 2.6 pre-release2 testing ends today
On Oct 21, 2009, at 3:44 PM, Tanya Lattner wrote:
> Just a reminder that today is the last day for pre-release2 testing.
>
Hi Tanya,
Attached are the log files for Mac OS X 10.5.8 on PowerPC. There are  
these failures for clang:
********************
Failing Tests (20):
         /Volumes/SandBox/2.6/llvm-2.6/tools/clang/test/CodeGen/ 
always_inline.c
        
2009 Aug 31
10
[LLVMdev] 2.6 pre-release1 ready for testing
LLVMers,
2.6 pre-release1 is ready to be tested by the community.
http://llvm.org/prereleases/2.6/
You will notice that we have quite a few pre-compiled binaries (of  
both clang and llvm-gcc). We have identified several bugs that will be  
fixed in pre-release2, so please search the bug database before filing  
a new bug.
If you have time, I'd appreciate anyone who can help test the