From: David G. <DGr...@am...> - 2017-07-24 17:07:53
|
I did a fresh install of MinGW on a Windows 7 computer. I started by selecting everything in Basic Setup. When I installed, I got a message box when the installer got to Fortran: "Internal specification error. Can't get 'tarname' for non-release element <<unknown>> Please report this to the package maintainer" It doesn't seen to indicate a real problem. Once I had finished selecting additional things to install and installed them, removing blockers as documented in the instructions, Fortran was installed |
From: Keith M. <kei...@us...> - 2017-07-24 19:54:44
Attachments:
20170724-1.log
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/07/17 18:07, David Gressett wrote: > I did a fresh install of MinGW on a Windows 7 computer. > I started by selecting everything in Basic Setup. Thanks for testing it! > When I installed, I got a message box when the installer got to > Fortran: > > "Internal specification error. Can't get 'tarname' for non-release > element <<unknown>> Please report this to the package maintainer" > > It doesn't seen to indicate a real problem. It isn't, but it appears disturbing, (with dependency tracing): $ mingw-get install --trace=0x0200 gcc-fortran 2>&1 | tee 20170724.log ... gcc-fortran-4.8.2-mingw32-dev.tar.meta: resolve dependencies require: libgfortran-4.8.2-mingw32-dll-3.tar considering: libgfortran-6.3.0-1-mingw32-dll-3.tar.xz considering: libgfortran-5.3.0-3-mingw32-dll-3.tar.xz considering: libgfortran-5.3.0-2-mingw32-dll-3.tar.xz considering: libgfortran-4.9.3-1-mingw32-dll-3.tar.xz considering: libgfortran-4.8.1-4-mingw32-dll-3.tar.lzma considering: libgfortran-4.8.1-3-mingw32-dll-3.tar.lzma considering: libgfortran-4.8.1-2-mingw32-dll-3.tar.lzma considering: libgfortran-4.8.1-1-mingw32-dll-3.tar.lzma considering: libgfortran-4.7.2-1-mingw32-dll-3.tar.lzma considering: libgfortran-4.7.0-1-mingw32-dll-3.tar.lzma considering: libgfortran-4.6.2-1-mingw32-dll-3.tar.lzma considering: libgfortran-4.6.1-2-mingw32-dll-3.tar.lzma considering: libgfortran-4.5.2-1-mingw32-dll-3.tar.lzma <<<unknown>>>: schedule installation (flags=0x00000242) mingw-get.exe: *** ERROR *** internal package specification error mingw-get.exe: *** ERROR *** can't get 'tarname' for non-release element <<<unknown>>> mingw-get.exe: *** ERROR *** please report this to the package maintainer mingw-get.exe: *** ERROR *** gcc-fortran-4.8.2-mingw32-dev.tar.meta: requires... mingw-get.exe: *** ERROR *** libgfortran-%-mingw32-dll-3.tar: unresolved dependency (type 'eq') mingw-get.exe: *** ERROR *** libgfortran-%-mingw32-dll-3.tar: cannot identify any providing package mingw-get.exe: *** ERROR *** please report this to the package maintainer > Once I had finished selecting additional things to install and > installed them, removing blockers as documented in the instructions, > Fortran was installed It is a bogus dependency, arising from the gymnastics involved in the attempt to circumvent the legacy of gcc-4.8.1 package malformations. Note the version of libgfortran, for which mingw-get was attempting to identify a provider; the correct dependency was resolved earlier, and is subsequently installed. Nonetheless, the bogus dependency is a bug, so I will follow it up. - -- Regards, Keith. Public key available from keys.gnupg.net Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQIcBAEBAgAGBQJZdlB6AAoJEMCtNsY0flo/Z9MP/A2i2nvbgqxTZ7RVS4VdeqZg n8uTruMxBei2GrWgb3VJbv9OCTxPAv2x5cozGiocU6b97V00+HuWlbpnS/vn0Qfw 4aFfRbP499j7GQ1nHnfojrYVZ+aJzttqK4WgeeIKgvibVlLfYg/0uxjLO58sskoG 8+kYb5JbPWV9Xuloc0V+TOjjrYX/JG/urChEEpUKMP5snXVtfrg6LY0SjTzQkR+H AVhk+YqNrSRT+ykmXfNm1NZDG6j9NOrtvwzjt3lDXJTA+5YfMsny4AP1PpBAM/ap WEbMgKJihSR6/4IF7vOdUKtUOchew2Vi3FG9r8xP+v0h7C526efEnnCp6JA2hUT5 Xg7zyekoS3iPUU1ZlgTKAd+JRVh+hOSFdb71o1P8ldgSdtB53YHGXJii+4PAL/r9 65hpheC3dsIjlslC6jg+Ye+CDxPZEKZ85MJ/PmhVdMxXFeRVaq5bb1Q/wbXeepak OsLmzbUUFelzTP0Q9RessN/6lVehAi41ZVF65BJgKBaLpbXSZZk8pY0/U/Lqi308 P20qs0mtMNLQTypu89ogcedY+X/DUPPKLWDDu1PVoHfNLoLfh/QNwUplxtPQIdXd ZWfwhwA8FcP2lJ932qKKPFEukaivh+BN0ZheLbQD8VKxbAfXESJPi4gh7A7MWCHb ffq3ML/hYBLLn4sDrxxd =Ky+K -----END PGP SIGNATURE----- |
From: Keith M. <kei...@us...> - 2017-07-24 21:09:59
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/07/17 20:54, Keith Marshall via MinGW-users wrote: > Nonetheless, the bogus dependency is a bug, so I will follow it up. Should be fixed now: https://sourceforge.net/p/mingw/mingw-dist/ci/e705fdbb23f97f7c27994b85c8b2b0c9f5d8af86/ Please verify. - -- Regards, Keith. Public key available from keys.gnupg.net Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQIcBAEBAgAGBQJZdmIfAAoJEMCtNsY0flo/Z5QP/AvkXmq/5ZMq+6aF1saMKfL/ g5ObmAH7QroYCPGN2wIEwwHibcqM8KrB7OSD2LkZqP0htPQhxkN+4o2H9AdxYCw+ 7gf3zWWf95mJgP5QR4Mq4wO45g4Xdz5FlNMngZR3B0zGN6hdJRYVj9IrF5roYtXP nRrPX1ESeOWl5h/+2wqls53ptkDeDgjwF+UvtVoPjXdB1uch8UnC/TsSVhmvIolo 8hU81DH6m9NZVfSfsN+Cg69qxwkNM50d16jtIi2ME+P0nfua8YKMrCufyC4jGgVG yyhBpohiElI6ATFDKWMeHzX16siP+oq+gdW3Y+F4GZPodjwZzVoRE5TQmkHVTSpj UTJCJ/BEvw51Z0vF1Sc9dnaSqoVET5rejv6msKHbHLLTsiQSM87pJS3VOg+NRGFy vJJDuwz3gvXKorzJpCm4G1Vb2lQTda5Rfd1wZiDihY5n044M9ToYvW6ATflG2FXm RWPXGatVIToeDScHCFEXW1txSlSszvHASkh+TupHo+gTKs43GYV+KHImckId9E3s ccYWI6o/VqOlftXhILCvLIaSrhQgd7LRKGFj6MBwcMJzx/niqFF5QJ6RF6UbMvDZ 7/Qwjh/8oCoyltiF+/NJeLv2x+MykWTVyRGPwkXGZYwwfyLFaAM0RYJFXEU/V9GI LG8oE+A7lx3VMP7vd3uQ =rH3X -----END PGP SIGNATURE----- |
From: David G. <DGr...@am...> - 2017-07-24 21:47:16
|
Keith Marshall wrote: >On 24/07/17 20:54, Keith Marshall via MinGW-users wrote: >> Nonetheless, the bogus dependency is a bug, so I will follow it up. >Should be fixed now: >https://sourceforge.net/p/mingw/mingw-dist/ci/e705fdbb23f97f7c27994b85c8b2b0c9f5d8af86/ >Please verify. Fixed. |