search for: ships

To accompany the Payment library (http://payment.rufy.com/), I have created the shipping library that connects APIs for various shippers like UPS and FedEx. It is available as a ruby gem: gem install shipping or from rubyforge http://rubyforge.org/projects/shipping There is going to be some data that will persist for all shipments. For example, you will not want to repeat the fedex account

The build for the Android sanitizers is unique in that it needs to link against the Android system libraries to create a shared object and its test suites. The current solution to build ASan is to drop the compiler-rt repo into the llvm source tree and cross-compile the llvm build for Android. This is a bit awkward for few reasons: 1) Not all of llvm can be cross-compiled for Android.

I am trying to use the shipping gem shipping.rubyforge.org, but I cant get it to work on my windows development box at all. Problem anytime I try to do anything I get: ArgumentError: couldn''t find HOME environment -- expanding `~/.shipping.yml'' from c:/ruby/lib/ruby/gems/1.8/gems/shipping-1.3.0/lib/shipping/base.rb:25:in `expand_path'' from

Hi, The llvm-gcc binaries I downloaded for the 2.7 prerelease contained a .la for libstdc++, and a .a file, but no .so file: /home/edwin/llvm2.7/llvm-gcc-4.2-2.7-x86_64-linux/lib64/libstdc++.la /home/edwin/llvm2.7/llvm-gcc-4.2-2.7-x86_64-linux/lib64/libstdc++.a While testing libtool's new LTO support [1] everything broke when it tried to use that .la file, with millions of messages like

Hello, Edwin > I think its a mistake in the binary package: the .la and .a shouldn't be > shipped, and the .so should be built & shipped! This means that llvm-gcc was compiled in static mode (same problem, btw, is seen with debian packages - llvm-gcc they ship is pretty useless due to this). One should configure llvm-gcc w/o --disable-shared. And yes, both .so and .a should be

greetings, has anyone had luck with the UPS portion of the shipping gem? i get nil''s returned for price, wondering what i''m missing. to avoid all confusion i included the account/login in the instantiation (sub with real values). @ups = Shipping::UPS.new :ups_account => ''7B4F74E3075AEEFF'', :ups_user => ''username'', :ups_password

Hi LLVM’ers! We are hosting a BoF at this year's Dev Meeting on a subject we hope will be of interest to some (many?) of you: shipping software (entirely) as LLVM IR. You can find our proposal in the meeting schedule online: https://llvmdevelopersmeetingbay2016.sched.org/event/8Yzq/shipping-software-as-llvm-ir The BoF is scheduled to last 45 minutes, which will go by very quickly! To make

I have a general question regarding smb.conf and I was hoping that some of the rather more knowledgeable and experienced people here could please comment please? I am currently setting my various SAMBA systems up via some shell-scripts. Within these scripts, I remove the stock smb.conf shipped with Samba and replace this with an empty smb.conf file to which I add my own configuration options

...hipping. In most cases, there is only one ship in the study area at one time. Ship length, distance from the animals, speed, angle from animals, and ship direction (as east/west bound) are among shipping-related covariates (with multiple interactions). The tricky part is that sometimes there are 2 ships in the area. I could add all the same covariates, but doubled-up for the second ship. However, this really hurts convergence. And - conceptually - why would ship length affect the animals differently between ship 1 and ship 2? I would think that animals would react similarly to both ships (and the...

> Alexey's approach with CMake sub-projects. I prefer that direction as well, but what I've proposed is a solution that works today. To support cross-compilation, we'll need to loop over each supported arch (llvm-config --targets-built), then loop over each supported triple for each arch (hard-coded map?), and then pair up each triple with a sysroot (system paths provided by the

Hi Mehdi, Yes, we did see your earlier post. Efficient (de)serialization is definitely important for both exporting (a la LTO and ThinLTO) and for shipping code as IR. I expect most use cases of the latter would benefit. -—Vikram // Vikram S. Adve // Professor, Department of Computer Science // University of Illinois at Urbana-Champaign // vadve at illinois.edu<mailto:vadve at

Hi I am late to the party. Here is my personal take of the topic: * Do you ship software as IR today? What lessons have you learned? Yes. We accept AppStore submission in bitcode (LLVM IR). The core function in clang is upstreamed and you can look up the related code path triggered by -fembed-bitcode option. * Challenges of shipping software as IR Compatibility: We are trying to enhance the

Hi Vikram, It is a bit more that just “efficient (de)serialization” as there is some amount of tradeoff to make between “size” vs “speed” vs “flexibility” (which are all some sort of “efficient”). For instance what if we get a faster deserialization but got larger size? That might be an issue for some people who’d like to ship bitcode. Another thing is that we may get better speed/size by

Some people on this group may have understood from messages posted here that the Sipura SPA-2000 is not currently available for shipping. That is not the case. Voxilla.com has the Sipura SPA-2000 available for immediate shipping, and has had them since late November. The price is $109.95, and it comes with a month of free VoicePulse service with activation fees waived (a $65 value). In return

I tried calling their toll free number and toll number last week in the morning and afternoon and was handed a recording saying this number is no longer in service. The web site was up but there was no message on the site as to why the phone numbers were not working. I just called the number now and it is working. Being around the internet for a quite a long time this gives me an uneasy

> Note that ASan tests on Android require llvm-symbolizer binary. That's a really good point. And I see that llvm-symbolizer can't just be pulled into compiler-rt because it has dependencies on DebugInfo, Object, and Support libraries. This throws a big wrench in Alexey's plan to have the native compiler-rt build generate the cross-compiled binaries for all supported targets. We

Russell Wallace wrote: > One issue I've been looking at with regard to using LLVM as a compiler > backend is distribution of programs, particularly on Linux where > different distributions have different binary package formats and it > is usual to ship programs as source rather than binary; specifically, > I'm looking at the general case where the end user may not have (the

I noticed we ship the <debian> folder with at least these libraries: libogg-1.1.3 vorbis-tools-1.2.0 By doing this we take the packaging code out of the Debian diffs where some people might be expecting it. Is this a problem? What benefits do you see in shipping it? Greetings, Sebastian

One issue I've been looking at with regard to using LLVM as a compiler backend is distribution of programs, particularly on Linux where different distributions have different binary package formats and it is usual to ship programs as source rather than binary; specifically, I'm looking at the general case where the end user may not have (the correct version of) LLVM installed, so the

Has anyone been able to get a UPS shipping calculator implemented into their site with Rails? It seems the only options they show on their site both use UPS''s own page displayed either standalone or within your own header and footer, but no straight API with a callback or anything. Can anyone point me in the right direction? -- Posted via http://www.ruby-forum.com/.