Re: phase installing: nut-snmp-2.7.4-1 failed

Alexander Hansen <[email protected]>
Newsgroups gmane.os.apple.fink.beginners
Message-ID <[email protected]>
Note:  we prefer that users try to go through their outputs rather than sending log files or other attachments.  It’s easy to lose track of what is going on when you use an attachment.

> On Jun 9, 2020, at 08:02, Bernhard Heinz <[email protected]> wrote:
> 
> Hi there,
> 
> I am getting the follwing error trying to build nut on my Mac OS 10.14.6 Mac mini (End 2014):
> phase installing: nut-snmp-2.7.4-1 failed
> 
> Same happens when I build nut-snmp separately.I cannot identify the build line where the error has been initiated, therefore I attach the entire Logfile.
> 
> Please help
> 
> Thanks in advance
> 
> Bernhard
> 
> 
> Bernhard HEINZ
> 
> Germany
> 
> Phone:+49 (0) 7545-2963
> Mobile:+49 (0) 171-420-6621
> Email:[email protected]
> 
> FaceTime:[email protected]
> Skype:b.a.heinz
> Facebook:http://facebook.com/bernhard.a.heinz
> _______________________________________
> Von meinem Mac Mini gesendet
> 
> 
> 
> 
> Extract from log  (Full Logfiles of nut-snmp and build are attached):
> 
> ### execution of /bin/mv failed, exit code 1
> ### execution of /tmp/fink.Fq36h failed, exit code 1
> Removing runtime build-lock...
> Removing build-lock package...
> /opt/sw/bin/dpkg-lockwait -r fink-buildlock-nut-2.7.4-1
> (Reading database ... 34300 files and directories currently installed.)
> Removing fink-buildlock-nut-2.7.4-1 ...
> Failed: phase installing: nut-snmp-2.7.4-1 failed
> 
> ...
> 
> Also include the following system information:
> Package manager version: 0.45.1
> Distribution version: selfupdate-rsync Mon Jun  8 10:22:33 2020, 10.14.5, x86_64
> Trees: local/main stable/main
> Xcode.app: 11.3.1
> Xcode command-line tools: 11.3.1.0.1.1576735732
> Max. Fink build jobs:  1
> 
> <200609-16.51-nut-snmp-build.txt>_______________________________________________


For a bit more context, what actually failed to “mv” is the following:

sudo -u fink-bld [ENV] sh -c /tmp/fink.Fq36h
/usr/bin/install -d -m 755 /opt/sw/src/fink.build/root-nut-snmp-2.7.4-1/opt/sw/lib/nut
/bin/mv /opt/sw/src/fink.build/root-nut-2.7.4-1/opt/sw/lib/nut/snmp-ups /opt/sw/src/fink.build/root-nut-snmp-2.7.4-1/opt/sw/lib/nut/
mv: rename /opt/sw/src/fink.build/root-nut-2.7.4-1/opt/sw/lib/nut/snmp-ups to /opt/sw/src/fink.build/root-nut-snmp-2.7.4-1/opt/sw/lib/nut/snmp-ups: No such file or directory
### execution of /bin/mv failed, exit code 1

There weren’t any error messages.  Checking the configuration stage for SNMP, I saw the following:

checking for Net-SNMP version via net-snmp-config... 5.6.2.1 found
checking for Net-SNMP cflags... -DNETSNMP_ENABLE_IPV6 -fno-strict-aliasing -g -Os -pipe -DBUILD=161 -DMACOSX_DEPLOYMENT_TARGET=10.14 -F/BuildRoot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.Internal.sdk/System/Library/PrivateFrameworks/ -F/BuildRoot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.Internal.sdk/System/Library/Frameworks/ -I/usr/local/libressl/include -Udarwin18 -Ddarwin18=darwin18 -I/usr/local/include
checking for Net-SNMP libs... -lnetsnmp -lcrypto.35
checking for net-snmp/net-snmp-config.h... yes
checking for init_snmp... no
….
Configuration summary:
======================
build serial drivers: yes 
build USB drivers: yes 
build SNMP drivers: no 

Is there an /opt/sw/src/fink.build/nut-snmp-2.7.4-1/nut-snmp/config.log file?  (I don’t know the exact path, but just look for config.log.  If so, you should be able to open that and search for “snmp" or “SNMP" to see what is reported.

-- 
Alexander Hansen, Ph.D.
Fink User Liaison



_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.