zsh-users
 help / color / mirror / code / Atom feed
From: Aaron Schrab <aaron.schrab@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: trapped in bash
Date: Fri, 16 Dec 2016 16:51:18 -0500	[thread overview]
Message-ID: <20161216215117.GF2023@pug.qqx.org> (raw)
In-Reply-To: <58540944.3030706@eastlink.ca>

At 07:33 -0800 16 Dec 2016, Ray Andrews <rayandrews@eastlink.ca> wrote:
>So I'm setting up a new machine with Debian 64 (using Debian 32 still 
>on old machine) and I'm thinking to just copy over my whole zsh 
>install from here to there and ... nope ... I 'cd' to where the binary 
>is and type  'zsh' and bash reports that it can't find the file.  Copy 
>it to '/bin' and it still can't find it.  Even the desperate '. ./zsh' 
>reports 'cannot execute binary file'.  I hope to gawd that an apt-get 
>install of zsh would work, but I'd like to use my existing setup 
>exactly as is. Do I have to rebuild? I'm new with 64 bit issues, 
>whatever they may happen to be, but I thought a 64 bit environment 
>could always run 32 bit apps.  Or have I forgotten something simple? 

The hardware and kernel are able to run 32bit binaries, but you can't 
use 64bit shared libraries with 32bit executables (or vice-versa).  You 
also need the 32bit version of the run-time dynamic linker; lack of that 
is why you're being told that a file isn't found.

Unless there was something really special about that build I'd either 
just go with installing via apt or rebuilding.

If you *really* want to use the same build you can likely do that with a 
multi-arch setup. To start with that would involve:

  dpkg --add-architecture i386
  apt update
  apt install libc6:i386

Once that is done the system should at least recognize that the old zsh 
build is executable. But you'll likely need to install several other 
i386 libraries; depending on the age of the system where that was built 
it's possible that the required versions won't be found for the current 
version of Debian.

The number of i386 library packages needed for this shouldn't be large, 
but a multi-arch system does mean that every `apt update` will fetch the 
package list for both of the architectures.

>Meanwhile  I'm trapped in the pre-fire age of bash out of the box.  
>Even 'ls -l' doesn't work, filenames only.

That shouldn't have anything to do with bash vs. zsh.


  reply	other threads:[~2016-12-16 21:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 15:33 Ray Andrews
2016-12-16 21:51 ` Aaron Schrab [this message]
2016-12-16 22:39   ` Ray Andrews
2016-12-16 23:05     ` Bart Schaefer
2016-12-17 20:27       ` Ray Andrews
2016-12-17 20:43         ` Bart Schaefer
2016-12-17 22:40           ` Ray Andrews
     [not found]           ` <5855BEF2.6090208__18199.534857604$1482015164$gmane$org@eastlink.ca>
2016-12-18 15:06             ` Daniel Shahaf
2016-12-18 15:54               ` Ray Andrews
2016-12-19  0:32                 ` Daniel Shahaf
2016-12-19  2:30                   ` Bart Schaefer
2016-12-19  4:29                     ` Ray Andrews
2016-12-19  5:48                       ` Bart Schaefer
2016-12-19 16:26                         ` Ray Andrews
     [not found]                         ` <ab7aeb33-d091-6602-8baa-cce92300d289__26556.3400615521$1482166729$gmane$org@eastlink.ca>
2016-12-19 17:47                           ` Daniel Shahaf
2016-12-17 23:16 ` Jim
2016-12-17 23:38   ` Ray Andrews

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161216215117.GF2023@pug.qqx.org \
    --to=aaron.schrab@gmail.com \
    --cc=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).