MySQL Bugs: #33590: libevent fails to build on Solaris

Bug #33590	libevent fails to build on Solaris
Submitted:	30 Dec 2007 17:33	Modified:	17 Apr 2008 9:32
Reporter:	Brian Aker	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	6.0 (bk tip)	OS:	Solaris
Assigned to:		CPU Architecture:	Any

Description:
On:
SunOS bitters 5.11 snv_55b sun4v sparc SUNW,Sun-Fire-T1000

(Though I expect platform does not matter)

Configure:
 ./configure --with-libevent

...
checking for libevent... using bundled libevent
...

Then grep:
/* Define if your system supports event ports */
/* #undef HAVE_EVENT_PORTS */
/* If we want to use libevent and have connection pooling */
/* #undef HAVE_LIBEVENT */

Should have error'ed out since I made the request. 

How to repeat:
Repeat steps in description

Suggested fix:
First, do not bundle libevent, that is bad business. Bug fixes, local fixes, etc... just a bad idea. 

Always error when a configure option is requested, and it cannot be performed. 

./configure --help message on libevent, does not mention how to build with native.

Thank you for the report.

I can not repeat described behavior on Solaris 10 and last mysql-6.0 tree:

$cat config.log | grep -i event      
  $ ./configure --with-libevent
configure:41310: checking for libevent
configure:41341: result: using bundled libevent
<snip>
$cat include/config.h | grep -i event
/* Define if your system supports event ports */
#define HAVE_EVENT_PORTS 1
/* If we want to use libevent and have connection pooling */
#define HAVE_LIBEVENT 1
/* Define to 1 if you have the <sys/event.h> header file. */
/* #undef HAVE_SYS_EVENT_H */

Please indicate if you are using different tree.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Brian,

we still need feedback from you.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".