Displaying 20 results from an estimated 400 matches similar to: "update_attributes"
2011 Dec 13
1
[LLVMdev] [PATCH] utils/unittest: Consistency of gtest and gtest_main libs.
$(llvm-config --libs | tr " " "\n" | grep gtest) returns:
-lgtest_main
-lgtest
instead of non-valid:
-lLLVMgtest_main
-lLLVMgtest
It also fixes:
$(ld): cannot find -lLLVMgtest
$(ld): cannot find -lLLVMgtest_main
---
unittests/Makefile.unittest | 2 +-
utils/llvm-build/llvmbuild/componentinfo.py | 4 ++--
utils/llvm-build/llvmbuild/main.py |
2010 Sep 09
3
1.9.2 why does relative_require need an additional backtrack in path
Why does Ruby-1.9.2-p0 require an additional ../ for relative paths
when compared to the same code for ruby1.8?
if RUBY_VERSION < ''1.9''
require File.dirname(__FILE__) + library
else
require_relative File.dirname(__FILE__) + ''/..'' + library
end
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core"
2020 May 21
5
Understanding the version handling in LLVM/Clang/LLD
[ Please CC me I ma not subcribed to this mailing-list ]
[ CC Tom and Hans as LLVM/stable maintainers ]
Hi,
I want to understand the version handling in LLVM/Clang/LLD.
Normally, I build from "release/10.x" Git branch by using the tool
tc-build from ClangBuiltLinux project.
With "llvm-10.0.1-rc1" Git tag I was able to setup a llvm-toolchain
consisting of the projects
2020 May 20
3
10.0.1-rc1 release has been tagged
On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote:
>
> On 05/19/2020 09:05 PM, Sedat Dilek wrote:
> > Hi Tom,
> >
> > thanks and congrats for LLVM 10.0.1-rc1 release.
> >
> > [1] shows 2 assets.
> > 10.0.0 RCs had a lot of more assets.
> > I am missing the llvm-project-10.0.1rc1.tar.xz tarball.
> >
> > Will
2020 May 21
2
10.0.1-rc1 release has been tagged
On Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote:
>
> On 05/20/2020 09:53 AM, Sedat Dilek wrote:
> > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote:
> >>
> >> On 05/19/2020 09:05 PM, Sedat Dilek wrote:
> >>> Hi Tom,
> >>>
> >>> thanks and congrats for LLVM
2020 May 20
3
10.0.1-rc1 release has been tagged
Hi Tom,
thanks and congrats for LLVM 10.0.1-rc1 release.
[1] shows 2 assets.
10.0.0 RCs had a lot of more assets.
I am missing the llvm-project-10.0.1rc1.tar.xz tarball.
Will you provide them later or is there a new development/workflow
decision I do not know of?
BTW, the source zip and tar.gz tarballs show no sizes.
I am using Mobile LTE/UMTS to download stuff from the Internet.
For now I
2006 Sep 01
2
[LLVMdev] gfortran: patch, question
Hi, I have a first quick patch and a question. The patch links f951
with g++ when LLVM is enabled. It's at the end of this email.
I wanted to know if I should submit patches with comments around them
like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to
the tree. I'd like to make it as easy as possible to apply these, so
let me know any rules I should be following.
2006 Sep 01
0
[LLVMdev] gfortran: patch, question
On Fri, 1 Sep 2006, Michael McCracken wrote:
> Hi, I have a first quick patch and a question. The patch links f951
> with g++ when LLVM is enabled. It's at the end of this email.
Thanks, applied!
> I wanted to know if I should submit patches with comments around them
> like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to
> the tree. I'd like to
2006 Sep 01
3
[LLVMdev] gfortran: patch, question
On 9/1/06, Chris Lattner <sabre at nondot.org> wrote:
> On Fri, 1 Sep 2006, Michael McCracken wrote:
> > I wanted to know if I should submit patches with comments around them
> > like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to
> > the tree. I'd like to make it as easy as possible to apply these, so
> > let me know any rules I
2005 Jan 14
6
[LLVMdev] Proposed Makefile Changes
Hi,
In buildling XPS using LLVM's makefile system, I'm finding that there's
a few things lacking in our support for LLVM-based projects. The items
below should help but may require changes to project makefiles. I
thought I'd check before just going and doing it.
1. Various autoconf generated variables (e.g. abs_top_srcdir) are
set in the makefiles but not used. They
2013 Feb 27
1
[LLVMdev] Compilation problem when addind a library
Hi !
Here is the situation. I created a pass in lib/Transforms/Obfuscation. I added a createFlattening() in IPO.h and in my code
to be able to use it in PassManagerBuilder.cpp (lib/Transforms/IPO) in the method PopulateModulePassManager() so I can add my pass to standard passes.
It all works if I add all my files in the lib/Transforms/IPO directory.
But I want to keep them away in the
2006 May 22
2
good practice or waste of time?
I have what I hope is a simple question regarding a security practice
I''ve been using in my first Rails app. I want to know if it''s
worthwhile or if the extra typing isn''t worth it.
I have 3 models that are related to each other.
class User < AR:Base
has_one :library
end
class Library < AR:Base
belongs_to :user
has_many :items
end
class Item < AR:Base
2005 Jan 16
0
[LLVMdev] Proposed Makefile Changes
The proposed makefile changes have been committed. If you are working
from CVS head and you use the LLVM Makefile System in your own project,
please make a note of the following:
1. If your makefiles use any BUILD_* variables, they now need to be
prefixed with PROJ_ instead of BUILD_. For example,
BUILD_SRC_ROOT is now PROJ_SRC_ROOT.
2. There are additional requirements
2005 Jan 16
0
[LLVMdev] Proposed Makefile Changes
The proposed makefile changes have been committed. If you are working
from CVS head and you use the LLVM Makefile System in your own project,
please make a note of the following:
1. If your makefiles use any BUILD_* variables, they now need to be
prefixed with PROJ_ instead of BUILD_. For example,
BUILD_SRC_ROOT is now PROJ_SRC_ROOT.
2. There are additional requirements for projects.
2005 Jan 16
1
[LLVMdev] Proposed Makefile Changes
The llvm.cs.uiuc.edu site does not seem to be updating at the moment so
it contains the old instructions. If you're looking for the new
instructions on the Projects.html page, you can view them here:
http://illuvium.net/docs/Projects.html
Reid.
On Sat, 2005-01-15 at 18:30, Reid Spencer wrote:
> The proposed makefile changes have been committed. If you are working
> from CVS head and
2006 Jan 04
0
update_attribute works, update_attributes doesn''t, why?
Hello again...
so I narrowed my problem down. For some reason, while using
login_generator, any User object I pull from the DB can be updated one
attribute at a time using update_attribute, but when I try and do
update_attributes it fails every time. Is this a limitation with
login_generator that I don''t know about, or is there a way around this?
I also tried the .update method and
2006 Jul 11
3
update_attributes and save!
I notice that ActiveRecord::Base.update_attributes() calls save().
What if I want to get an exception if the save fails? Is there a way to
get the update_attributes() function plus the save! function?
Thanks,
Wes
--
Posted via http://www.ruby-forum.com/.
2006 Jun 26
0
Update_attributes working, or not? I can''t tell.
I have a basic login system implemented. I''ve recently added a
timestamp field "last_activity_time". During the login process, if I
successfully get back a user object, I do this:
user.update_attribute(:last_activity_time, Time.now())
It appears to be successful given the breadcrumbs I''ve strewn around it,
but nothing gets written out to my table. In
2006 Jun 27
1
user.save now workie, but user.update_attributes does
In my User model, I had this:
def update_last_login_time
self.last_login = Time.now
self.save
end
But last_login was not being set.
When I changed it to this it worked:
self.update_attribute( :last_login, Time.now )
Any ideas why?
~S
2006 Apr 21
0
collection_select has_and_belongs_to_many update_attributes
I know there have been threads on this before but I was thinking
shouldn''t multiple collection_select automatically update habtm
relations when you update_attributes?
In order to get multiple collection_select to work I use:
collection_select(:user, :group_ids, Group.find(:all), :id,
:name,{},{:multiple=>'''',:name=>''group[id][]''})
In fact if I