search for: spec'd

...m >> involved with, I need at least glib 2.19. > > > Do you know why? As in, what features or fixes are required? If not, I think John's question is pertinent. If you're building a binaries to distribute, your best bet might actually be to produce multiple builds targeting specific Linux distributions. Alternately, some specific LSB release (none of which, as far as I can tell, require glibc 2.19+). To all...yes I meant glibc, not glib. Target environment -- could be any version of Linux. This is for Apache OpenOffice. The buildbots we've been using are being decommi...

...d they are harder to find. As I > recall, one should avoid "deep discharge" batteries for UPSes. A deep > discharge battery is great for constant load stuff (like wheelchairs, > golf carts, etc) but UPSes need "shorter" bursts of lots of power. > > I read the spec sheets and order the heaviest batteries I can find. > More lead means heavier batteries, and longer life. My 16 batteries arrived last night. > I check each battery's initial voltage. I have a note that says I > expect at least 12.9V, but I haven't had a chance to verify this...

Sounds like great advice, thanks! Would you care to post it to the NUT wiki or in-source FAQ document (or can I)? Probably the meaningfulness of specific company names is too geographically and temporally limited, however the technical part is universally applicable. Jim On Wed, Nov 13, 2024 at 6:08?AM Harlan Stenn via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > On 11/12/2024 10:58 AM, Dan Langille via Nut-upsuser...

...high-rate batteries, and they are harder to find. As I recall, one should avoid "deep discharge" batteries for UPSes. A deep discharge battery is great for constant load stuff (like wheelchairs, golf carts, etc) but UPSes need "shorter" bursts of lots of power. I read the spec sheets and order the heaviest batteries I can find. More lead means heavier batteries, and longer life. I check each battery's initial voltage. I have a note that says I expect at least 12.9V, but I haven't had a chance to verify this lately. I check the spec'd net weight of the ba...

This worked fine for years until I updated firefox and thunderbird recently. Now, however, when I click on a link in an email in thunderbird, rather than open the indicated webpage in firefox, nothing at all happens. network.protocol-handler.app.http in tbird's about:config specifies the executable /usr/lib/thunderbird/open-browser.sh and running the latter at the CLI with a URL as an arg does work as expected: the spec'd URL is loaded into firefox. So I suspect a bug in tbird. Anyone else having this problem?

...And it makes hard assumption that size of integer is 32 or 64. > This gives us trouble because we have 16 bit integer. > Is there a reason for this assumption? Or we can just add the 16-bit > integer to it as well? Hi Alireza, The reason for this is that the getelementptr instruction is spec'd to take either an i32 or i64. We could extend this, but it probably won't make a difference in practice. If the front-end generates code like: %tmp = sext i16 %idx to i32 %tmp2 = getelementptr float* %P, i32 %tmp Then the llvm code generator will squish the sign extension etc w...

...d be any >> version of Linux. This is for Apache OpenOffice. The buildbots we've been >> using are being decommisioned due to EOL. As a developer on that project, I >> need to be able to test and use the builds. We'll be moving to a Ubuntu 14 >> environment, which is spec'd at glibc 2.19 near as I can determine. So a >> long story. We will not be building for targeted environments. > > Well, at the end of the day, if you're trying to build for multiple > environments then you really need to build to the lowest common > denominator. What...

Hello, nut recently told me that the batteries need replacing in my Eaton 5PX2200RT (ups) and 5PXEBM48RT (external battery pack). According to my notes, it has been just over 4 years since I installed them. Looking at on-line sales, these seem to use batteries in a pre-packaged plastic shell. I don't recall if that's what's in my units or not. Do you have any experience with

This method is defined in: Lib/VMCore/Type.cpp And it makes hard assumption that size of integer is 32 or 64. This gives us trouble because we have 16 bit integer. Is there a reason for this assumption? Or we can just add the 16-bit integer to it as well? Thanks Alireza Moshtaghi Senior Software Engineer Development Systems, Microchip Technology

...l.com> wrote: > > > > Hey folks, > > > > Would you all mind having a bit of a design discussion around the > feature both at the DWARF level and the LLVM implementation? It seems like > what's currently being proposed/reviewed (based on the DWARF feature as > spec'd) is a pretty big change & I'm not sure I understand the motivation, > exactly. > > > > The core point of my confusion: Why does describing the thing a pointer > points to require describing a named variable that it points to? What if it > doesn't point to a na...

Hi, Stumbled into a problem with icecast-2.3.1 (a recent daily svn snapshot). We have 6 spec'd in the xml for the (one and only) mountpt's <mount/max-listeners>. The <limit/clients> near the top of the xml is also set to 6 (as seen on the sample xml dists). When we get up to N-1 listeners, we cannot access the admin webpages from localhost or anywhere-else-host. Here...

Hey folks, Would you all mind having a bit of a design discussion around the feature both at the DWARF level and the LLVM implementation? It seems like what's currently being proposed/reviewed (based on the DWARF feature as spec'd) is a pretty big change & I'm not sure I understand the motivation, exactly. The core point of my confusion: Why does describing the thing a pointer points to require describing a named variable that it points to? What if it doesn't point to a named variable? Seems like there sh...

Hi there... Foolish me.... all was going sooooooo well and then I got a wild hair and updated to the latest clamav .92 today. It is possible I should have just done an rpm update install yet there were some changes in ClamAV lately and I didn't know how well that would go. up till now I spec'd and rolled my own Clamav RPMs without milter somewhat recently ClamAV changed from having a clamav-server RPM file to not having it so I went to the magnificent Dag repo and snagged what I needed I did a yum remove and then a yum localinstall What I didn't think about was that the clam...

...tplatt at us.ibm.com To: R-bugs at biostat.ku.dk Subject: Unable to build Date: Fri, 13 Oct 2006 21:42:37 +0200 (CEST) Full_Name: Daniel E. Platt Version: 2.4.0 OS: AIX 5.3 Submission from: (NULL) (129.34.20.23) Did a new build of gcc c,c++,gfortran v4.1.1, (re)built R 2.3.1 using config.site as spec'd in R-admin.pdf in sec C.9 as described by Jagat Sheth, with addition of FC=gfortran (configure tried using f95, which is present on the system, but won't bind with gcc's obj files). Applying the same to 4.1.1 produces the following: make[4]: Leaving directory `/geno4/watplatt/R/...

On 21 Jun 2012, at 01:19, Chandler Carruth wrote: > cmake, while ugly, can be made to support all of our use cases. There > are some use cases that autoconf+make can't support, So far I have assumed that "use cases that autoconf+make can't support" is referring to Windows support. (I am not a Windows user myself.) But the following two statements left me wondering: Are

...-- CHS current addressable sectors: 16514064 LBA user addressable sectors: 55704096 device size with M = 1024*1024: 27199 MBytes Capabilities: LBA, IORDY(can be disabled) Buffer size: 512.0kB Queue depth: 1 Standby timer values: spec'd by Standard R/W multiple sector transfer: Max = 16 Current = 16 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=240ns IORDY flow control=...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am setting up a proof-of-concept backup server at my office. The end idea is for a dozen or so of our ~200 workstations to dump images (like PowerQuest DeployCenter, not JPEG) to a 2Tb RAID5 at reasonable speeds. The testbed (whose specs are listed below) is, I admit, grossly lacking in RAM. I still think it should handle at least two or three systems at once without choking. But on to that.... Most of the machines we've used as test clients can dump to the system at very high speeds without a problem. CPU utilization hits...

...hat both RVV and SV should avoid using > vscale. > > In the case of RVV, MVL is a hardware defined constant that is never > *intended* to be known by applications. There's no published detection > mechanism. Loops are supposed to be designed to run a few more times on > lower spec'd hardware. > > Robin, what's your thoughts there? > Software should be portable across different RVV implementations, in particular across different values of the impl-defined constants VLEN, ELEN, SLEN. But being portable does not mean software must never mention these (and deri...

On Thu, Nov 14, 2019 at 1:53 PM Robinson, Paul <paul.robinson at sony.com> wrote: > My reading of the DWARF issue is that it was fairly specifically designed > to handle the case of a function taking parameters by pointer/reference, > which is then inlined, and the caller is passing local objects rather than > other pointers/references. So: > > > > void inline_me(foo *ptr) { > > does something with ptr->x...

Hi all, I'm in the final stages of putting a new Vorbis RTP draft together, the new sections are below. There are a number of open questions: 1.) At present there is a 16 bit length field for the codebooks. As they are spec'd as being unbound in length, but typically around 15K, are there situations where they may be greater than 64KB? The size limit can be extended to 2MB as there are 5 bits unused. 2.) We discussed using the RTP seq ids to keep the config RTCP messages in sync with the RTP data stream. I'...