On Wed, 18 Aug 1999, Christopher P. Gill wrote:

> I'm hoping that someone has a quick suggestion that will allow be to get
> past this.  Here's the log of what happens (long lines wrapped)

The problem is the method of extraction. I ran into the same thing. The
package system is doing a "gzcat mysql-3.22.22.tar.gz | tar xf -" and that
was segfaulting on my machine as well. What I did was to extract
mysql-3.22.22.tar.gz manually into the work directory with the following:

% cd /usr/pkgsrc/databases/mysql-client/work
% tar zxf l ../../../distfiles/mysql-3.22.22.tar.gz
% touch .extract_done

Then you should be able to go back to the mysql-client directory and finish
the build. I'm not sure why tar is dying but that worked for me...
-Dave

> 
> ####
> 
> adsl-151: {34} pwd
> /usr/pkgsrc/databases/mysql-client
> adsl-151: {35} make
> ===>  Validating dependencies for mysql-client-3.22.22
> >> Checksum OK for mysql-3.22.22.tar.gz.
> ===>  Extracting for mysql-client-3.22.22
> ===>  mysql-client-3.22.22 depends on executable: gmake - 
> /usr/pkg/bin/gmake found
> ===>  mysql-client-3.22.22 depends on file: /usr/pkg/bin/pkglibtool-1.2p1
> - found
> ===>  mysql-client-3.22.22 depends on installed package: perl-5.00404 -
> perl-5.00404  found
> /usr/bin/tar: Segmentation fault - core dumped
> *** Error code 139
> 
> Stop.
> *** Error code 1
> 
> Stop.
> *** Error code 1
> 
> Stop.
> 
> ####
> 
> 
> Putting gdb on the core file in /usr/pkgsrc/databases/mysql-client/work
> tells me little since I don't have source:
>  Core was generated by `tar'.
>  Program terminated with signal 11, Segmentation fault.
>  #0  0x331d6 in ?? ()
> 
> The file it's working on is kinda largish, but not *that* big:
>  -rw-r--r--   1 me   wheel  3762716 Apr 28 21:28 mysql-3.22.22.tar.gz
> 
> And the machine (Quadra 800 40/500+520, GENERIC kernel) should have plenty
> of RAM - so says 'top', at least:
>  Memory: 6736K Act 1240K Inact 428K Wired 24M Free 8K Swap 80M Swap free 
> 
> And I've got more than 20 MB available on /usr/pkgsrc, and at least 60 MB
> in /tmp.
> 
> I don't think it's an unstable system because I haven't had anything else
> act like this, and I've compiled about a dozen other packages.  I did a
> 'make clean', and also removed the distfile.  Trying again got me the same
> thing.
> 
> Any ideas, anyone?
> 
> 
> /*======================================================================
> "Don't die wondering..."                http://www.cldc.howard.edu/~cpg
>                                               email: cpg@scs.howard.edu
> chris out-              Christopher P. Gill
>   peace.        C.L.D.C. Senior System Operator (Ret.)
> ======================================================================*/
> 

-- 
Dave Schmitt <dschmi1@umbc.edu>