We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Problem z instalacją Mysql


borec
27-09-2008, 10:46
Kod:
/usr/lib64/libssl.so: file not recognized: File format not recognized
Chyba jednak 64bit (nowe celerony też są 64bit).

Zrób revdep-rebuild, jeśli nic nie przekompiluje spróbuj przekompilować openssl (emerge -av openssl).

luckan
26-09-2008, 18:35
Oto zawartość końcowa logu z kompilacji
Kod:
sql_do.o procedure.o item_uniq.o sql_test.o log.o log_event.o init.o derror.o sql_acl.o unireg.o des_key_file.o discover.o time.o opt_range.o opt_sum.o records.o filesort.o handler.o ha_heap.o ha_myisam.o ha_myisammrg.o ha_berkeley.o ha_innodb.o ha_ndbcluster.o ha_ndbcluster_cond.o sql_db.o sql_table.o sql_rename.o sql_crypt.o sql_load.o mf_iocache.o field_conv.o sql_show.o sql_udf.o sql_analyse.o sql_cache.o slave.o sql_repl.o sql_union.o sql_derived.o client.o sql_client.o mini_client_errors.o pack.o stacktrace.o repl_failsafe.o sql_olap.o sql_view.o gstream.o spatial.o sql_help.o sql_cursor.o tztime.o my_time.o my_user.o my_decimal.o sp_head.o sp_pcontext.o sp_rcontext.o sp.o sp_cache.o parse_file.o sql_trigger.o ha_example.o ha_archive.o ha_tina.o ha_blackhole.o ha_federated.o  ../innobase/usr/libusr.a ../innobase/srv/libsrv.a ../innobase/dict/libdict.a ../innobase/que/libque.a ../innobase/srv/libsrv.a ../innobase/ibuf/libibuf.a ../innobase/row/librow.a ../innobase/pars/libpars.a ../innobase/btr/libbtr.a ../innobase/trx/libtrx.a ../innobase/read/libread.a ../innobase/usr/libusr.a ../innobase/buf/libbuf.a ../innobase/ibuf/libibuf.a ../innobase/eval/libeval.a ../innobase/log/liblog.a ../innobase/fsp/libfsp.a ../innobase/fut/libfut.a ../innobase/fil/libfil.a ../innobase/lock/liblock.a ../innobase/mtr/libmtr.a ../innobase/page/libpage.a ../innobase/rem/librem.a ../innobase/thr/libthr.a ../innobase/sync/libsync.a ../innobase/data/libdata.a ../innobase/mach/libmach.a ../innobase/ha/libha.a ../innobase/dyn/libdyn.a ../innobase/mem/libmem.a ../innobase/sync/libsync.a ../innobase/ut/libut.a ../innobase/os/libos.a ../innobase/ut/libut.a -lrt ../myisam/libmyisam.a ../myisammrg/libmyisammrg.a ../heap/libheap.a ../vio/libvio.a ../mysys/libmysys.a ../dbug/libdbug.a ../regex/libregex.a ../strings/libmystrings.a -lz -ldl -L/usr/lib64 -lssl -lcrypto -lpthread -lcrypt -lnsl -lm -lpthread
/usr/lib64/libssl.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
make[4]: *** [mysqld] B��d 1
make[4]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql/sql'
make[3]: *** [all-recursive] B��d 1
make[3]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql/sql'
make[2]: *** [all] B��d 2
make[2]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql/sql'
make[1]: *** [all-recursive] B��d 1
make[1]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql'
make: *** [all] B��d 2
 * 
 * ERROR: dev-db/mysql-5.0.60-r1 failed.
 * Call stack:
 *      ebuild.sh, line 1701:  Called dyn_compile
 *      ebuild.sh, line 1039:  Called qa_call 'src_compile'
 *      ebuild.sh, line   44:  Called src_compile
 *      ebuild.sh, line 1383:  Called mysql_src_compile
 *   mysql.eclass, line  648:  Called die
 * The specific snippet of code:
 *   	emake || die "emake failed"
 *  The die message:
 *   emake failed
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-db/mysql-5.0.60-r1/temp/build.log'.
 *
czytalem poprzedni posta ale nie wiem czy może mi pomóc.

mlodszy
26-09-2008, 17:33
Kod:
A complete build log is located at '/var/tmp/portage/dev-db/mysql-5.0.60-r1/temp/build.log'.
Pokaz koniec z bledem

Przeczytaj jeszcze o tym: http://gentoo-wiki.com/Advanced_Emerge_World

Zrob aktualizacje.

luckan
26-09-2008, 16:43
to był Celeron, a więc 32bity.
Jak znam życie to czeka mnie reinstalka serwera.
Nie będzie to takie straszne ponieważ nic jeszcze na nim nie było.
To jest serwer pod ffmpeg i przecieram szlaki, jeśli chodzi o dystrybucje gentoo :/
Zwykle pracuje w suse 10,3.

borec
26-09-2008, 14:56
64bit? Jaki procesor? Mogę Ci zrobić paczkę.

luckan
26-09-2008, 11:24
Witam. Mam mały problem z mysql na dedyku z gentoo.
Zanim dotarłem do instrukcji postępownia z mysql na dedyku http://pomoc.ovh.pl/MysqlProblemyIRozwiazania

Zrobiłem reinstalacje, na tyle skutecznie że zostałem wogóle bez mysql.
Czy ktoś wie jak zainstlować poprawnie mysql.

Przy normalnym trybie instalacji emerg mysql na końcu pojawia się błąd:/
Kod:
make[4]: *** [mysqld] Bł±d 1
make[4]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql/sql'
make[3]: *** [all-recursive] Bł±d 1
make[3]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql/sql'
make[2]: *** [all] Bł±d 2
make[2]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql/sql'
make[1]: *** [all-recursive] Bł±d 1
make[1]: Leaving directory `/var/tmp/portage/dev-db/mysql-5.0.60-r1/work/mysql'
make: *** [all] Bł±d 2
 [31;01m*[0m 
 [31;01m*[0m ERROR: dev-db/mysql-5.0.60-r1 failed.
 [31;01m*[0m Call stack:
 [31;01m*[0m      ebuild.sh, line 1701:  Called dyn_compile
 [31;01m*[0m      ebuild.sh, line 1039:  Called qa_call 'src_compile'
 [31;01m*[0m      ebuild.sh, line   44:  Called src_compile
 [31;01m*[0m      ebuild.sh, line 1383:  Called mysql_src_compile
 [31;01m*[0m   mysql.eclass, line  648:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m   	emake || die "emake failed"
 [31;01m*[0m  The die message:
 [31;01m*[0m   emake failed
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant.
 [31;01m*[0m A complete build log is located at '/var/tmp/portage/dev-db/mysql-5.0.60-r1/temp/build.log'.
 [31;01m*[0m