Installation de Mysql sous Gentoo

Après plusieurs tentaives pour installer Mysql sous Gentoo avec emerge sans succès, j'ai finalement installé Mysql manuellement.
J'ai suivi les étapes du fichier d'installation  :

• shell> groupadd mysql

• shell> useradd -r -g mysql mysql

• shell> cd /usr/local

• shell> tar zxvf /path/to/mysql-VERSION-OS.tar.gz

• shell> ln -s full-path-to-mysql-VERSION-OS mysql

• shell> cd mysql

• shell> chown -R mysql .

• shell> chgrp -R mysql .

• shell> scripts/mysql_install_db --user=mysql

J'ai rencontré l'erreur suivante :

Installing MySQL system tables..../bin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

Pour résoudre ce problème, j'ai installé libaio avec emerge dev-libs/libaio

• shell> chown -R root .

• shell> chown -R mysql data

• shell> cp support-files/my-medium.cnf /etc/my.cnf

• shell> bin/mysqld_safe --user=mysql &

Dans le fichier d'erreur monfichier.err qui se trouve dans le répertoire /usr/local/mysql/data/
J'avais l'erreur suivante : Can't open and lock privilege tables: Table 'mysql.user' doesn't exist


J'ai résolu le problème avec mysql_install_db --user=mysql --ldata=/usr/local/mysql/data/


Remarque :
J'ai rencontré la même erreur en faisant
GRANT ALL ON tbl.* TO 'user'@'localhost' IDENTIFIED BY 'tbl';
==> Erreur Mysql.User doesn't exist
Une veille version de Mysql existait sur mon poste, j'ai du l'effacer et relancer la commande suivante :

./scripts/mysql_install_db --user=mysql --ldata=/usr/local/mysql/data/
Installing MySQL system tables...2013-06-03 13:28:20 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-06-03 13:28:20 7779 [Note] InnoDB: The InnoDB memory heap is disabled
2013-06-03 13:28:20 7779 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation
2013-06-03 13:28:20 7779 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-06-03 13:28:20 7779 [Note] InnoDB: Using Linux native AIO
2013-06-03 13:28:20 7779 [Note] InnoDB: Not using CPU crc32 instructions
2013-06-03 13:28:20 7779 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-06-03 13:28:20 7779 [Note] InnoDB: Completed initialization of buffer pool
2013-06-03 13:28:20 7779 [Note] InnoDB: Highest supported file format is Barracuda.
2013-06-03 13:28:20 7779 [Note] InnoDB: The log sequence numbers 1600614 and 1600614 in ibdata files do not match the log sequence number 1601046 in the ib_logfiles!
2013-06-03 13:28:20 7779 [Note] InnoDB: Database was not shutdown normally!
2013-06-03 13:28:20 7779 [Note] InnoDB: Starting crash recovery.
2013-06-03 13:28:20 7779 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-06-03 13:28:20 7779 [Note] InnoDB: Restoring possible half-written data pages
2013-06-03 13:28:20 7779 [Note] InnoDB: from the doublewrite buffer...
2013-06-03 13:28:20 7779 [Note] InnoDB: 128 rollback segment(s) are active.
2013-06-03 13:28:20 7779 [Note] InnoDB: Waiting for purge to start
2013-06-03 13:28:20 7779 [Note] InnoDB: 5.6.11 started; log sequence number 1601046
2013-06-03 13:28:24 7779 [Note] Binlog end
2013-06-03 13:28:24 7779 [Note] InnoDB: FTS optimize thread exiting.
2013-06-03 13:28:24 7779 [Note] InnoDB: Starting shutdown...
2013-06-03 13:28:25 7779 [Note] InnoDB: Shutdown completed; log sequence number 1626426
OK

Filling help tables...2013-06-03 13:28:25 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-06-03 13:28:25 7804 [Note] InnoDB: The InnoDB memory heap is disabled
2013-06-03 13:28:25 7804 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation
2013-06-03 13:28:25 7804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-06-03 13:28:25 7804 [Note] InnoDB: Using Linux native AIO
2013-06-03 13:28:25 7804 [Note] InnoDB: Not using CPU crc32 instructions
2013-06-03 13:28:25 7804 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-06-03 13:28:25 7804 [Note] InnoDB: Completed initialization of buffer pool
2013-06-03 13:28:25 7804 [Note] InnoDB: Highest supported file format is Barracuda.
2013-06-03 13:28:25 7804 [Note] InnoDB: 128 rollback segment(s) are active.
2013-06-03 13:28:25 7804 [Note] InnoDB: Waiting for purge to start
2013-06-03 13:28:25 7804 [Note] InnoDB: 5.6.11 started; log sequence number 1626426
2013-06-03 13:28:25 7804 [Note] Binlog end
2013-06-03 13:28:25 7804 [Note] InnoDB: FTS optimize thread exiting.
2013-06-03 13:28:25 7804 [Note] InnoDB: Starting shutdown...
2013-06-03 13:28:27 7804 [Note] InnoDB: Shutdown completed; log sequence number 1626436
OK

...
Vous devez voir OK apparaîttre !

CONFIG_DEVTMPFS: is not set when it should be

Problème

emerge  sys-fs/udev

* Messages for package sys-fs/udev-200:

 *   CONFIG_DEVTMPFS:    is not set when it should be.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.

Solution

Il faut modifier son kernel de la manière suivante :

 Device Drivers-> Generic Driver 
* Maintain a devtmpfs filesystem to mount at /dev.  

 For getting the devfs automatically mounted at boot time it makes sense to also enable the option  
* Automount devtmpfs at /dev

Chromium 26.0.1410.43 Failed

Problème

 J'ai essayé de compiler la version 26.0.1410.43 de Chromium mais sans succès

Solution

Je n'ai pas trouvé d'autre solution que de downgrader la version comme ceci :


 vi /etc/portage/package.mask.
 >www-client/chromium-23.0.1271.97




Merci à http://mindspill.net/computing/linux-notes/gentoo/how-to-downgrade-a-gentoo-package/

CONFIG_DM_CRYPT: is not set (required for cryptsetup)

Problème

* Messages for package sys-fs/cryptsetup-1.4.3:

*   CONFIG_DM_CRYPT:   is not set (required for cryptsetup)

*

* Please check to make sure these options are set correctly.

* Failure to do so may cause unexpected problems.

* This ebuild introduces a new set of scripts and configuration

* than the last version. If you are currently using /etc/conf.d/cryptfs

* then you *MUST* copy your old file to:

* /etc/conf.d/dmcrypt

* Or your encrypted partitions will *NOT* work.

* Please see the example for configuring a LUKS mountpoint

* in /etc/conf.d/dmcrypt

*

* If you are using baselayout-2 then please do:

* rc-update add dmcrypt boot

* This version introduces a command line arguement 'key_timeout'.

* If you want the search for the removable key device to timeout

* after 10 seconds add the following to your bootloader config:

* key_timeout=10

* A timeout of 0 will mean it will wait indefinitely.

*

* Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use

* a compatibility mode when using cryptsetup-1.1.x. This can be

* done by specifying the cipher (-c), key size (-s) and hash (-h).

* For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup

Solution

- Mettre à jour le kernel

- Dans la config du kernel : device drivers -> Multiple devices driver support (RAID and LVM) -> Crypt target support 

- emerge sys-fs/cryptsetup

Liens :

- http://forums.gentoo.org/viewtopic-t-860101.html

- http://doc.ubuntu-fr.org/cryptsetup

sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2

Problème :

emerge -p system
[blocks B      ] <sys-apps/sysvinit-2.88-r4 ("<sys-apps/sysvinit-2.88-r4" is blocking sys-apps/util-linux-2.22.2)

Solution :

Cela signifie qu'une veille version de sys-apps/sysvinit bloque sys-apps/util-linux.
Il faut donc mettre à jour sys-apps/sysvinit avant sys-apps/util-linux.
Vous pouvez exécuter la commande suivante :


emerge -uDv1 sysvinit util-linux



See http://forums.gentoo.org/viewtopic-t-952770-start-0-postdays-0-postorder-asc-highlight-.html?sid=39638f320d5e82ad9f36be3479918c87

Upgrading udev-171-r9 to udev-197-r3 on Gentoo

Bonjour à tous.
Si vous avez des soucis pour upgradez udev.Vous pouvez allez voir ce blog très bien fait : http://blog.yjl.im/2013/01/upgrading-udev-171-r9-to-udev-197-r3-on.html
Il vous expliquera comment migrer de version.

Problem emerging firefox-10.0.11 with libpng

Problème :

Récemment, j'ai eu un problème en compilant firefox 10.0.11
Le problème était le suivant :

[i]checking for png_get_acTL in -lpng... yes
configure: error: --with-system-png requested but no working libpng found
*** Fix above errors and then restart with               "make -f client.mk build"
make[2]: *** [configure] Error 1
make[2]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.11/work/mozilla-esr10'
make[1]: *** [obj-i686-pc-linux-gnu/Makefile] Error 2
make[1]: Leaving directory `/var/tmp/portage/www-client/firefox-10.0.11/work/mozilla-esr10'
make: *** [build] Error 2
emake failed
 * ERROR: www-client/firefox-10.0.11 failed (compile phase):
 *   emake failed
 *
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 7029:  Called die
 * The specific snippet of code:
 *           CC="$(tc-getCC)" CXX="$(tc-getCXX)" LD="$(tc-getLD)" MOZ_MAKE_FLAGS="${MAKEOPTS}" emake -f client.mk || die "emake failed";
 *
 * If you need support, post the output of `emerge --info '=www-client/firefox-10.0.11'`,
 * the complete build

Solution :

Il y a avait un conflit avec une version antérieur de libpng.
Pour résoudre le problème, j'ai fait le ménage de tout ce qui concernait libpng dans /usr/local/include et usr/local/lib.Merci à ssuominenpour m'avoir aider à résoudre ce problème :  http://forums.gentoo.org/viewtopic-p-7215412.html#7215412