search for: obsolescence

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

...to the 3.3 series. Does the closing comment in https://bugzilla.samba.org/show_bug.cgi?id=5535 mean that the inconsistencies about RID calculation won't be addressed in the 3.0 and 3.2 series? Does the fact that 3.3.2 always uses sambaNextRid mean that algorithmic RID allocation is doomed to obsolescence? Regards, Thierry

...1.5 Storage-class specifiers > > The placement of a storage-class specifier other than at the beginning > of the declaration specifiers in a declaration is an obsolescent > feature. The attached patch (against SVN revision 72220) is a suggestion of how to eliminate the sources of such obsolescence warnings from the R source tree, including the example in the R-exts manual. The patch was originally made for r72218, and against that version it was tested successfully on Ubuntu 14.04.5 LTS (gcc 4.8.4) and OS X 10.7.5 (gcc 6.3.0 installed from Homebrew). Revision 72220 failing 'make chec...

Full_Name: Steven L. Scott Version: 2.2.1 OS: Windows-Cygwin Submission from: (NULL) (128.125.60.50) I've had problems unpacking the R source coded downloaded from http://lib.stat.cmu.edu/R/CRAN/src/base/R-2/R-2.2.1.tar.gz Version info for tar and gunzip provided below (GNU legalese edited out), along with the error messages I get. Thanks. Steve /notcygwin[506] gunzip --version gunzip

There appear to be three acts_as_taggable implementations and I''m looking for a recommendation on which to use. - Gem - DHH plugin - Dema mixin The Gem implementation appears to be obsolescent, from what I can read on the lists and Google search. I like that the DHH plugin uses polymorphic associations because there will be lots of different taggable items in my application; however,

On 03/11/03 00:25, Mark Spencer wrote: > As a side note, I strongly would like to see someone implement a > client using libiax2 which implements IAX2 instead of the (now > obsolescent) IAX version 1. I'm implementing a Java-based IVR server (and yes, I know Asterisk does IVR, and no, it's not flexible enough to do what I want and no, it doesn't integrate well with the Java

On 2 September 2016 at 14:54, Thomas Petzoldt wrote: | Hi, | | I have the same problem and, at a first look, the issues reported by the | CRAN checks seemed easy to fix. However, after checking it again locally | and on http://win-builder.r-project.org it appeared that GCC 4.9.3 | (Windows, Rtools 3.4), same also on win-builder reports even more | issues, especially legacy Fortran (mainly

So I had this crazy idea to put together a cheap video wall<https://lh6.googleusercontent.com/-GNJ97iKoU3Y/UumgZ62KESI/AAAAAAAAa8Y/t07wL1D7Tmk/w931-h698-no/IMG_20140125_210754.jpg> in my local hackerspace using a lot of screens suffering from planned obsolescence or at least a poor choice in their used caps and cheap - used Nvidia NVS 440 cards. During evaluation of Win 7/8 I noticed there was an 8 gpu OS limit that I didn't know of before. I also ran into that limt using the proprietary nvidia driver on Linux. So now I'm trying to see how far nou...

Hi Kurt, I have started to look into this, and I need some guidance about how to prioritize my repairs. There are basically 4 categories of warnings from gfortran?s pedantic critique of my packages: 1. Some errant tab characters it doesn?t like, 2. Too many or too few continue statements 3. Horrible (and obsolescent) arithmetic and computed gotos 4. undeclared doubles and dubious

Hi, Following on from suggestions made last week, I decided to install R 2.1.0 on my Linux machine. I'm running into a problem there however, as shown: make[1]: Entering directory `/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/library/Recommended' make[2]: Entering directory `/d0/home/fgibbons/tmp/R2.1.0/R-2.1.0/src/library/Recommended' begin installing recommended package VR WARNING:

...or: Ben Campbell <ben at nostrum.com> Mailing list Address: cellar at ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/cellar Archive: https://mailarchive.ietf.org/arch/browse/cellar/ Charter: The preservation of audiovisual materials faces challenges from technological obsolescence, analog media deterioration, and the use of proprietary formats that lack formal open standards. While obsolescence and material degradation are widely addressed, the standardization of open, transparent, self-descriptive, lossless formats remains an important mission to be undertaken by the open...

Hi Dmitry, Where were you expecting notice to have been given? If I recall correctly, the obsolescence of the C backend was mentioned many times on this mailing list, and as Owen notes, in the release notes since 2.8. I'm not trying to be snarky. You were obviously genuinely surprised by its removal, and that makes me wonder if where the core open source devs are expecting people to look for tha...

...st code (such as the above) as a solution to someone else's problem: As received, it just would not work! Comment: I have for long time been under the impression, now apparently a delusion, that the abominable quoted-printable had found its due final resting-place in the Museum of Dishonorable Obsolescence; apparently not! Also, if people are using web-mailers (Yahoo or other) that wantonly insert this kind of rubbish, they should look into the possibility of either changing the configuration under which they post their mails (if possible), or mailing via a different agent. The "quoted-printab...

Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.

On Fri, January 9, 2015 17:36, John R Pierce wrote: > On 1/9/2015 2:32 PM, Always Learning wrote: >> Enterprise, in the RHEL context, suggests stability or have I >> misunderstood the USA definition of "Enterprise" ? > > > Enterprise to me implies large business Enterprise literally means 'undertaking'. It has been used euphemistically since the later

...other devs who can contribute test suites. So, I'll give patches, you - tests. Let's team up! Cristianno, are you interested? - D. 2012/4/19 Jim Grosbach <grosbach at apple.com>: > Hi Dmitry, > > Where were you expecting notice to have been given? If I recall correctly, the obsolescence of the C backend was mentioned many times on this mailing list, and as Owen notes, in the release notes since 2.8. I'm not trying to be snarky. You were obviously genuinely surprised by its removal, and that makes me wonder if where the core open source devs are expecting people to look for tha...

Dear all, I've also noticed C backend was removed a little bit... silently. In the end of March I only got open bugs closed by Benjamin Kramer in bugzilla, but they sounded like "decision is made". So the question is: it such silent removal a normal practice? In times of 3.0 release there were long discussions on what to drop and what to preserve, e.g. sparc backend, if I remember

Hello, My name is Sean Gilligan (wikiname: SeanGilligan) and I'd like to contribute to the CentOS wiki. Initially I'd like to do some documentation for Java (OpenJDK) on CentOS 5.3. I've used Fedora for years, but am getting tired of the obsolescence that keeps happening. I'm also very excited about having an integrated Java that I can use for actual server deployments. I like to document install processes and have been doing it on an internal (Fedora-hosted MoinMoin) wiki for some years now. I'm excited about contributing to and...

Hello, Does Xen support IA64 ? If not, is there a project to port Xen on IA64. Best Regards. Valerie. ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

I have released a patch for klibc which changes off_t to 64 bits, and hopefully deals with most of the rest of the fallout. We shouldn't be using any obsolescent types anymore, except for struct statfs (I intend to hack that next so we use statfs64() and fstatfs64()). We're still using some older system calls, like sigaction() instead of rt_sigaction() where available, but