[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
On 12/6/2011 3:46 PM, David Holland wrote:
> On Tue, Dec 06, 2011 at 07:28:16AM +0100, John Marino wrote:
> >>> Log Message:
> >>> devel/kdesdk3: Fix for DragonFly
> >>> DragonFly needs devel/flex rather than USE_TOOLS+= lex in order to
> >>> build kdesdk3.
> >> Doesn't USE_TOOLS+=flex do that?
> > No, both lex and flex point to the same file: /usr/bin/lex
> > mk/tools/tools.DragonFly.mk:
> > TOOLS_PLATFORM.flex?= /usr/bin/lex
> > TOOLS_PLATFORM.lex?= /usr/bin/lex
> > which is actually kind of strange because on my system
> > /usr/bin/flex exists, but /usr/bin/lex does not.
> > Does this indicate an old mk file perhaps?
> I'm not sure exactly, but if it points to something that doesn't exist
> it's definitely wrong. Let's move this to tech-pkg.
> (I would think, also, that USE_TOOLS+=flex should get you flex,
> specifically, and USE_TOOLS+=lex should allow other implementations as
> well. But I guess that isn't the issue in this case.)
Ok, correction, DragonFly has lex, lex++, flex, flex++ on /usr/bin, so
it does point to an existing binary.
I gather that TOOL_PLATFORM.flex needs to be changed to "?=
/usr/bin/flex" to be correct.
The problem with kdesdk3 and lilipond involved a missing FlexLexer.h.
Will using flex bring FlexLexer.h into the wrappers?
Main Index |
Thread Index |