Opened 18 years ago

Closed 18 years ago

Last modified 8 years ago

#852 closed defect (fixed)

mysql 4.0.20 doesn't configure against glibc 2.3.4

Reported by: stef@… Owned by: blfs-book@…
Priority: high Milestone:
Component: BOOK Version: ~CVS
Severity: normal Keywords: VERIFIED


One for the future, as it's not relevant for the current LFS release version (maybe you should put a "future" option in somewhere in the bug report screen!), however...

The configure script for mySQL greps for the string "Linuxthreads" in /usr/include/pthread.h

This string isn't present in the pthread.h shipping with glibc 2.3.4 (as used in LFS CVS).

Kludging the configure script to grep for something else (I used PTHREAD) makes it configure, build and run no problems.

Change History (9)

comment:1 by jim@…, 18 years ago

This has been discussed on lfs-hackers numerous times. Please search the mailling lists before creating a bug report. Just add the following to your configure line --with-named-thread-libs=-lpthread.

comment:2 by bdubbs@…, 18 years ago

No, please DO submit bugs like these. Bugzilla is how we track problems, not a mailing list.

comment:3 by Randy McMurchy, 18 years ago

BLFS instructions have been updated to build MySQL successfully against LFS-6.0, however the patch should be removed and --with-named-thread-libs=-lpthread should be passed instead.

comment:4 by Randy McMurchy, 18 years ago

Severity: blockernormal

comment:5 by igor@…, 18 years ago

4.0.21 still requires the patch.

comment:6 by Randy McMurchy, 18 years ago

Resolution: fixed
Status: newclosed

With the additional information provided by Igor in: this bug is being closed

comment:7 by igor@…, 18 years ago

After some googling I found out that you need to pass CPPFLAGS="-D_GNU_SOURCE" to configure script in addition to the --with-named-thread-libs=-lpthread switch in order to successfully compile MySQL.

comment:8 by igor@…, 18 years ago

Keywords: VERIFIED added

comment:9 by bdubbs@…, 8 years ago

Milestone: old

Milestone old deleted

Note: See TracTickets for help on using tickets.