search for: specifics

I run the command $gem update --system after all time while installing gems and even $rails -v command also giving below error Invalid gemspec in [/usr/local/lib/ruby/gems/1.9.1/specifications/ json-1.6.1.gemspec]: invalid date format in specification: "2011-09-18 00:00:00.000000000Z" Invalid gemspec in [/usr/local/lib/ruby/gems/1.9.1/specifications/ json-1.6.0.gemspec]: invalid

Thoughts? [root@ca-sna-pm01 config]# rake RAILS_ENV=production db:migrate (in /usr/share/puppet-dashboard) NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no

...troduced to add flexibility to existing structures in attempt to keep their size and offsets constant and not dependent on features. While this is not a complete specification, it describes all the main structures and should be enough to make sure the idea is solid before going into implementation specifics. A new virtio-pci capability structure will be introduced. This structure will be used to describe the basics of a virtio-pci device. The structure is actually a PCI capability structure which wraps the new virtio-pci capability structure: +------------++------------+------------+------------+---...

...troduced to add flexibility to existing structures in attempt to keep their size and offsets constant and not dependent on features. While this is not a complete specification, it describes all the main structures and should be enough to make sure the idea is solid before going into implementation specifics. A new virtio-pci capability structure will be introduced. This structure will be used to describe the basics of a virtio-pci device. The structure is actually a PCI capability structure which wraps the new virtio-pci capability structure: +------------++------------+------------+------------+---...

Hi, Is there a way to tell / narrow down if an issue with errors like below are due to a bad cable or bad port multiplier ? The disks in a particular cage are throwing errors like these below. (RELENG9 from today) siis0 at pci0:5:0:0: class=0x010400 card=0x71241095 chip=0x31241095 rev=0x02 hdr=0x00 vendor = 'Silicon Image, Inc.' device = 'SiI 3124 PCI-X Serial

On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz" <boaz.ouriel at intel.com> wrote: > **** Introduction **** > Lately, Khronos has ratified a new provisional specification which is called SPIR. > This specification standardizes an intermediate representation for the OpenCL kernel language. > It is based on LLVM infrastructure and this is why I am sending this mail to the

Hello all, I am quite new to the puppet arena, but I am really impressed with puppet as a tool and the possibilities it gives you with regards to managing many systems. I am running dashboard 1.2.14 and am trying to query via the rake API: http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html when I do, I get the following error: <snip> # sudo -u puppet-dashboard rake -f

Hi All, In continuation of the previous SPIR introduction email here is a link to the specification: http://www.khronos.org/registry/cl/specs/spir_spec-1.0-provisional.pdf The first topic which we would like to discuss is "SPIR portability". I will send soon an additional mail which will help in leading the discussion on this topic. Thanks and happy reading, Boaz -----Original

Hi, I''m trying to install dashboard on precise and I get the below error. I''m using the latest version that is available in the puppet apt repository. The package rdoc is installed (it''s just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn''t specify? I don''t know ruby that well so finding it hard

Greetings All, I am sending this mail on behalf of the OpenCL Khronos members. **** Introduction **** Lately, Khronos has ratified a new provisional specification which is called SPIR. This specification standardizes an intermediate representation for the OpenCL kernel language. It is based on LLVM infrastructure and this is why I am sending this mail to the LLVM mailing list. Khronos members

There are a few places in llvm's generic codegen that refer to target specific intrinsics. This is bad layering and we shouldn't do it. It also means that if we don't build a target we still have to support all of it's intrinsics and other such annoyances. The main violator of this is InstCombineCalls - I'd like to push this into the targets, and just have a case that says

Hi Boaz, I have a couple of specific questions: (a) You mention special calling conventions and adding them to LLVM. What are their semantics? And what is their purpose? (b) Why disallow type conversion for vector types? (ss. 3.3) Cheers, James On Tue, 2012-09-11 at 12:56 +0100, Ouriel, Boaz wrote: > Hi All, > > In continuation of the previous SPIR introduction email here is a link

Hi all, In my controller I am doing the following to populate a nested form for a has_many through association: def new @specification = Specification.new Component.find_each.each do |component| @specification.component_specifications.build(:component_id => component.id) end The idea being whenever someone creates or edits a form, it will be populated with all

Hi, I have samba as a PDC and I need to deny login for a specific user in a specific machine. How can I achieve that? -- Rodrigo Abrantes Antunes Instituto Federal Sul-rio-grandense

Where can I get E1 and/or Euro-ISDN specifications/data sheets? Are there specs for other E./G./Q./etc. protocols as well? Thanks!

Hi all, I DONT KNOW WHAT IS THIS WHEN I RUN SERVER OR CONSOLE ITS COMMING. PLEASE ANYBODY TELME WHATS PROBLEM WHATS SOLLUTION rajesh@rajesh:~/workspace/apl$ ruby script/console Loading development environment (Rails 2.3.2) NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of James Molloy > Sent: Tuesday, September 11, 2012 8:49 AM > To: Ouriel, Boaz > Cc: cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] SPIR provisional specifciation is now available > in the Khronos website > > Hi Boaz, >

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Vikram Adve > Sent: Thursday, September 06, 2012 3:52 PM > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] "SPIR" ? A Standard Portable IR for OpenCL > Kernel Language > > On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz"

According to the "LLVM Assembly Language Reference Manual": When constructing the data layout for a given target, LLVM starts with a default set of specifications which are then (possibly) overriden by the specifications in the datalayout keyword. The default specifications are given in this list: * E - big endian * p:32:64:64 - 32-bit pointers with 64-bit alignment Are these

Hello, this is my first communication to any freedesktop list in a long time. I've noticed some problems with some links on the wiki, on some pages related to Specifications. Consider these two example pages: https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/ https://www.freedesktop.org/wiki/Specifications/xembed-spec/ Both pages have one or more links to "html (one