On Fri, 3 Dec 1999, Stefan van der Eijk wrote:

> Hi,
> 
> I just had some fun recompiling MySQL on my alpha... at a certain moment
> it started eating memory and basically crashed the system (many zombies
> etc. etc.). I must say that on my intel system it goes right... Has
> anybody else experienced this?? 
> 
> This is where it goes wrong:
> 
> sql_parse.cc: In function `int check_connections(class THD *)':
> sql_parse.cc:87: warning: passing `size_socket *' as argument 3 of
> `getpeername(int, sockaddr *, socklen_t *)' changes signedness
> g++ -DMYSQL_SERVER                      -DDEFAULT_MYSQL_HOME="\"/\""
>         -DDATADIR="\"/var/lib/mysql\""                 
> -DSHAREDIR="\"/usr/share/mysql\""                       -DHAVE_CONFIG_H
> -I./../include
> -I./../regex                    -I. -I../include -I.. -I.   
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3
> -DDBUG_OFF   -fno-implicit-templates   -c sql_yacc.cc
> /my/gnu/lib/bison/bison.simple: In function `int yyparse()':
> /my/gnu/lib/bison/bison.simple:692: virtual memory exhausted
> make[3]: *** [sql_yacc.o] Error 1
> make[3]: Leaving directory `/usr/src/RPM/BUILD/mysql-3.22.27/sql'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/usr/src/RPM/BUILD/mysql-3.22.27/sql'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/RPM/BUILD/mysql-3.22.27'
> make: *** [all-recursive-am] Error 2
> Bad exit status from /var/tmp/rpm-tmp.417 (%build)
> 
> Any idea's??
> 
> Greetings,
> 
> Stefan

"
g++ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3
-DDBUG_OFF -fno-implicit-templates -rdynamic -o gen_lex_hash
gen_lex_hash.o ../isam/libnisam.a ../merge/libmerge.a ../heap/libheap.a
../mysys/libmysys.a ../dbug/libdbug.a ../regex/libregex.a
../strings/libmystrings.a -ldl -lnsl -lm -lz -lcrypt -lpthread
"

top out at just over 500Meg, goes back to 85 and starts climbing again,
does this twice and continues.. 

--
MandrakeSoft          http://www.mandrakesoft.com/
                                        --Axalon

Reply via email to