mirror of
https://github.com/MariaDB/server.git
synced 2025-01-18 21:12:26 +01:00
MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry.
amazon-web-servicesdatabasefulltext-searchgalerageographical-information-systeminnodbjsonmariadbmysqlrdbmsrelational-databasessqlstorage-enginevector-database
8a9c988122
Change "configure.in".
The branches for Tru64 (ex: OSF/1) and Linux are separated,
and for Linux 'getconf GNU_LIBPTHREAD_VERSION' is used to tell between Linuxthreads and NPTL.
configure.in:
Step 3 of the switch to support configuration with NPTL:
Change "configure.in".
1) Separate the branches checking for thread libraries on OSF/1 (now: Tru64) and on Linux,
as these are different things. In the Tru64 branch, remove the obsolete part for OSF/1 3.2,
because that is gone since long (about a decade?); we are at 5 now. Adapt the comment.
2) For Linux, the thread libraries are "Linuxthreads" (older) and "NPTL" (newer).
Until now, we cared only about "Linuxthreads", and we did so by checking a comment in
the header file '/usr/include/pthread.h'.
With NPTL as an alternative or only thread package, this is not secure any more,
there are distributions where the header file still contains that comment but the lib is NPTL.
For all current distributions, the way to check is the 'getconf' command.
On old distributions, 'getconf' exists but does not understand the 'GNU_LIBPTHREAD_VERSION'
parameter. It is unlikely that such an old system should have NPTL, so the header file check is
sufficient if the getconf inquiry fails.
For both Linuxthreads and NPTL, '-lpthread' is the linker option to use.
3) To detect problems as early as possible, on Linux a link test using '-lpthread' is done.
The code is copied from a later check where the thread functions are searched in '-lc',
'-lpthread', and '-lpthreads', but this later search would not be executed after the lib
was already determined. So if the test is not done here, it will be detected only during
the real build. This is too late.
|
||
|---|---|---|
| bdb | ||
| BitKeeper | ||
| BUILD | ||
| client | ||
| cmd-line-utils | ||
| dbug | ||
| Docs | ||
| extra | ||
| heap | ||
| include | ||
| innobase | ||
| isam | ||
| libmysql | ||
| libmysql_r | ||
| libmysqld | ||
| man | ||
| merge | ||
| myisam | ||
| myisammrg | ||
| mysql-test | ||
| mysys | ||
| ndb | ||
| netware | ||
| NEW-RPMS | ||
| os2 | ||
| pstack | ||
| regex | ||
| scripts | ||
| sql | ||
| sql-bench | ||
| sql-common | ||
| SSL | ||
| strings | ||
| support-files | ||
| tests | ||
| tools | ||
| VC++Files | ||
| vio | ||
| zlib | ||
| .bzrignore | ||
| .cvsignore | ||
| acinclude.m4 | ||
| config.guess | ||
| config.sub | ||
| configure.in | ||
| COPYING | ||
| depcomp | ||
| install-sh | ||
| ltconfig | ||
| ltmain.sh | ||
| Makefile.am | ||
| missing | ||
| mkinstalldirs | ||
| README | ||
This is a release of MySQL, a GPL (free) SQL database server (more licence information in the PUBLIC file and in the reference manual). Please read the "Upgrading from..." section in the manual first, if you are migrating from older versions of MySQL! The latest information about MySQL can be found at: http://www.mysql.com To see what it can do take a look at the features section in the manual. For installation instructions see the Installation chapter in the manual. For future plans see the TODO appendix in the manual. New features/bug fixes history is in the news appendix in the manual. For the currently known bugs/misfeatures (known errors) see the bugs appendix in the manual. For examples of SQL and benchmarking information see the bench directory. The manual mentioned above can be found in the Docs directory. The manual is available in the following formats: as plain ASCII text in Docs/manual.txt, in HTML format in Docs/manual_toc.html, as GNU Info in Docs/mysql.info and as PostScript in Docs/manual.ps. MySQL is brought to you by the MySQL team at MySQL AB For a list of developers and other contributors, see the Credits appendix in the manual. ************************************************************ IMPORTANT: Send bug (error) reports, questions and comments to the mailing list at mysql@lists.mysql.com Please use the 'mysqlbug' script when posting bug reports or questions about MySQL. mysqlbug will gather some information about your system and start your editor with a form in which you can describe your problem. Bug reports might be silently ignored by the MySQL maintainers if there is not a good reason included in the report as to why mysqlbug has not been used. A report that says 'MySQL does not work for me. Why?' is not considered a valid bug report. The mysqlbug script can be found in the 'scripts' directory of the distribution, that is '<where-you-installed-mysql>/scripts'.