similar to: NUT 2.6.3 compile error @ slackware64-current

Displaying 20 results from an estimated 400 matches similar to: "NUT 2.6.3 compile error @ slackware64-current"

2011 Oct 13
1
nut 2.6.2 possible bug
Built for years every version using: ./configure --with-usb Configuration summary: ====================== build serial drivers: yes build USB drivers: yes build SNMP drivers: yes build neon based XML driver: yes build Powerman PDU client driver: no build IPMI driver: no enable SSL development code: yes enable libwrap (tcp-wrappers) support: yes build CGI programs: no enable HAL support: no
2011 Jun 28
3
Changes to upscli_connect
Hello, I am currently working on the nut scanner. For detecting available upsd on the network, I rely on upscli_connect. The problem with this function is that it calls a blocking "connect" function. So the nut-scanner is blocked while waiting for the TCP timeout when trying to connect to an IP without upsd available . Since this timeout may be rather long (3 minutes on my host), I
2014 Apr 16
0
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
On 04/16/2014 02:15 PM, Didier Spaier wrote: > Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 > (to make a bootable USB stick) fails like this: > > Error converting to codepage 850 Invalid argument > Cannot initialize 'S:' > Bad target s:/ldlinux.sys > syslinux: failed to create ldlinux.sys > > But running the same command in
2014 Apr 16
2
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
On 16/04/2014 23:46, H. Peter Anvin wrote: > On 04/16/2014 02:15 PM, Didier Spaier wrote: >> Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 >> (to make a bootable USB stick) fails like this: >> >> Error converting to codepage 850 Invalid argument >> Cannot initialize 'S:' >> Bad target s:/ldlinux.sys >>
2010 Aug 09
2
Error compiling wine 1.3.0 on slackware64
im having a error compiling wine version 1.3.0 on slackware64 i have the multilib gcc and 32 bit packages installed and i cannot compile i am getting this error. make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/root/wine-1.3.0/dlls/windebug.dll16' make[1]: Entering directory `/root/wine-1.3.0/dlls/windowscodecs' gcc -m32 -c -I. -I. -I../../include -I../../include
2014 Apr 16
0
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
On 04/16/2014 04:07 PM, Didier Spaier wrote: > > Confirmed, thanks Hans. > Don't call me that, please. > > So I assume that we need to ship iconv in the initrd. > Or ship the "linux" version instead of the "mtools" version of syslinux, or use the extlinux installer and mount explicitly. -hpa
2012 Nov 30
1
Fw: quantreg installation and conflicts with R 2.15.2
Just noticed that I get a similar error about object 'kronecker' in "Matrix" package when trying to load "lme4". So this is a more pervasive problem. Brian Brian S. Cade, PhD U. S. Geological Survey Fort Collins Science Center 2150 Centre Ave., Bldg. C Fort Collins, CO 80526-8818 email: brian_cade@usgs.gov tel: 970 226-9326 ----- Forwarded by Brian S
2014 Apr 16
2
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 (to make a bootable USB stick) fails like this: Error converting to codepage 850 Invalid argument Cannot initialize 'S:' Bad target s:/ldlinux.sys syslinux: failed to create ldlinux.sys But running the same command in the installed system succeeds. In both cases we are using syslinux-4.0.6 (same syslinux
2009 Nov 01
3
Picture Tutorial: How to Setup Slackware64 13.0 HVM domU with Xen 3.5-unstable pv-ops Dom0 Kernel 2.6.31.4 in Fedora 11 x86-64 Dom0
Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ There are 83 screenshots so far at
2009 Nov 01
3
Picture Tutorial: How to Setup Slackware64 13.0 HVM domU with Xen 3.5-unstable pv-ops Dom0 Kernel 2.6.31.4 in Fedora 11 x86-64 Dom0
Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ There are 83 screenshots so far at
2013 Jan 15
1
RFC Eaton serial scan
?Hello, I would like to merge branches/serial_nutscanner to the trunk. The attached patch contains the needed modifications. You can read docs/man/nutscan_scan_eaton_serial.txt to see what it is about and docs/man/nut-scanner.txt to see modification to nut-scanner tool interface. This adds about 100K to the libnutscan.so file. Regards, Fred -----------------------------
2017 Dec 05
0
warnings about factor levels dropped from predict.glm
A guess (treat accordingly): Different BLAS versions are in use on the two different machines/versions. In one, near singularities are handled, and in the other they are not, percolating up to warnings at the R level. You can check this by seeing whether the estimated fit is the same on the 2 machines. If so, ignore the above. -- Bert Bert Gunter "The trouble with having an open mind
2010 Nov 30
1
Compiling ocfs2-tools-1.6.3 on slackware64-13.1
Hello all, I'm having trouble compiling ocfs2-tools-1.6.3 on slackware64-13.1 These are my configure flags (the last 2 I added after googling this problem, but didn't help): ./configure \ --sbindir=/sbin \ --bin=/bin \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --datadir=/etc/ocfs2 \ --sharedstatedir=/var/ocfs2 \ --libexecdir=/usr/libexec \
2011 Sep 19
1
Compilation error: NUT 2.6.2 --without-snmp
Hello all! I get a compilation error with '--without-snmp' option. Can someone help please? Thanks in advance Sergey Env: === 1. Nut-2.6.2 2. gcc-3.3.6 ----- ./configure -q --prefix=/usr --with-drivers=richcomm_usb --with-user=upsd --with-group=upsd --with-cgi --with-cgipath=/www/cgi-bin --with-htmlpath=/www --with-statepath=/var/state/ups --without-wrap --without-snmp --without-serial
2005 Feb 23
2
stopping a function
I've looked for this information in all the R help sources I could find and found nothing. Is it possible to use some function key to stop the execution of some R command without ending the R session (Windows, R 1.91)? I've several times started functions that for various reasons are not executing properly and it would be nice to stop them without killing the R session. I've been
2011 Feb 25
4
means, SD's and tapply
I'm trying to use tapply to output means and SD or SE for my data but seem to be limited by how many times I can subset it. Here's a snippet of my data > stems353[1:10,] Time DataSource Plot Elevation Aspect Slope Type Species SizeClass Stems 1 Modern Cameron 70F221 1730 ESE 20 Conifer ABCO Class1 3 2 Modern Cameron 70F221 1730
2018 Jan 12
1
glm$effects
I know I must be missing something obvious, but checking help and googling a bit did not turn up a useable answer. When I've estimated a glm() model object (my example is with just identity link with gaussian family so I could have used lm() instead), one of the terms returned in the model object is listed as $effects. What are these quantities? I have not been able to relate them to the
2012 Nov 30
1
quantreg installation and conflicts with R 2.15.2
I recently lost the partitions on my hard drive (second time in 6 months) so I had to have our IT folks image all my files over to a new drive. I completely reinstalled R (now 2.15.2) and all my libraries to my computer (Dell Latitude running Windows 7). A few of my previous workspaces (created with R 2.14.1) can't be restored, reporting an error similar to the one I get when I try to
2017 Dec 05
2
warnings about factor levels dropped from predict.glm
I am helping a student with some logistic regression analyses and we are getting some strange inconsistencies regarding a warning about factor levels being dropped when running predict.glm(, newdata = ournewdata) on the logistic regression model object. We have checked multiple times that the factor levels have been defined similarly on both data sets (one used to estimate model and the newdata)
2007 Mar 19
1
likelihoods in SAS GENMOD vs R glm
List: I'm helping a colleague with some Poisson regression modeling. He uses SAS proc GENMOD and I'm using glm() in R. Note on the SAS and R output below that our estimates, standard errors, and deviances are identical but what we get for likelihoods differs considerably. I'm assuming that these must differ just by some constant but it would be nice to have some confirmation