can not login anymore after update

[M.W. van der Grient]

I have done what you suggested. But can not install Linux-PAM module
because of the build failure. I have tried 1.3.0 and a earlier version
1.2.1. But no luck:

d-function-cast -Wcast-align -Wcast-qual -Wmissing-declarations
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes
> -Wwrite-strings -Winline -Wshadow -MT pam_console_apply-modechange.o -MD
> -MP -MF .deps/pam_console_apply-modechange.Tpo -c -o
> pam_console_apply-modechange.o `test -f 'modechange.c' || echo
> './'`modechange.c
> mv -f .deps/pam_console_apply-modechange.Tpo
> .deps/pam_console_apply-modechange.Po
> gcc -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2
> -I../../libpam/include -I../../libpamc/include
>  -DLOCKDIR=\"/var/run/console\" -fpie -O2 -march=x86-64 -pipe -W -Wall
> -Wbad-function-cast -Wcast-align -Wcast-qual -Wmissing-declarations
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes
> -Wwrite-strings -Winline -Wshadow -MT pam_console_apply-regerr.o -MD -MP
> -MF .deps/pam_console_apply-regerr.Tpo -c -o pam_console_apply-regerr.o
> `test -f 'regerr.c' || echo './'`regerr.c
> mv -f .deps/pam_console_apply-regerr.Tpo .deps/pam_console_apply-regerr.Po
> bison -y -d -o configfile.tab.c -p _pc_yy configfile.y
> configfile.y: warning: 1 shift/reduce conflict [-Wconflicts-sr]
> sh ./sed-static configfile.tab.c
> flex -Cr -oconfigfile.lex.c -P_pc_yy configfile.l
> sh ./sed-static configfile.lex.c
> gcc -DHAVE_CONFIG_H -I. -I../..   -D_FORTIFY_SOURCE=2
> -I../../libpam/include -I../../libpamc/include
>  -DLOCKDIR=\"/var/run/console\" -fpie -O2 -march=x86-64 -pipe -W -Wall
> -Wbad-function-cast -Wcast-align -Wcast-qual -Wmissing-declarations
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes
> -Wwrite-strings -Winline -Wshadow -MT pam_console_apply-configfile.o -MD
> -MP -MF .deps/pam_console_apply-configfile.Tpo -c -o
> pam_console_apply-configfile.o `test -f 'configfile.c' || echo
> './'`configfile.c
> In file included from configfile.c:56:0:
> configfile.lex.c:23:15: error: static declaration of '_pc_yylex' follows
> non-static declaration
>  #define yyleng _pc_yyleng
>                ^
> configfile.lex.c:1091:28: note: in expansion of macro 'yylex'
>
>                             ^
> configfile.lex.c:1111:1: note: in expansion of macro 'YY_DECL'
>   */
>  ^~~
> configfile.lex.c:23:15: note: previous declaration of '_pc_yylex' was here
>  #define yyleng _pc_yyleng
>                ^
> configfile.lex.c:1089:12: note: in expansion of macro 'yylex'
>
>             ^
> In file included from configfile.c:57:0:
> configfile.y:325:1: warning: 'do_yyerror' defined but not used
> [-Wunused-function]
>  do_yyerror(const char *format, ...) {
>  ^~~~~~~~~~
> In file included from configfile.c:56:0:
> configfile.lex.c:11:24: warning: '_pc_yy_scan_string' defined but not used
> [-Wunused-function]
>  #define yy_scan_buffer _pc_yy_scan_buffer
>                         ^
> configfile.lex.c:2000:24: note: in expansion of macro 'yy_scan_string'
>   */
>                         ^
> In file included from configfile.c:56:0:
> configfile.lex.c:1624:16: warning: 'input' defined but not used
> [-Wunused-function]
>  #else
>                 ^
> configfile.lex.c:1581:17: warning: 'yyunput' defined but not used
> [-Wunused-function]
>
>                  ^
> make[3]: *** [Makefile:698: pam_console_apply-configfile.o] Error 1
> make[3]: Leaving directory '/usr/src/Linux-PAM-1.3.0/modules/pam_console'
> make[2]: *** [Makefile:436: all-recursive] Error 1
> make[2]: Leaving directory '/usr/src/Linux-PAM-1.3.0/modules'
> make[1]: *** [Makefile:483: all-recursive] Error 1
> make[1]: Leaving directory '/usr/src/Linux-PAM-1.3.0'
> make: *** [Makefile:415: all] Error 2
> Creating /var/log/lunar/compile/Linux-PAM-1.3.0.xz
> ! Problem detected during BUILD



2017-05-15 10:23 GMT+02:00 Stefan Wold <ratler at lunar-linux.org>:

> Hi,
>
> If Linux-PAM failed to build it should not have installed anything that
> would break the login. But it does sound like there's an actual problem
> with PAM, or something related to it. Maybe cracklib update broke Linux-PAM
> for you? Boot into single user mode and try to rebuild Linux-PAM.
>
> Cheers,
> Stefan
>
> On Mon, May 15, 2017 at 9:52 AM M.W. van der Grient <mwgrient69 at gmail.com>
> wrote:
>
>> I can not login anymore!
>> If I login as a regular user or root, I can enter my user name, but the
>> login gives back a prompt, not the expected password prompt.
>>
>> Linux-PAM is not updated because of a build error, can this be related?
>>
>> have a nice day! Marco
>> _______________________________________________
>> Lunar-dev mailing list
>> Lunar-dev at lunar-linux.org
>> http://lists.lunar-linux.org/cgi-bin/mailman/listinfo/lunar-dev
>
>
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://lists.lunar-linux.org/cgi-bin/mailman/listinfo/lunar-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lunar-linux.org/pipermail/lunar-dev/attachments/20170515/f2316bbe/attachment.html>