similar to: Reviving the Windows port of NUT

Displaying 20 results from an estimated 10000 matches similar to: "Reviving the Windows port of NUT"

2014 Jan 15
0
Reviving the Windows port of NUT
2014/1/15 Charles Lepple <clepple at gmail.com>: > Emilien, > > just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! > We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. I am just fixing some bugs and implementing some minor windows-specific features. > The problem is that
2014 Jan 16
1
Reviving the Windows port of NUT
On Jan 15, 2014, at 10:18 AM, Emilien KIA wrote: > 2014/1/15 Charles Lepple <clepple at gmail.com>: >> Emilien, >> >> just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! >> We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. > > I am just fixing some bugs
2011 Jan 28
1
ssl-nss-port branch does not compile on Ubuntu (asciidoc)
It looks like there was an issue with the AsciiDoc merge from the trunk: http://buildbot.networkupstools.org/private/nut/builders/Ubuntu-lucid-x86/builds/119/steps/compile/logs/stdio As mentioned in the email about windows_port, I would recommend testing the branch after a merge from the trunk. You can either run "make distcheck", or contact me (off-list) to set up a password so
2011 Sep 20
3
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
Hello everybody, Just a short note that clang build "clang-native-arm-cortex-a9" is broken and the very last successful build was for revision 139932. All newer revisions fail. The builder is available here: http://172.16.0.135:8011/waterfall Thanks Galina
2013 Oct 17
0
UPSC based Windows Client
[Please remember to copy the list.] On Oct 15, 2013, at 8:45 AM, eric kreuwels wrote: > Hi Charles > > Thanks for your answer. Good questions/suggestions. I copied both the WinUPSC and the installer project on my GDRIVE and shared it with you: > https://docs.google.com/file/d/0B0mSjYYj84-6ZGM4MWZfMnFxbUU/edit?usp=sharing > > Archiving WinUPSC in the NUT GitHub would be my
2015 Mar 19
4
Roadmap to 2.7.3
Hi Charles and the list, a complementary update... 2015-03-16 13:46 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 4, 2015, at 9:04 AM, Charles Lepple wrote: > > > We only have a few open items that I think should be resolved before > releasing 2.7.3. The list grew a bit in the past week, but we'll cover that > later. Here is the list: > > > >
2011 Sep 20
2
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
The host c++ standard library is missing <utility>, it appears. On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > Please use the correct link : > http://63.145.236.72:8011 > and ignore the previous. > > Also log for broken build is here: > > make[1]: Entering directory >
2012 May 03
1
[nut-commits] svn commit r3554 - branches/windows_port/common
c'est quoi cette chelouzerie ? je parle de l'ajout du sizeof(DWORD)... et ce que ce serait pas un str*n*cpy ou s*n*printf la vraie solution ? Arno 2012/5/3 Frederic BOHE <fbohe-guest at alioth.debian.org>: > Author: fbohe-guest > Date: Thu May ?3 08:31:38 2012 > New Revision: 3554 > URL: http://trac.networkupstools.org/projects/nut/changeset/3554 > > Log: >
2012 Oct 12
2
NSS support in trunk (was: NSS branch pull request)
2012/10/12 Emilien Kia <kiae.dev at gmail.com> > Hi guys, > Hi Emilien and the list, This is a pull request to finally merge NSS feature in nut trunk: > https://github.com/clepple/nut/pull/3 > I'd like to take a moment to shed some more light on this important development, which lasted 3 years: - the initial
2011 May 24
2
Merging windows_port branch
Hello, As you may have noticed, a first running version of nut for Windows has been released some time ago. In order to validate the possibility to merge the windows_port branch to the trunk, I have produced a patch file using the "svn diff" command. This patch couldn't be applied directly and the use of a merging tool is still needed. It is only intended to be reviewed so that we
2011 Sep 20
0
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
Please use the correct link : http://63.145.236.72:8011 and ignore the previous. Also log for broken build is here: make[1]: Entering directory `/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build llvm[1]: Compiling APInt.cpp for Release+Asserts build In file included from APFloat.cpp:15: In file
2012 Nov 09
1
nut_clock_* UT review
2012/11/9 <VaclavKrpec at eaton.com> > Hello gentlemen, > Hi Vasek, I'm moving the thread to -upsdev, since it has not to be private... please note that revisions 3771 and 3772 conclude nut_clock_* > development (including UTs): > interestingly enough, we were talking about that 5 mn ago with Emilien ;) my conclusion was that nut_clock devs were completed with 3772, and
2011 Sep 20
1
[LLVMdev] [cfe-commits] Clang build "clang-native-arm-cortex-a9" is broken
Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host? -eric On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote: > The host c++ standard library is missing <utility>, it appears. > > > On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > >> Please use the correct link : >>
2015 Jul 06
4
Nut-2.7.3 & gcc-3.3.6
Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternative to
2015 Jul 06
4
Nut-2.7.3 & gcc-3.3.6
Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternative to
2012 Oct 08
1
HPUX warning during build spotted
?Hello everybody, during the last build (#380) on HPUX (eaton-hpux11-pa-risc buildslave), I've noticed the following warning when compiling upsd: ../../server/upsd.c:417: warning: implicit declaration of function 'fromhost' fromhost is either an alias for sock_host or declared as extern void fromhost() in tcpd.h (iff any of TLI or PTX or TLI_SEQUENT macra are defined), which I guess
2010 Nov 25
3
Announce: new team member (to work on Mozilla NSS port)
Dear fellows, As you have probably seen, NUT has had a recent boost through the help of Eaton. Frederic Bohe (contractor for Eaton France) has worked on Augeas, and is now working the Windows port. Chetan Agarwal, seconded by Prashi Gandi (both from Eaton India) are working on XCP and quality / validation related projects. I'm now pleased to announce that Emilien Kia (contractor for Eaton
2013 Oct 14
3
UPSC based Windows Client
[attachments trimmed] Begin forwarded message: > From: eric kreuwels > Subject: UPSC based Windows Client > Date: October 13, 2013 4:43:31 PM EDT > To: nut-upsdev at lists.alioth.debian.org > > > Dear developers > > Last month I wrote WinUPSC, a Windows task tray UPS monitor. WinUPSC re-uses the UPSC logic to poll the UPS. > This initial version was tested
2013 Aug 18
2
APC Back-UPS CS and ES series
I'm using FreeNAS 9.1, and I've just got an APC Back-UPS CS 500. In theory it's supported by NUT, but the latest released version (2.6.5) doesn't have support for it (the driver reports an error, which is apparently due to an overflow). According to a thread on the mailing list, Back-UPS ES series requires a fix that's in source control, and CS series requires an additional
2015 Apr 08
2
Roadmap to 2.7.3
Hi Charles and the list here is an update on 2.7.3 2015-03-20 3:33 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 19, 2015, at 2:00 PM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > * #158: the branch has been collapsed into one commit, but additional >> documentation (nut-names.txt) is needed: >>