-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Feb 28, 2017 at 06:52:56AM -0500, Chuck Hallenbeck wrote: > My comment below: > > > On Tue, Feb 28, 2017 at 12:30:25PM +0100, to...@tuxteam.de wrote: > > On Tue, Feb 28, 2017 at 06:04:24AM -0500, Chuck Hallenbeck wrote: > > > > > > On Tue, Feb 28, 2017 at 07:59:01AM -0300, Eduardo M KALINOWSKI wrote: > > > > On 27-02-2017 21:03, Chuck Hallenbeck wrote: > > > > > Hi everyone, > > > > > > > > > > I'm attempting to install a tommercial TTS from Cepstral on my Debian > > > > > Stretch system, and get the following when running swift: > > > > > > > > > > /usr/local/bin/swift: 12: exec: /opt/swift/bin/swift.bin: Exec format > > > > > error > > > > Show us the output of > > > > file /usr/local/bin/swift > > > > file /opt/swift/bin/swift.bin > > > > > > > > (Especially the latter.) > > > > [took the liberty to fix top-post] > > > > > Here is what file says: > > > > > > /opt/swift/bin/swift.bin: ELF 64-bit LSB executable, x86-64, version 1 > > > (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, > > > for GNU/Linux 2.6.9, not stripped > > > > How did this swift.bin arrive to your disk? (I mean: download, unpack, > > etc.) > > > > Suspecting some corruption along the way (e.g. line-end transformation > > by text mode in ftp, some (un)packer or similar). > > The Cepstral was obtained from a direct link to www.cepstral.com which > support gave me, via wget. There was an earlier package that was in > fact first downloaded to a Windows machine and then moved to Debian, > but while Windows unzipped it without changing its name, it eventually > produced the error I am now getting with the directly downloaded > package. BTW, I failed to show the output of file for the symlink, > which looks like this: > > /usr/local/bin/swift: symbolic link to /opt/swift/bin/swift > > I notice that it does not point to swift.bin, but to a directory > containing it.
Is /opt/swift/bin/swift really a directory? I'd expect it to be just a shell script invoking swift.bin (after possibly setting up some environment). > Either way, it runs under Arch on this box, but not under Debian. Hmmm. "it" meaning the very same file, i.e. Arch and Debian share a file system? Or a copy of the file? If the last is the case, could you compare their checksums, i.e. sha1sum /opt/swift/bin/swift.bin Are they equal? (No need to do it if the first is the case, of course). Just a shot in the dark: quoting a previous mail from you > Here is what file says: > > /opt/swift/bin/swift.bin: ELF 64-bit LSB executable, x86-64, version 1 > (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, > for GNU/Linux 2.6.9, not stripped Does /lib64/ld-linux-x86-64.so.2 exist on your Debian box? (would be strange if not, but hey...) regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAli1becACgkQBcgs9XrR2kYpQwCfb6O4tt1f3V0O1KSI2Bo17n4o t4AAn05+c0rKtW5TA1E5Gv87tvLgn2ax =41hy -----END PGP SIGNATURE-----
