After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 509360 - No checks for flex in configure script
No checks for flex in configure script
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.5.3
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2008-01-14 13:00 UTC by Wouter Bolsterlee (uws)
Modified: 2013-06-02 12:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for flex&bison config parameters (589 bytes, patch)
2011-12-16 13:15 UTC, Jury 		none Details | Review

Description Wouter Bolsterlee (uws) 2008-01-14 13:00:28 UTC 
The configure script does not check for flex, while the break builds if it's not available.

I'm trying to compile a pristine 1.5.3 tarball release.
Comment 1 Wouter Bolsterlee (uws) 2008-01-14 13:31:35 UTC 
The same goes for bison, it seems.
Comment 2 Jury 2011-12-16 13:15:24 UTC 
Created attachment 203674 [details] [review]
Patch for flex&bison config parameters

This patch fixes an issue with config-script, that ignores --flex and --bison parameters.
Pay attention to version - this patch is for 1.7.2 version.
Before patching execute
mv src/libdoxycfg.t src/libdoxycfg.t.in
Then run patch for both patch-files.

P.S. I'm really surprised this issue is not fixed since 2008.
Comment 3 Nicolas Dély 2012-01-26 10:09:35 UTC 
I've found the same issue when I've been passing --bison=bison-wrapper on 1.7.3
Comment 4 Ryan Schmidt 2012-03-31 02:49:24 UTC 
It's also important to check that the version of flex (and presumably) bison is new enough; the build fails on OS X Tiger for example using the system's rather old flex version. See https://trac.macports.org/ticket/33819
Comment 5 albert 2013-06-02 12:06:53 UTC 
Looking at the supplied patch and the current versions of the involved files it looks like to me that the patch has been or similar code has been integrated.

I think this problem has been solved in the mean time.
Comment 6 Dimitri van Heesch 2013-06-02 12:09:49 UTC 
Setting to fixed as suggested. Please reopen this bug report if you still see this issue with the latest version of doxygen. Add a self-contained example (source+config file in a zip or tar) if possible.