Re: building edm on 64-bin debian

[Ralph Lange <Ralph.Lange@gmx.de>]

Hi Ana,

What is your specific reason for building EPICS stuff from source on Debian?

There is a repository of production-quality EPICS packages for Debian.    http://epics.nsls2.bnl.gov/debian

Which basically means you can just install EPICS and a large set of drivers and extensions using the package manager. All the work you are going through already has been done.

If you find things missing or not working, it would be great if you contribute to the packaging effort - that way other Debian EPICS users can benefit directly from your work.    https://github.com/epicsdeb

Thanks a lot,
~Ralph

On 21/01/2015 01:25, Ana Malagon wrote:

Hi Mark,

Thanks; that did it - I checked for the location of libXt.so and found it in

/usr/lib/x86_64-linux-gnu

and the libXm had somehow gotten into the wrong directory so after moving that over and changing X11_LIB and MOTIF_LIB in CONFIG_SITE accordingly, it compiled!

Thanks very much as always for the quick replies :)

Ana

On Tue, Jan 20, 2015 at 4:05 PM, Mark Rivers <rivers@cars.uchicago.edu> wrote:

Is there in fact a libXm.a or libXm.so file somewhere on your system?  If so, where is it?

 

In extensions/configure/CONFIG_SITE.linux-x86_64.linux-x86_64 what do X11_LIB and MOTIF_LIB point to?

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Ana Malagon
Sent: Tuesday, January 20, 2015 5:50 PM
To: tech-talk@aps.anl.gov
Subject: building edm on 64-bin debian

 

Hi,

 

I'm running into an error when building edm 1.12.98 with epics base 3.14.12.4 on a 64-bit machine with debian 7.5:

 *** No rule to make target `/usr/lib64/libXm.a', needed by `libcfcaa62e-8199-11d3-a77f-00104b8742df.so'.  Stop.

I've installed the packages I need using apt-get (libmotif-dev, libxmu-dev, libxt-dev), and I've tried changing the X11_LIB and MOTIF_LIB to /usr/lib64/x86_64-linux-gnu in the CONFIG_SITE.linux-x86_64.linux-x86_64 file in extensions/configure/os, as suggested in this posting, but I get the same error.

I don't seem to have a CONFIG_EXTENSIONS file anywhere so can't follow the steps from another post with the same error; anyone have any suggestions for what I might try next?

Thanks,

Ana