[Maria-developers] PIC build options and MariaDB
Hello, I noticed that the MySQL packages in Debian have PIC stuff in their alternative build arguments, see http://anonscm.debian.org/gitweb/?p=pkg-mysql/mysql-5.6.git;a=blob;f=debian/... http://anonscm.debian.org/gitweb/?p=pkg-mysql/mysql-5.5.git;a=blob;f=debian/... Anybody here who understands deeply the build arguments who could say if having these PIC additions is desirable? Also the MySQL rules file has a section like this: # See http://blogs.innodb.com/wp/2010/04/innodb-performance-aio-linux/ 67 # Also #659565 68 ifneq (,$(findstring linux-gnu,$(DEB_HOST_GNU_TYPE))) 69 USE_LINUX_NATIVE_AIO:=-DLINUX_NATIVE_AIO=ON 70 endif Should MariaDB use this too, is it valid for XtraDB? -- Check out our blog at http://seravo.fi/blog and follow @ottokekalainen
Am 02.04.2014 17:10, schrieb Otto Kekäläinen:
I noticed that the MySQL packages in Debian have PIC stuff in their alternative build arguments, see http://anonscm.debian.org/gitweb/?p=pkg-mysql/mysql-5.6.git;a=blob;f=debian/... http://anonscm.debian.org/gitweb/?p=pkg-mysql/mysql-5.5.git;a=blob;f=debian/...
Anybody here who understands deeply the build arguments who could say if having these PIC additions is desirable?
surely because you want the result below these days http://tk-blog.blogspot.co.at/2009/02/relro-not-so-well-known-memory.html * PIC * Full RELRO [root@rh:~]$ /usr/bin/hardening-check /usr/libexec/mysqld /usr/libexec/mysqld: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: yes
participants (2)
-
Otto Kekäläinen -
Reindl Harald