Deutsch English Français Italiano |
<pan$e6e34$6159cfe7$17af853e$c2b3de67@linux.rocks> View for Bookmarking (what is this?) Look up another Usenet article |
From: Farley Flud <ff@linux.rocks> Subject: Another Success With GNU/Linux! Newsgroups: comp.os.linux.advocacy Mime-Version: 1.0 Message-Id: <pan$e6e34$6159cfe7$17af853e$c2b3de67@linux.rocks> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Lines: 52 Path: ...!2.eu.feeder.erje.net!feeder.erje.net!feeder1.feed.ams11.usenet.farm!feed.usenet.farm!tr1.eu1.usenetexpress.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!news.usenetexpress.com!not-for-mail Date: Sun, 22 Dec 2024 14:04:35 +0000 Nntp-Posting-Date: Sun, 22 Dec 2024 14:04:35 +0000 X-Received-Bytes: 1912 Organization: UsenetExpress - www.usenetexpress.com X-Complaints-To: abuse@usenetexpress.com Bytes: 2241 A new version of dictd, 1.13.3, is available. Gentoo, due to unfortunate manpower shortages (not enough volunteers), has lost the maintainer for dictd and so I had to build it myself. It failed. There were crazy errors: clientscan.c: No such file or directory WTF! Now, clientscan.c is actually created from clientscan.l via the flex scanner but somehow flex was not doing its job. I went back to the configure output (this is an autoconf build): checking for flex... flex checking for lex output file root... lex.yy checking for lex library... none needed checking for library containing yywrap... no configure: WARNING: yywrap not found; giving up on flex WTF! Flex contains "yywrap" but somehow the configure script wasn't able to find it. Rather than work through all that autoconf gobbledygook I just decided to modify the Makefile. That's because configure set one variable in the Makefile to NULL due to not finding yywrap: LEX = flex That's all it took! The package then built with no errors! Ha, ha, ha! I suppose that the developers of dictd fucked up the autoconf script because they are moving to a different build system called mk-configure: https://github.com/cheusov/mk-configure I consider mk-configure to be even more of a clusterfuck than autoconf. But this is why I LOVE GNU/Linux. There is always challenging excitement happening. -- Systemd: solving all the problems that you never knew you had.