Date: Wed, 06 Aug 2014 13:14:35 +0200 From: Paul Herman <pherman@frenchfries.net> To: freebsd-stable@freebsd.org Subject: Re: Weird bmake behaviour from within installworld Message-ID: <53E20E1B.5020904@frenchfries.net> In-Reply-To: <86zjfjxq1x.fsf@nine.des.no> References: <86zjfjxq1x.fsf@nine.des.no>, <20140803193541.GA1839@lonrach.local>, <20140804094937.GA9720@roberto-aw.eurocontrol.fr>, <20140804104146.GB9720@roberto-aw.eurocontrol.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
[...note not subscribed...] > Ollivier Robert <roberto@keltia.freenix.fr> writes: > > ub_c_lex_destroy() in daemon.c is used through LEX_HAS_YYLEX_DESTROY > > but never defined. MFH issue? > > ub_c_lex_destroy() is in libunbound and is generated at build time by > flex, see /usr/obj/usr/src/lib/libundound/configlexer.c. It *should* be, but it isn't. This is because yylex_destroy() isn't in flex 2.5.4 (9-STABLE) but it is in 2.5.37 (10-STABLE). 9-STABLE: [pherman@cow ~]$ echo %% | lex -t | grep yylex_destroy [pherman@cow ~]$ flex -V flex version 2.5.4 [pherman@cow ~]$ nm /usr/obj/usr/src/lib/libunbound/configlexer.o | grep destroy [pherman@cow ~] 10-STABLE: [pherman@tom ~]$ echo %% | lex -t | grep yylex_destroy int yylex_destroy (void ); [...] [pherman@tom ~]$ flex -V flex 2.5.37 [pherman@tom ~]$ nm /usr/obj/usr/src/lib/libunbound/configlexer.o | grep destroy 0000000000003d80 T ub_c_lex_destroy Also, updating base flex to 2.5.37 didn't help me. I've found that removing / undef-ing: /* if lex has yylex_destroy */ #define LEX_HAS_YYLEX_DESTROY 1 from /usr/src/contrib/unbound/config.h allows the build to complete, although not sure what kind of side effects this causes. Cheers, -Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E20E1B.5020904>