Re: `gmake test` probs Solaris9 for M. 4.1.4.
On Fri, 9 Sep 2005, Michael Stassen wrote: With mysql 4.1.12, `make -n test` reveals cd mysql-test; ./mysql-test-run ./mysql-test-run --ps-protocol For the record, here's what I got on Solaris 9 for 4.1.13 neelix hgs 18 % cd mysql-test ./mysql-test-run --force Installing Test Databases Removing Stale Files Installing Master Databases running ../sql/mysqld --no-defaults --bootstrap --skip-grant-tables --basedir=. --datadir=./var/master-data --skip-innodb --skip-ndbcluster --skip-bdb --language=../sql/share/english/ --character-sets-dir=../sql/share/charsets/ Installing Slave Databases running ../sql/mysqld --no-defaults --bootstrap --skip-grant-tables --basedir=. --datadir=./var/slave-data --skip-innodb --skip-ndbcluster --skip-bdb --language=../sql/share/english/ --character-sets-dir=../sql/share/charsets/ Manager disabled, skipping manager start. Loading Standard Test Databases Starting Tests TESTRESULT --- alias [ pass ] alter_table[ pass ] analyse[ pass ] analyze[ pass ] ansi [ pass ] archive[ skipped ] auto_increment [ pass ] backup [ pass ] bdb-alter-table-1 [ skipped ] bdb-alter-table-2 [ skipped ] bdb-crash [ skipped ] bdb-deadlock [ skipped ] bdb[ skipped ] bdb_cache [ skipped ] bench_count_distinct [ pass ] bigint [ pass ] binary [ pass ] blackhole [ skipped ] bool [ pass ] bulk_replace [ pass ] case [ pass ] cast [ pass ] check [ pass ] comments [ pass ] compare[ pass ] connect[ pass ] consistent_snapshot[ pass ] constraints[ pass ] count_distinct [ pass ] count_distinct2[ pass ] count_distinct3[ pass ] create [ pass ] create_select_tmp [ pass ] csv[ skipped ] ctype_big5 [ skipped ] ctype_collate [ pass ] ctype_cp1250_ch[ skipped ] ctype_cp1251 [ pass ] ctype_cp932[ skipped ] ctype_create [ pass ] ctype_latin1 [ pass ] ctype_latin1_de[ pass ] ctype_latin2 [ pass ] ctype_many [ skipped ] ctype_mb [ pass ] ctype_recoding [ pass ] ctype_sjis [ skipped ] ctype_tis620 [ skipped ] ctype_uca [ skipped ] ctype_ucs [ skipped ] ctype_ucs_binlog [ skipped ] ctype_ujis [ skipped ] ctype_utf8 [ pass ] date_formats [ pass ] delayed[ pass ] delete [ pass ] derived[ pass ] dirty_close[ pass ] distinct [ pass ] drop [ pass ] drop_temp_table[ pass ] empty_table[ pass ] endspace [ pass ] errors [ pass ] exampledb [ skipped ] explain[ pass ] flush [ pass ] flush_block_commit [ pass ] flush_table[ pass ] foreign_key[ pass ] fulltext [ pass ] fulltext2 [ pass ] fulltext_cache [ pass ] fulltext_distinct [ pass ] fulltext_left_join [ pass ] fulltext_multi [ pass ] fulltext_order_by [ pass ] fulltext_update[ pass ] fulltext_var [ pass ] func_compress [ pass ] func_concat[ pass ] func_crypt [ pass ] func_date_add [ pass ] func_default [ pass ] func_des_encrypt [ skipped ] func_encrypt [ skipped ] func_encrypt_nossl [ pass ] func_equal [ pass ] func_gconcat [ pass ] func_group [ pass ] func_if[ pass ] func_in[ pass ] func_isnull[ pass ] func_like [ pass ] func_math [ pass ] func_misc [ pass ] func_op[ pass ] func_regexp
Re: `gmake test` probs Solaris9 for M. 4.1.4.
Hi Hugh, all,
sorry about the delay.
Hugh Sasse wrote:
On Fri, 9 Sep 2005, Joerg Bruehe wrote:
Michael,
you beat me in replying, and saved me from typing the analysis - thanks!
Michael Stassen wrote:
[[...]]
The test suite is broken.
Well, I would not put it that way - a diplomatic wording is:
The tool to run the test suite does not run as it should.
I understand that the effect for Hugh and you is the same ;-)
Nobody was claiming *deliberate* breakage! :-)
Neither did I get it that way - no offence taken. :-)
[...]
The specific error causing your and Hugh's problem, the incorrect
skipping of tests which are not applicable to the server to be tested,
has been fixed, but maybe this version has not yet been pushed to the
4.1 tree.
Can we grab the new version off the web (CVSweb or similar?)
AIUI, it is pushed to the 4.1 tree, so a current tree snapshot should
include it. But I cannot identify an individual change as beint _that_
correction. From a discussion about this problem, it was a different
handling of process exit codes in Perl and shell that made the skip fail.
somewhere? If it is feasible for me I'd like to translate it to
Ruby to give you that much wider coverage. Depends if my Perl
fluency is sufficient, etc. Whether {you, the committee, ???} accept
the contribution is another matter entirely, of course.
Until now, we have no Ruby code in the server and the various tools,
including the build tools. As using a new language would require the
corresponding tools to be installed on all build platforms, the
advantages have to be very great to outweigh that effort.
We have not yet decided whether this script will remain a Perl script or
will even be transformed to C later. Given the development speed in
Perl, we would have to finalize it first.
As several of our build tools are written in Perl, we cannot easily drop
that language.
What are the advantages of Ruby? (off-topic, personal mail please)
Regards,
Jörg
--
Joerg Bruehe, Senior Production Engineer
MySQL AB, www.mysql.com
Office: (+49 30) 417 01 487 VoIP: [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: `gmake test` probs Solaris9 for M. 4.1.4.
I've see no reply to this and I checked the archives, so please excuse my resubmitting it. Maybe I shouldn't be using 4.1.14 but 4.0.x? Thank you, Hugh On Wed, 7 Sep 2005, Hugh Sasse wrote: Attempts to do make test prior to installation, to check that I'm installing something workable, give: quote neelix hgs 63 % gmake test cd mysql-test; perl mysql-test-run.pl perl mysql-test-run.pl --ps-protocol No ndbcluster support Killing Possible Leftover Processes Removing Stale Files Installing Master Databases Installing Master Databases Installing Slave Databases Installing Slave Databases Installing Slave Databases === Finding Tests in the 'main' suite Starting Tests in the 'main' suite TESTRESULT --- alias [ pass ] alter_table [ pass ] analyse [ pass ] analyze [ pass ] ansi[ pass ] archive [ fail ] Errors are (from /scratch/hgs/mysql-4.1.14/mysql-test/var/log/mysqltest-time) : This test is not supported by this installation mysqltest returned unexpected code 15872, it has probably crashed (the last lines may be the most important ones) Aborting: archive failed. To continue, re-run with '--force'. Ending Tests Shutting-down MySQL daemon Master(s) shutdown finished Slave(s) shutdown finished gmake: *** [test] Error 1 neelix hgs 64 % /quote So, firstly, invoke what with '--force'? You don't get anything useful if you pass that to make Also, how can I tell if InnoDB built OK? I'm doing this for use with Ruby on Rails, and I need it to be in a separate directory from the version we already have (3.x) used by others. I modified mysql-4.1.14/BUILD/compile-solaris-sparc thusly neelix hgs 81 % display_diffs.rb . --- ./compile-solaris-sparc.orig2005-08-17 18:06:41.0 +0100 +++ ./compile-solaris-sparc 2005-09-06 18:36:25.386697000 +0100 @@ -11,6 +11,6 @@ (cd gemini aclocal autoheader aclocal automake autoconf) fi -CFLAGS=-g -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa CXX=gcc CXXFLAGS=-Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Woverloaded-virtual -Wsign-promo -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor -felide-constructors -fno-exceptions -fno-rtti -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa -g ./configure --prefix=/usr/local/mysql --enable-assembler --with-extra-charsets=complex --enable-thread-safe-client +CFLAGS=-g -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa CXX=gcc CXXFLAGS=-Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Woverloaded-virtual -Wsign-promo -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor -felide-constructors -fno-exceptions -fno-rtti -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa -g ./configure --prefix=/usr/local/mysql --enable-assembler --with-extra-charsets=complex --enable-thread-safe-client --with-tcp-port=3308 --with-unix-socket-path=/tmp/mysql4.sock --prefix=/usr/local/mysql-4.1.14 gmake -j 4 neelix hgs 82 % and I invoked the script directly, and also tried with bash. Not sure what else to pass on. GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for sparc-sun-solaris2.9 gcc (GCC) 3.4.3 Thank you Hugh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: `gmake test` probs Solaris9 for M. 4.1.4.
Hugh, I get the same thing on Mac OS X 10.3.9. My thinking was that rather than replying with an unhelpful Me too, I would do some digging and then reply with what I found. I realize now that left you hanging (sorry), so I'll report what I've found so far. The test suite is broken. The archive test is meant to test the archive table engine, but the archive engine is not built into mysql by default. You have to add the --with-archive-storage-engine if you want it. You didn't do that, so the archive test should have been skipped. With mysql 4.1.12, `make -n test` reveals cd mysql-test; ./mysql-test-run ./mysql-test-run --ps-protocol With 4.1.14, that has changed to cd mysql-test; perl mysql-test-run.pl perl mysql-test-run.pl --ps-protocol Apparently, the test program shell script, mysql-test-run, has been rewritten as a perl script, though there is no mention of this in the change log http://dev.mysql.com/doc/mysql/en/news-4-1-x.html. A quick glance at the source shows that the perl script is not finished -- it has quite a few commented-out, fix me sections. You still have a couple of options to test your build. You can run the new test suite with the --force option. Do what make would do, `cd mysql-test`, then `perl mysql-test-run.pl --force`. You will see that every test that should have been skipped will instead be run and fail (archive, the bdb tests, blackhole, csv, example, func_des_encrypt, isam, the ndb tests, openssl_1, raid, and so on). If every test passes except for tests of things you don't have, you should be OK. In particular, there are a set of innodb tests which should answer your question about whether or not innodb is working in your build. There's a second way, which I think is better. It turns out that the old shell-script test suite is still built. Hence, you can still test the old way. cd mysql-test ./mysql-test-run --force This will properly skip tests of features not compiled in. Note that I added --force because, at least in my case, the new embedded test, not_embedded_server, is run and fails. I'm not yet sure if that should have been skipped. As the old test script is still built and the new test script is unfinished, undocumented, and broken, I am suspicious that the real problem is that make was prematurely (accidentally?) changed to use the new one before it was ready. I've copied the bugs list in hopes of an answer. Michael P.S. Out of curiosity, why did you find it necessary to edit BUILD/compile-solaris-sparc? Couldn't you make the changes you wanted with options to configure? Hugh Sasse wrote: I've see no reply to this and I checked the archives, so please excuse my resubmitting it. Maybe I shouldn't be using 4.1.14 but 4.0.x? Thank you, Hugh On Wed, 7 Sep 2005, Hugh Sasse wrote: Attempts to do make test prior to installation, to check that I'm installing something workable, give: quote neelix hgs 63 % gmake test cd mysql-test; perl mysql-test-run.pl perl mysql-test-run.pl --ps-protocol No ndbcluster support Killing Possible Leftover Processes Removing Stale Files Installing Master Databases Installing Master Databases Installing Slave Databases Installing Slave Databases Installing Slave Databases === Finding Tests in the 'main' suite Starting Tests in the 'main' suite TESTRESULT --- alias [ pass ] alter_table [ pass ] analyse [ pass ] analyze [ pass ] ansi[ pass ] archive [ fail ] Errors are (from /scratch/hgs/mysql-4.1.14/mysql-test/var/log/mysqltest-time) : This test is not supported by this installation mysqltest returned unexpected code 15872, it has probably crashed (the last lines may be the most important ones) Aborting: archive failed. To continue, re-run with '--force'. Ending Tests Shutting-down MySQL daemon Master(s) shutdown finished Slave(s) shutdown finished gmake: *** [test] Error 1 neelix hgs 64 % /quote So, firstly, invoke what with '--force'? You don't get anything useful if you pass that to make Also, how can I tell if InnoDB built OK? I'm doing this for use with Ruby on Rails, and I need it to be in a separate directory from the version we already have (3.x) used by others. I modified mysql-4.1.14/BUILD/compile-solaris-sparc thusly neelix hgs 81 % display_diffs.rb . --- ./compile-solaris-sparc.orig2005-08-17 18:06:41.0 +0100 +++ ./compile-solaris-sparc 2005-09-06 18:36:25.386697000 +0100 @@ -11,6 +11,6 @@ (cd gemini aclocal autoheader aclocal automake autoconf) fi -CFLAGS=-g -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -O3
Re: `gmake test` probs Solaris9 for M. 4.1.4.
On Fri, 9 Sep 2005, Michael Stassen wrote: Hugh, I get the same thing on Mac OS X 10.3.9. My thinking was that rather than replying with an unhelpful Me too, I would do some digging and then reply with what I found. I realize now that left you hanging (sorry), so I'll report what I've found so far. Ok, thanks for this report, which is in plenty of detail, even if it is so far :-) The test suite is broken. Who guards the guards? :-) The archive test is meant to test the archive table engine, but the archive engine is not built into mysql by default. You have to add the --with-archive-storage-engine if you want it. You didn't do that, so the I'm not sure what it is, so I probably don't need it. archive test should have been skipped. With mysql 4.1.12, `make -n test` reveals cd mysql-test; ./mysql-test-run ./mysql-test-run --ps-protocol With 4.1.14, that has changed to cd mysql-test; perl mysql-test-run.pl perl mysql-test-run.pl --ps-protocol Apparently, the test program shell script, mysql-test-run, has been rewritten as a perl script, though there is no mention of this in the change log http://dev.mysql.com/doc/mysql/en/news-4-1-x.html. A quick glance at the I was rather surpised about the dependency on Perl. source shows that the perl script is not finished -- it has quite a few commented-out, fix me sections. I'll have a look. You still have a couple of options to test your build. You can run the new test suite with the --force option. Do what make would do, `cd mysql-test`, then `perl mysql-test-run.pl --force`. You will see that every test that should have been skipped will instead be run and fail (archive, the bdb tests, blackhole, csv, example, func_des_encrypt, isam, the ndb tests, I'm fairly fluent in perl, though mine's a bit Chaucerian, since I learned Perl4 :-), and am not *so* familiar with the 5 constructs, but I could try to send patches (to whom?). openssl_1, raid, and so on). If every test passes except for tests of things you don't have, you should be OK. In particular, there are a set of innodb tests which should answer your question about whether or not innodb is working in your build. Thanks. There's a second way, which I think is better. It turns out that the old shell-script test suite is still built. Hence, you can still test the old way. Yes, and It may be worth trying both. cd mysql-test ./mysql-test-run --force This will properly skip tests of features not compiled in. Note that I added I can probably steal how to skip them and stick that in the Perl. --force because, at least in my case, the new embedded test, not_embedded_server, is run and fails. I'm not yet sure if that should have been skipped. The errors explicitly told me I needed --force, so that's OK. As the old test script is still built and the new test script is unfinished, undocumented, and broken, I am suspicious that the real problem is that make was prematurely (accidentally?) changed to use the new one before it was ready. I've copied the bugs list in hopes of an answer. Definitely some weirdness about the release process there :-) I'm sure I've done worse in the past, though. I'm not subscribed to the bugs list, so this might bounce back off there. The third way, I suppose, is to ask whether I'm actually using the correct version -- should I be on 4.1,x, or 4.0.x, or what? I'm under the impression that for work with Ruby on Rails I need the latest 4.x but I could have misunderstood something. What I really mean is: which versions are considered stable? [Ruby has a custom that minor release numbers are odd for developement, even for stable, but minorminor ones increment successively after that: 1.8.2, and 1.8.3 (due soon) are stable, 1.9.x is development (at present). I'm not sure how things work in the MySQL world.] Michael P.S. Out of curiosity, why did you find it necessary to edit BUILD/compile-solaris-sparc? Couldn't you make the changes you wanted with options to configure? I was passing options to configure, and the was a bit of setup in compile-solaris-sparc that was probably there for a reason. So I changed it there. I changed it to give me the alternative port and directory so I don't munge things for people using V3.x, used for teaching. [Besides, I'd have to mess with autoconf to fix configure properly, as it is setup by that, and I'm not so fluent in autoconf as I'd wish, plus it seems silly to mod the autoconf stuff for something so parochial as port + directory.] Maybe there's a better place altogether to define this stuff? Thank you, Hugh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: `gmake test` probs Solaris9 for M. 4.1.4.
Michael, you beat me in replying, and saved me from typing the analysis - thanks! Michael Stassen wrote: [[...]] The test suite is broken. Well, I would not put it that way - a diplomatic wording is: The tool to run the test suite does not run as it should. I understand that the effect for Hugh and you is the same ;-) The archive test is meant to test the archive table engine, but the archive engine is not built into mysql by default. You have to add the --with-archive-storage-engine if you want it. You didn't do that, so the archive test should have been skipped. With mysql 4.1.12, `make -n test` reveals cd mysql-test; ./mysql-test-run ./mysql-test-run --ps-protocol With 4.1.14, that has changed to cd mysql-test; perl mysql-test-run.pl perl mysql-test-run.pl --ps-protocol Apparently, the test program shell script, mysql-test-run, has been rewritten as a perl script, though there is no mention of this in the change log http://dev.mysql.com/doc/mysql/en/news-4-1-x.html. A quick glance at the source shows that the perl script is not finished -- it has quite a few commented-out, fix me sections. Correct. A Perl script for the test suite is being worked on. Reasons: 1) A shell script will never work for native Windoes users who do not install Cygwwin, MinGW, MKS or similar suites. 2) The shell script lacks some functionality which is needed, and it is already too convoluted. So that Perl script is work in progress which we needed to test on all build platforms. It was an oversight that it got included in the source tree in the current status, the tests have also been done using the old shell script. [[...]] There's a second way, which I think is better. It turns out that the old shell-script test suite is still built. Hence, you can still test the old way. cd mysql-test ./mysql-test-run --force Right, this is what I recommend. To be a bit picky: There is one standard test suite only (which is included in the source tar-ball), but there are currently two different scripts to run it, the (old) shell and the (new) Perl script. The specific error causing your and Hugh's problem, the incorrect skipping of tests which are not applicable to the server to be tested, has been fixed, but maybe this version has not yet been pushed to the 4.1 tree. [[...]] As the old test script is still built and the new test script is unfinished, undocumented, and broken, I am suspicious that the real problem is that make was prematurely (accidentally?) changed to use the new one before it was ready. I've copied the bugs list in hopes of an answer. Both yes and no: yes in the sense that the new suite (as included in the 4.1.14 tree) is not yet correct. no in the sense that the change to use it _internally_ was deliberate in order to get full platform coverage. We are sorry it caused you inconveniences! Regards, Jörg -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: `gmake test` probs Solaris9 for M. 4.1.4.
On Fri, 9 Sep 2005, Joerg Bruehe wrote:
Michael,
you beat me in replying, and saved me from typing the analysis - thanks!
Michael Stassen wrote:
[[...]]
The test suite is broken.
Well, I would not put it that way - a diplomatic wording is:
The tool to run the test suite does not run as it should.
I understand that the effect for Hugh and you is the same ;-)
Nobody was claiming *deliberate* breakage! :-)
[...]
quite a few commented-out, fix me sections.
Correct. A Perl script for the test suite is being worked on. Reasons:
1) A shell script will never work for native Windoes users who do not
install Cygwwin, MinGW, MKS or similar suites.
2) The shell script lacks some functionality which is needed, and it is
already too convoluted.
Good reasons.
[...]
cd mysql-test ./mysql-test-run --force
Right, this is what I recommend.
To be a bit picky: There is one standard test suite only (which is included
in the source tar-ball), but there are currently two different scripts to run
it, the (old) shell and the (new) Perl script.
The specific error causing your and Hugh's problem, the incorrect skipping of
tests which are not applicable to the server to be tested,
has been fixed, but maybe this version has not yet been pushed to the 4.1
tree.
Can we grab the new version off the web (CVSweb or similar?)
somewhere? If it is feasible for me I'd like to translate it to
Ruby to give you that much wider coverage. Depends if my Perl
fluency is sufficient, etc. Whether {you, the committee, ???} accept
the contribution is another matter entirely, of course.
Regards, J?rg
Thank you,
Hugh
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
`gmake test` probs Solaris9 for M. 4.1.4.
Attempts to do make test prior to installation, to check that I'm installing something workable, give: quote neelix hgs 63 % gmake test cd mysql-test; perl mysql-test-run.pl perl mysql-test-run.pl --ps-protocol No ndbcluster support Killing Possible Leftover Processes Removing Stale Files Installing Master Databases Installing Master Databases Installing Slave Databases Installing Slave Databases Installing Slave Databases === Finding Tests in the 'main' suite Starting Tests in the 'main' suite TESTRESULT --- alias [ pass ] alter_table [ pass ] analyse [ pass ] analyze [ pass ] ansi[ pass ] archive [ fail ] Errors are (from /scratch/hgs/mysql-4.1.14/mysql-test/var/log/mysqltest-time) : This test is not supported by this installation mysqltest returned unexpected code 15872, it has probably crashed (the last lines may be the most important ones) Aborting: archive failed. To continue, re-run with '--force'. Ending Tests Shutting-down MySQL daemon Master(s) shutdown finished Slave(s) shutdown finished gmake: *** [test] Error 1 neelix hgs 64 % /quote So, firstly, invoke what with '--force'? You don't get anything useful if you pass that to make Also, how can I tell if InnoDB built OK? I'm doing this for use with Ruby on Rails, and I need it to be in a separate directory from the version we already have (3.x) used by others. I modified mysql-4.1.14/BUILD/compile-solaris-sparc thusly neelix hgs 81 % display_diffs.rb . --- ./compile-solaris-sparc.orig2005-08-17 18:06:41.0 +0100 +++ ./compile-solaris-sparc 2005-09-06 18:36:25.386697000 +0100 @@ -11,6 +11,6 @@ (cd gemini aclocal autoheader aclocal automake autoconf) fi -CFLAGS=-g -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa CXX=gcc CXXFLAGS=-Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Woverloaded-virtual -Wsign-promo -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor -felide-constructors -fno-exceptions -fno-rtti -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa -g ./configure --prefix=/usr/local/mysql --enable-assembler --with-extra-charsets=complex --enable-thread-safe-client +CFLAGS=-g -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa CXX=gcc CXXFLAGS=-Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Woverloaded-virtual -Wsign-promo -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor -felide-constructors -fno-exceptions -fno-rtti -O3 -fno-omit-frame-pointer -mcpu=v8 -Wa,-xarch=v8plusa -g ./configure --prefix=/usr/local/mysql --enable-assembler --with-extra-charsets=complex --enable-thread-safe-client --with-tcp-port=3308 --with-unix-socket-path=/tmp/mysql4.sock --prefix=/usr/local/mysql-4.1.14 gmake -j 4 neelix hgs 82 % and I invoked the script directly, and also tried with bash. Not sure what else to pass on. GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for sparc-sun-solaris2.9 gcc (GCC) 3.4.3 Thank you Hugh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
