ubuntu 20.04 docker container issue with ld lmavis

[knpshkn]

Hello,
can someone point me in the right direction, I'm trying to build a docker container using ubuntu 20.04, but i'm getting the error
/usr/bin/ld: cannot find -lmavis

gcc -o mavistest mavistest.o -Wl,-rpath,$ORIGIN/../lib64 -L/build/root/event-driven-servers/build/linux-4.19.0-27-amd64-x86_64/mavis -Wl,-rpath,/usr/share/tacacs/lib64 -lmavis  
gcc -shared -o libmavis_log.so libmavis_log.o 
gcc -shared -o libmavis_auth.so libmavis_auth.o tohex.o 
make[4]: Entering directory '/build/root/event-driven-servers/mavis/python'
make[4]: Entering directory '/build/root/event-driven-servers/mavis/perl'
gcc -shared -o libmavis_userdb.so libmavis_userdb.o -L/usr/x86_64-linux-gnu/lib -Wl,-rpath,/usr/x86_64-linux-gnu/lib -lcrypt 
gcc -shared -o libmavis_anonftp.so libmavis_anonftp.o 
gcc -shared -o libmavis_cache.so libmavis_cache.o 
gcc -shared -o libmavis_null.so libmavis_null.o 
/usr/bin/ld: cannot find -lmavis
collect2: error: ld returned 1 exit status
make[2]: *** [/build/root/event-driven-servers/mavis/Makefile.obj:82: mavistest] Error 1
make[2]: *** Waiting for unfinished jobs....

can anyone tell me what is missing?

[MarcJHuber]

Hi,

most likely, there's no libmavis.so binary in /build/root/event-driven-servers/build/linux-4.19.0-27-amd64-x86_64/mavis.

Cheers,

Marc

[knpshkn]

Marc, i'm not a big expert in linux, maybe you have an idea why this might happen?

[MarcJHuber]

Hi,

no, I've no clue. What options did you use when calling ./configure? And what distribution is this, Alpine?

Cheers,

Marc

[knpshkn]

i have

./configure --debug --prefix="${TACACS_DIR}" --minimum tac_plus-ng

and distribution is ubuntu:20.04 (or 24.04 with the same issue)

[MarcJHuber]

Hi,

ok, thanks, sorry, I should have read this more thoroughly.

The build issue might be related to "make" building in parallel. Does "make -j1" show the same issue?

Cheers,

Marc

[knpshkn]

Indeed, this is caused by parallel building. Thanks!
Now I'm faced with another issue

gcc  -Wall -W -Wno-strict-prototypes -Wno-implicit-fallthrough -Werror -Wno-deprecated-declarations -Wno-unused-result -g -Og -ggdb -DOSTYPE=linux -DOSLEVEL=0x04130000 -DOS="\"linux-4.19.0-27-amd64-x86_64\"" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DDEBUG -DWITH_PCRE2 -DPCRE2_CODE_UNIT_WIDTH=8 -DWITH_CRYPT -DWITH_PTHREAD -DWITH_EPOLL -DWITH_POLL -DWITH_SELECT -DWITH_IPC -I/build/root/event-driven-servers  -I/usr/include -c -o config.o /build/root/event-driven-servers/tac_plus-ng/config.c
/build/root/event-driven-servers/tac_plus-ng/config.c: In function ‘tac_script_parse_r’:
/build/root/event-driven-servers/tac_plus-ng/config.c:4687:32: error: ‘%s’ directive output may be truncated writing up to 16383 bytes into a region of size 8191 [-Werror=format-truncation=]
 4687 |  snprintf(buf, sizeof(buf), "\"%s%s\"", sym->buf, sep);
      |                                ^~
In file included from /usr/include/stdio.h:867,
                 from /build/root/event-driven-servers/tac_plus-ng/headers.h:78,
                 from /build/root/event-driven-servers/tac_plus-ng/config.c:59:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: ‘__builtin___snprintf_chk’ output between 4 and 16387 bytes into a destination of size 8192
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   68 |        __bos (__s), __fmt, __va_arg_pack ());
      |        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

[MarcJHuber]

Hi,

ok, seems easy, bf29887 should fix this.

Thanks,

Marc

[knpshkn]

Yes, fixed. Thank you!