#43949: gmp install fails with :debug:extract Error code: NONE -------------------------------+-------------------------------- Reporter: brookemgilbert@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: Port: gmp | -------------------------------+-------------------------------- Comment (by brookemgilbert@…): Replying to [comment:5 ryandesign@…]:
Ok, that is the right checksum. So you do appear to have the right file. So the DNS problems don't seem to be contributing to this particular problem. So what is? We could try to run a version of the command MacPorts is trying to run to extract the file, and see if we get any additional errors that MacPorts didn't mention. I'd do this in a temporary directory that automatically cleans itself up after a few days, such as /tmp:
{{{ cd /tmp /usr/bin/bzip2 -dc '/opt/local/var/macports/distfiles/gmp/gmp-6.0.0a.tar.bz2' | /usr/bin/tar -xf - }}}
If this is successful, it should print no output, and a directory "gmp-6.0.0" should have been created. If it's not successful, maybe it prints a warning or an error. I am wondering if your system's bzip2 and/or tar utilities may be broken.
Here goes... {{{ $ cd /tmp $ /usr/bin/bzip2 -dc '/opt/local/var/macports/distfiles/gmp/gmp-6.0.0a.tar.bz2' | /usr/bin/tar -xf - $ ls gmp-6.0.0/ AUTHORS configure.ac mp_clz_tab.c COPYING cxx mp_dv_tab.c COPYING.LESSERv3 demos mp_get_fns.c COPYINGv2 doc mp_minv_tab.c COPYINGv3 errno.c mp_set_fns.c ChangeLog extract-dbl.c mpf INSTALL gen-bases.c mpn INSTALL.autoconf gen-fac.c mpq Makefile.am gen-fib.c mpz Makefile.in gen-jacobitab.c nextprime.c NEWS gen-psqr.c primesieve.c README gen-trialdivtab.c printf acinclude.m4 gmp-h.in rand aclocal.m4 gmp-impl.h scanf assert.c gmpxx.h tal-debug.c bootstrap.c install-sh tal-notreent.c compat.c invalid.c tal-reent.c config.guess longlong.h tests config.in ltmain.sh tune config.sub memory.c version.c configfsf.guess mini-gmp ylwrap configfsf.sub missing configure mp_bpl.c }}} Surely there must be a way to get more info back about the error.. Shall I just fire up a debug build? -- Ticket URL: <https://trac.macports.org/ticket/43949#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X