-
-
Notifications
You must be signed in to change notification settings - Fork 391
Adapt to builds with Slackware 15 #2143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…VE_WINDOWS [networkupstools#2142] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Not sure if this still is in progress (and I'm too fast) but - in present state - not sure if this will suffice. Lines 2780 to 2789 in 2856cac
|
On another note - should it even consider building for Windows when we don't specifically request it as a build target? |
That's what I looked for the first time, how you can disable building for Windows. |
Argh, right. Missed that while commuting, phone screen is just that large... :\ |
Curiously - note how no other system complains, still... |
That's what Slackware64-current does, it quickly implements new releases, that's why I use it and it ends up creating addiction, it's hard for me to use anything else. It also creates problems now with NUT, but also other applications, for example Clamav, which has problems with the new versions of other included software. |
… build environment Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Well in all fairness to Slackware, I think their only "fault" there was not stripping the Windows binaries from GNU Binutils as probably most other distributions would do when not also shipping out MinGW. It's a "problem" with 15.0 and older versions respectively as well, but it's true Slackware does like to package as much software as possible into their distribution. |
Bumped this PR with a "reference" docs update on how I set up the Slackware environment for local tests (and it does complain about So far one lacking bit is a modern Java which could let this VM become part of NUT CI farm. Maybe that would start with the older Java 8 and some (older?) remote or swarm plugin, but not sure OTOH. |
For what it's worth, I use JDK11 from here: http://www.slackware.com/~alien/slackbuilds/openjdk11/pkg64/ You'd download the respective txz package and install it via 'installpkg'. P.S. I personally also consider Sotirov's SlackPack a reputable repository: https://sotirov-bg.net/slackpack/ |
… build environment - clarify Alien Slack Builds Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
…ed header files Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
…required tools and headers are in place Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Well, at least now |
Building this without any troubles now (via |
Good to hear, thanks for the feedback. Well, it was... interesting. But now I've got so many curious OSes in the zoo here, what's another?.. :) |
So, with a patchwork from several package repos (still missing a few bits like GPIO and I2C) the NUT Configuration summary:
NUT Paths:
NUT Paths for third-party integrations:
NUT Build/Target system info:
NUT Compiler settings:
|
Looking good, one thing to note: --build=x86_64-slackware-linux Essentially all build recipes are built like that on Slackware: --build=$ARCH-slackware-linux Never got i2c or GPIO working myself either. |
Do you mean that's something worth providing as the |
Ach jo, portability and legacy compatibility - bit us here (on another old CI system):
|
So as long as I'm CI-testing and not packaging "cleanly", it should not matter? Or can there be some practical differences (different set of compiler default settings etc.) so that a build passing for CI with auto-guessed defaults (or common ones from |
The latter, it's the buildtype most users (and not just packagers, since Slackware is more self-building driven than some other distributions) on Slackware would likely build for and hence a defaults-passed CI might not necessarily mean it must also build/pass cleanly with the specific Slackware buildtype - I'd see it as a distro-specific precaution worth passing (if easily possible). Another older example (for self building): But I'm not an expert when it comes to CI, so that's just my view as user/packager on Slackware - and with that I must say good night for now. ;-) |
Ok, thanks for clarifications. Bastardized that script a bit locally to configure similarly, but it still passes :D
NUT Configuration summary:
NUT Paths:
NUT Paths for third-party integrations:
NUT Build/Target system info:
NUT Compiler settings:
Hit one more snag though:
Missed |
…seline (not in default install) Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
… ASCIIDOC_MIN_VERSION [networkupstools#2142] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
…etworkupstools#2142] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
Oh... there is an |
Eh, github lags today... "Checking for ability to merge automatically… Hang in there while we check the branch’s status." takes a minute or so, and appveyor gives up in a second: "continuous-integration/appveyor/pr — AppVeyor was unable to build non-mergeable pull request" (but sometimes catches up de-facto without notifications)... It is also very slow to check out. To the point of git timing out after 3 minutes :\ |
Very happy to see this integrated into CI and building nicely on all my Slackware environments now - THANKS. 🥇 |
lua-5.4.6 is already in Slackware-64-current so it will also be in Slackware 15.1 (current becomes stable at a certain point and then the cycle continues). |
…upstools#2143 follow-up] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
…exec option [networkupstools#2143 follow-up] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
For any other "slackers", you'll be delighted to hear that NUT is now a part of the default set of pre-compiled packages shipping with Slackware OS. It has since this PR been integrated into the https://mirrors.slackware.com/slackware/slackware64-current/ChangeLog.txt
https://mirrors.slackware.com/slackware/slackware64-current/source/a/nut/ Many thanks, Jim! |
And thanks back to you for a lot of testing, ideas and questions - both Slackware-related and not. |
Started as
scripts/Windows/Makefile.am: limit binary builds to cases where we HAVE_WINDOWS
and as such -Closes: #2142