Skip to content

Commit e36aa71

Browse files
committed
doc CHANGE add infor about missing extensions plugins into FAQ
1 parent 430b252 commit e36aa71

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

FAQ.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,4 +21,23 @@ $ make
2121
or add the libyang's location to the linker paths in `/etc/ld.so.conf.d` and
2222
then run `ldconfig` to rebuild the linker cache.
2323

24+
__Q: yanglint(1) does not start and, but prints the following error messages:__
25+
```
26+
./yanglint
27+
libyang[0]: Invalid keyword "type" as a child to "annotation". (path: /)
28+
libyang[0]: Module "yang" parsing failed.
29+
Failed to create context.
30+
```
31+
32+
__A:__ To handle complex YANG extensions, libyang (and therefore yanglint(1))
33+
needs plugins. By default, the plugins are installed into the system path
34+
(next to the libyang library into the separate `libyang` subdirectory). If
35+
libyang was not installed, yanglint cannot find these plugins and it fails.
36+
If you do not want to install libyang, it is possible to specify path to the
37+
plugins via environment variable. The plugins can be found in the libyang
38+
build directory in `src/extensions/` subdirectory. So running yanglint(1)
39+
then can be made this way:
40+
```
41+
$ LIBYANG_EXTENSIONS_PLUGINS_DIR=`pwd`/src/extensions ./yanglint
42+
```
2443

0 commit comments

Comments
 (0)