Hi, Has anyone been able to build MySQL 4.0 source using pgcc? I tried for several hours with different setting in each try without any success. MySQL 4.0 alpha does compile, but it refuses to start, dumping the same error output each time such attempt is made:
******* Being error output ******* InnoDB: The first specified data file /usr/local/mysql/data/ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file /usr/local/mysql/data/ibdata1 size to 67108864 InnoDB: Database physically writes the file full: wait... InnoDB: Log file /usr/local/mysql/data/ib_logfile0 did not exist: new to be created InnoDB: Setting log file /usr/local/mysql/data/ib_logfile0 size to 5242880 InnoDB: Log file /usr/local/mysql/data/ib_logfile1 did not exist: new to be created InnoDB: Setting log file /usr/local/mysql/data/ib_logfile1 size to 5242880 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: creating foreign key constraint system tables InnoDB: Assertion failure in thread 1024 in file dict0crea.c line 1115 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16773120 record_buffer=131072 sort_buffer=2097144 max_used_connections=0 max_connections=1000 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2192372 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Bogus stack limit or frame pointer, fp=0xbfffe7f8, stack_bottom=0x776f6c6c, thread_stack=65536, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x615f7861 is invalid pointer thd->thread_id=-185339151 ******* End of error out put ******* I found a message by Gilles in the list stating exactly the same problem. Is this a known bug or are there several compiler setting I should pay attention to? The above error disappears if I compile the source with gcc. Build environment is of following: OS: Red Hat 7.1 (kernel 2.4.3-12) Compiler: pgcc-2.95.2 19991024 (release) Compiler setting: CFLAGS="-O3 -mpentium -mstack-align-double" CXX=gcc CXXFLAGS="-O3 -mpentium -mstack-align-double -felide-constructors -fno-exceptions -fno-rtti" configure setting: --prefix=/usr/local/mysql-4.0.0-alpha-source --disable-shared --enable-assembler --with-extra-charsets=none --with-mysqld-ldflags=-a ll-static --with-openssl --with-innodb --without-debug Regards, Jindo --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
