OT, Linux: bash can't see a file that's there, really!

On Fri, 05 Jun 2015 10:08:24 +0200, David Brown wrote:

> On 05/06/15 09:38, Tim Wescott wrote:
>> On Fri, 05 Jun 2015 08:54:30 +0200, David Brown wrote:
>> 
>>> On 05/06/15 00:35, Tim Wescott wrote:
>>>> On Thu, 04 Jun 2015 22:29:01 +0000, Simon Clubley wrote:
>>>>
>>>>> On 2015-06-04, Tim Wescott <seemywebsite@myfooter.really> wrote:
>>>>>>
>>>>>> $ldd /usr/share/arm-none-eabi/bin/arm-none-eabi-gcc
>>>>>> 	not a dynamic executable
>>>>>>
>>>>>> That seems more direct.  Is it a 32-bit vs. 64-bit thing?
>>>>>>

<< snip >>

>> 
>> Yes, it's a brand-new Ubuntu 14.04 64-bit install.  I copied over the
>> files from my Ubuntu 32-bit system (where they just worked, after
>> unzipping the file from CodeSourcery)
>> 
>> 
> With such copying, or manual installation, the package manager doesn't
> know that you need to install the 32-bit libraries.  If you had
> installed a 32-bit program with "apt-get" (or other system tools), the
> libraries could be installed automatically.
> 
> The suggestion I saw on the web was this:
> 
> <http://askubuntu.com/questions/454253/how-to-run-32-bit-app-in-
ubuntu-64-bit>
> 
> Roughly:
> 
> sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get
> install libc6:i386 libncurses5:i386 libstdc++6:i386
> 
> 
> That installs some basic 32-bit libraries, which are probably enough for
> the compiler.  Of course, if you want to run CodeSourcery's eclipse with
> packaged JVM, you will need a lot more 32-bit libraries.
> 
> A quick way to get a fair number of these libraries would be to install
> a 32-bit app from the Ubuntu package manager - something like Skype
> should work.
> 

That worked.  Thank you very much -- you've saved me from upgrade hell, I 
suspect.

> 
> Another option would be just to get the 64-bit packages from Code
> Sourcery!
> 

<< snip >>

>> Snivel.  Whine.  Etc.
>> 
>> 
> I strongly dislike getting embedded compilers from a distribution.  It's
> okay for things like gdb or openocd, but not for the compiler or
> library.  When I am working on a project, I need to know that the
> compiler and library is the same regardless of the machine, the distro,
> or the version of the system - I don't want an "apt-get upgrade" to
> change my embedded compiler!
> 
> So I make a point of keeping all my embedded compilers separated.  For
> example, at the moment I am using a compiler from here:
> 
> /opt/Freescale/KDS_2.0.0/toolchain/bin/arm-none-eabi-gcc
> 
> The installation is independent of the distro and system.
> 
> (I do a similar thing on Windows - I truly /hate/ when an installation
> such as AVR Studio insists on "upgrading" an existing installation,
> instead of installing it in parallel.)

I'm in agreement with you, which is why I want to carry on with what I 
have for as long as possible.  Upgrading your tools and inadvertently 
breaking things is a bitch.  Fortunately your suggestion above worked.

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com