Centos 6 x86_64 Installation

On 10/10/14 20:23, Martyn Pittuck wrote:

Has anyone successfully installed Eagle on Centos???

 

No, but I'm running it on Fedora, also RPM-based

The default repositories (and EPEL) don't have libssl.i686 or

libcrypto.i686 - nor do they have openssl-libs.i686.

 

So any ideas?

 

Have you tried rpmfind? Or google? I typed "centos 6 libssl.i686" into

google and got lots of hits with links to likely looking RPMs

You will probably need to configure your system to have more than just

the base repository set. This is almost universally true of RH-derived

(and Debian-derived) distros. In fact the only one I've not had to do so

on was Gentoo.

HTH,

Rob

Yeah, I spent a couple of hours trying to get the dependencies installed, found the RPM's for Fedora but they use a newer version of glibc than is used in Centos 6.x - don't really fancy trying to change the glibc version, even if it is for the 32 bit libraries.

However I did chase the dependency's to get the 32 bit glibc 2.17 installed, gave up when the list got passed 15 packages (was going to overwrite .so's which are used by the ARM cross compiler I'm using).

I was hoping to either get a 'it works if you do this' or at least 'I eventually got there'.

Thanks anyway!

On 10/10/2014 4:47 PM, Martyn Pittuck wrote:

Yeah, I spent a couple of hours trying to get the dependencies

installed, found the RPM's for Fedora but they use a newer version of

glibc than is used in Centos 6.x - don't really fancy trying to change

the glibc version, even if it is for the 32 bit libraries.

 

However I did chase the dependency's to get the 32 bit glibc 2.17

installed, gave up when the list got passed 15 packages (was going to

overwrite .so's which are used by the ARM cross compiler I'm using).

 

I was hoping to either get a 'it works if you do this' or at least 'I

eventually got there'.

 

Thanks anyway!

Hi Martin,

The key here is to setup a 32-bit environment under your 64-bit machine.

I've attached a procedure that works under debian distros, it may take

some tweaking to get it to work under an RPM based distro.

hth,

Jorge Garcia

Thanks for the info but I believe I am suck with the 32 bit environment I am using. The cross compiler uses pre-compiled binaries requiring one version of GLIBC and Eagle seems to require another.

Anything other than the base yum repositories is going to be a difficult sell to the system admins.

Time to look for alternatives, or use windows VM...

On 10/19/2014 12:23 PM, Martyn Pittuck wrote:

Thanks for the info but I believe I am suck with the 32 bit environment

I am using. The cross compiler uses pre-compiled binaries requiring one

version of GLIBC and Eagle seems to require another.

What 32-bit libraries do you have installed, and what libraries is Eagle

expecting?

Anything other than the base yum repositories is going to be a difficult

sell to the system admins.

The Linux linking loader will look for libraries in the directories

listed in the environment variable "LD_LIBRARY_PATH" before it searches

the standard locations. Once you locate the required shareable libraries

you can put them in a directory separate from the system directories and

point the loader at them.

For example, I'm using Linux Mint 17 with Eagle 6.2.0 installed in /opt.

It requires several libraries from older versions of the distribution.

To see what libraries are missing, you can use the "ldd" command and

look for the ones marked "not found". For example, on my system I'm

missing libpng14.so.14:

  libXi.so.6 => /usr/lib/i386-linux-gnu/libXi.so.6 (0xf74e3000)

  libpng14.so.14 => not found

  libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf74c7000)

I created a subdirectory /opt/eagle-6.2.0/lib and populated it with the

shareable libraries I needed from an older system. When I invoke Eagle,

I use this shell script, which handles defining LD_LIBRARY_PATH for me:

#!/bin/bash

EAGLE_DIR=/opt/eagle-6.2.0

export LD_LIBRARY_PATH=$EAGLE_DIR/lib

exec $EAGLE_DIR/bin/eagle

Time to look for alternatives, or use windows VM...

Nope, just time to learn more about Linux. Worst case you might have to

compile a few libraries from source, but that'd be easier that

reinstalling the whole set of libraries from Fedora.

You'd need to post a list of the files you're missing before anyone is

likely to be able to give you more help (unless Jorge decides to install

a CentOS system to tinker with). Don't forget that CentOS is nothing

more than RedHat Enterprise Linux recompiled with a different name. You

may be able to find RHEL packages with what you need.

-Reece