flex: update to 2.5.39

[rurban@…]

See ​http://patchwork.openembedded.org/patch/68029/

diff -bu ./Makefile.am~ ./Makefile.am
--- ./Makefile.am~	2014-03-26 13:46:44.000000000 +0100
+++ ./Makefile.am	2015-01-03 11:47:43.000000000 +0100
@@ -73,13 +73,13 @@
 	libmain.c \
 	libyywrap.c

-libfl_la_LDFLAGS = -no-undefined -version-info @SHARED_VERSION_INFO@
+libfl_la_LDFLAGS = -all-static -no-undefined -version-info @SHARED_VERSION_INFO@

 libfl_pic_la_SOURCES = \
 	libmain.c \
 	libyywrap.c

-libfl_pic_la_LDFLAGS = -no-undefined -version-info @SHARED_VERSION_INFO@
+libfl_pic_la_LDFLAGS = -all-static -no-undefined -version-info @SHARED_VERSION_INFO@

 noinst_HEADERS = \
 	flexdef.h \
./conf.in

[larryv (Lawrence Velázquez)]

Why would we want this? Our flex port does not appear to install any shared libraries.

[rurban@…]

Why would we want this?

flex is 2 versions behind. we have still 2.5.37. 2.5.39 requires now this automake patch to compile to static libs only.

Our flex port does not appear to install any shared libraries.

Yes. That's why we need this patch. Upstream also.

flex cannot be used as shared lib by design on most platforms. yylex is always external (user-provided), and only some systems allow unresolved symbols in shared libs.

[ryandesign (Ryan Carsten Schmidt)]

flex is 2 versions behind. we have still 2.5.37. 2.5.39 requires now this automake patch to compile to static libs only.

So our current flex 2.5.37 works fine, but you would like us to update to 2.5.39, which doesn't work unless it's patched. I propose this: report this problem to the developers of flex so that they can fix it in the appropriate way (because I'm not sure I'm qualified to judge whether the fix you have proposed is the correct one). I see ​one report about this in the flex bug tracker already, but the fix proposed there is different. When the developers release a new version of flex that once again works on OS X, then we will update the port to that version.

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

2.6.0 was just released which reports to fix this issue.

[ryandesign (Ryan Carsten Schmidt)]

Replying to khindenburg@…:

2.6.0 was just released which reports to fix this issue.

r142999