Re: [Nut-upsdev] Build error after pulling the latest

Fri, 24 Jan 2025 08:18:51 -0800

At 01:45 AM 1/24/2025, Jim Klimov wrote:
Hello,

  Did you re-run `autogen.sh` and `configure` after the source code base change that impacted `configure.ac` and/or the m4 scripts it includes?

Jim


On Fri, Jan 24, 2025 at 6:37 AM William R. Elliot <[email protected]> wrote:
Hello all.
I pulled the latest from the repository and merged it with my driver development activity. Building from the 'nut' directory I receive the following error(s):
  CC       libcommon_la-common.lo
common.c: In function 'suggest_doc_links':
common.c:692:25: error: 'MAN_SECTION_CMD_SYS' undeclared (first use in this function)
  692 |                         MAN_SECTION_CMD_SYS, buf2);
      |                         ^~~~~~~~~~~~~~~~~~~
common.c:692:25: note: each undeclared identifier is reported only once for each function it appears in
common.c:696:25: error: 'NUT_WEBSITE_BASE' undeclared (first use in this function)
  696 |                         NUT_WEBSITE_BASE, buf2);
      |                         ^~~~~~~~~~~~~~~~
At top level:
cc1: note: unrecognized command-line option '-Wno-unknown-warning-option' may have been intended to silence earlier diagnostics
cc1: note: unrecognized command-line option '-Wno-reserved-identifier' may have been intended to silence earlier diagnostics
make[2]: *** [Makefile:904: libcommon_la-common.lo] Error 1
This is the most recent entry in the 'master' log:

commit 4c00520887d7ec17ae413eadb2e698f8ad95d33c (origin/master, origin/HEAD, master)
Merge: 9066236ec 8c851c836
Author: Jim Klimov <[email protected] >
Date:   Thu Jan 23 11:23:24 2025 +0100
    Merge pull request #2778 from jimklimov/fix-appveyor-libmodbus
   
    Fix Appveyor CI to use NUT libmodbus fork
I am doing my driver work on Ubuntu Linux.
Hopefully this is something easy to fix...for those who are deep into nut.
Thanks,
Bill

Virus-free. www.avg.com

Hello Jim.

Of course not! But now that I have, everything builds fine. Thank you.

Bill

[Anecdotal...read at your leisure]

Many, many years ago I was instructing one of the office staff on the use of a word processor application that was new to them. As long as what I instructed fit what the person was trying to do everything was fine. But if they tried to do something that was outside what had been taught they went off into the weeds. I was familiar with the application and could pull them out of the weeds and get them back on track to accomplishing their goal.

[This probably says a lot about the instructor rather than the staff member, but that is not the point. :-) ]

As someone who is just trying to get a driver to work well, I just needed to know how to build the project and add my driver files to it so I can build/test/change/build/test/repeat. I did that build months ago and have stayed in the 'drivers' directory pretty much since. Trying to fork the repository (which should have been done at the start) and push my changes caused the need to pull the master branch again which sent me into the weeds. Jim, thanks for knowing how to get me out of the weeds quickly!


_______________________________________________
Nut-upsdev mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev

Reply via email to