06-10-2023 05:13 AM - edited 06-10-2023 05:15 AM
❯ make clean all
rm -rf ../load-dir
mkdir -p ../load-dir
/Users/basharaziz/abc/../nso-6.1/bin/ncsc `ls basic-service-ann.yang > /dev/null 2>&1 && echo "-a basic-service-ann.yang"` \
--fail-on-warnings \
--yangpath ../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang \
-c -o ../load-dir/basic-service.fxs yang/basic-service.yang
❯ make clean all
rm -rf ../load-dir
mkdir -p ../load-dir
/Users/basharaziz/abc/../nso-6.1/bin/ncsc `ls basic-service-ann.yang > /dev/null 2>&1 && echo "-a basic-service-ann.yang"` \
--fail-on-warnings \
--yangpath ../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang \
-c -o ../load-dir/basic-service.fxs yang/basic-service.yang
../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang/tailf-ned-cisco-ios.yang:210823: error: when tailf:cli-drop-node-name is given, it is recommended that tailf:cli-suppress-mode is used in combination. using tailf:cli-drop-nodename in a list child without using tailf:cli-suppress-mode on the list, might lead to confusing behaviour, where the user enters the submode without being able to give further configuration.
../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang/tailf-ned-cisco-ios.yang:210823: error: when tailf:cli-drop-node-name is given, it is recommended that tailf:cli-suppress-mode is used in combination. using tailf:cli-drop-nodename in a list child without using tailf:cli-suppress-mode on the list, might lead to confusing behaviour, where the user enters the submode without being able to give further configuration.
../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang/tailf-ned-cisco-ios.yang:260455: error: when tailf:cli-drop-node-name is given, it is recommended that tailf:cli-suppress-mode is used in combination. using tailf:cli-drop-nodename in a list child without using tailf:cli-suppress-mode on the list, might lead to confusing behaviour, where the user enters the submode without being able to give further configuration.
../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang/tailf-ned-cisco-ios.yang:292727: error: when tailf:cli-drop-node-name is given, it is recommended that tailf:cli-suppress-mode is used in combination. using tailf:cli-drop-nodename in a list child without using tailf:cli-suppress-mode on the list, might lead to confusing behaviour, where the user enters the submode without being able to give further configuration.
make: *** [../load-dir/basic-service.fxs] Error 1
module basic-service {
namespace "http://example.com/basic-service";
prefix basic-service;
import ietf-inet-types {
prefix inet;
}
import tailf-common {
prefix tailf;
}
import tailf-ncs {
prefix ncs;
}
import tailf-ned-cisco-ios {
prefix ios;
}
description
"Bla bla...";
revision 2016-01-01 {
description
"Initial revision.";
}
augment "/ncs:services" {
list basic-service {
description "This is an RFS skeleton service";
key name;
leaf name {
type leafref {
path "/ncs:devices/ncs:device/ncs:name";
}
}
uses ncs:service-data;
ncs:servicepoint basic-service-servicepoint;
leaf int-name {
type string;
}
leaf loopback-ip {
type inet:ipv4-address;
}
leaf loopback-description {
type string;
}
leaf hostname {
type string;
}
}
}
}
all: fxs
.PHONY: all
# Include standard NCS examples build definitions and rules
include $(NCS_DIR)/src/ncs/build/include.ncs.mk
src=$(wildcard yang/*.yang)
DIRS = ../load-dir
FXS = $(SRC:yang/%.yang=../load-dir/%.fxs)
## Uncomment and patch the line below if you have a dependency to a NED
## or to other YANG files
YANGPATH += ../../cisco-ios-cli-6.93/src/ncsc-out/modules/yang \
I am able to LS the subdirectories from src:
~/nso-6.1-run/packages/basic-service/src ls ../../cisco-ios-cli-6.93/
CHANGES LICENSES.nedcom/ build-meta-data.xml netsim/ private-jar/ src/
LICENSE README load-dir/ package-meta-data.xml shared-jar/
Solved! Go to Solution.
06-12-2023 05:29 AM
The errors you get looks like warnings to me. The compilation will fail on warnings since you compile with the --fail-on-warnings flag. Try removing that flag, if you're ok with the warnings. Those are by the way warnings from the NED YANG that your package is pointing to, so you won't be able to do much about them from your own package anyway.
06-12-2023 05:29 AM
The errors you get looks like warnings to me. The compilation will fail on warnings since you compile with the --fail-on-warnings flag. Try removing that flag, if you're ok with the warnings. Those are by the way warnings from the NED YANG that your package is pointing to, so you won't be able to do much about them from your own package anyway.
06-12-2023 01:40 PM
Thank you Hazad. It works after removing the warning. It comes from old packages.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide