When attempting to install, I get:
...
==> Validating source files with md5sums...
meshconv ... FAILED
==> ERROR: One or more files did not pass the validity check!
(Now reported on GitHub as per instructions.)
Git Clone URL: | https://aur.archlinux.org/meshconv.git (read-only, click to copy) |
---|---|
Package Base: | meshconv |
Description: | Converts to and from several popular 3D file formats |
Upstream URL: | https://www.patrickmin.com/meshconv/ |
Licenses: | |
Submitter: | bartus |
Maintainer: | bartus |
Last Packager: | bartus |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2017-11-04 20:13 |
Last Updated: | 2020-09-08 08:19 |
When attempting to install, I get:
...
==> Validating source files with md5sums...
meshconv ... FAILED
==> ERROR: One or more files did not pass the validity check!
(Now reported on GitHub as per instructions.)
Please report issues
and patches
to meshconv@github.com
@bartus,
Patrick Min has been very responsive and helpful but doesn't know why the Linux binary is crashing.
You used the statically linked Linux binary "version 1.26, build #1830, timestamp 2017/08/22 15:18:19" a few months ago. Does it still run for you today? Perhaps for some obscure reason newer kernels are leading to this binary SIGSEGV'ing as it's compiled against an ancient 2.6.18 kernel version???
When I have time I'll give it a spin under wine. Thank you :)
P.S.: After I got 64-bit wine set up, the meshconv Windows binary runs fine for me, too. Thanks!
Clemmitt
@cmsigler I was using exactly the same version as you. There is a newer build already, but available only for Windows:
--- meshconv 3D mesh converter, version 1.27, build #1841, timestamp 2017/11/26 21:32:44
Works fine with wine 3.3.
@bartus,
Sorry I didn't see your message last night.
Which version were you using? Was it "version 1.26, build #1830, timestamp 2017/08/22 15:18:19"?
I can't imagine there's something like a kernel problem with my system. Everything works 100% except for this statically linked binary crashing shrug Since it's statically linked I don't understand what else it could be -- unless it's some very esoteric recent change in the way the kernel loads ELF binaries.
I'll report it upstream to Patrick Min. I didn't do that at first because it's closed source and I assumed upstream would be unresponsive. Thanks for the suggestion.
P.S.: E-mail bug report has been sent upstream.
Update: Patrick Min has had another Arch Linux user report problems with the meshconv binary. I will post any significant info he reports.
Clemmitt
@cmsigler Did you send this report to dev. I was using this binary few months ago and it has been working just fine.
Hi,
Tried installing and running meshconv. It crashes with SIGSEGV. Can't even run it with no arguments to get a usage printout.
Since it's a static binary (an ancient one) with no symbols gdb doesn't help much:
(gdb) run Starting program: /usr/bin/meshconv
--- meshconv 3D mesh converter, version 1.26, build #1830, timestamp 2017/08/22 15:18:19 --- written by Patrick Min, 1997 - 2017
Timer [main timer] started
Program received signal SIGSEGV, Segmentation fault. 0xffffffffff600000 in ?? () (gdb) where
Kernel ver is 4.15.7-1-ARCH, but since it's statically linked I'm not sure where to start submitting other relevant system info. File info:
$ ll /usr/bin/meshconv -rwxr-xr-x 1 root root 2549792 Mar 7 13:19 /usr/bin/meshconv*
$ file /usr/bin/meshconv /usr/bin/meshconv: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18, BuildID[sha1]=0f9793eba320dc7691146d7f7e6b59b17b419a70, stripped
It doesn't seem to be packaged for Debian or Red Hat. I have no real experience disassembling a statically linked binary. Since there's no source I guess it's useless. So I'm posting this for others who might be interested. HTH.
Clemmitt Sigler
Pinned Comments
bartus commented on 2019-04-10 11:42
Please report
issues
andpatches
to meshconv@github.com