EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: medm build
From: D Peter Siddons <[email protected]>
To: [email protected]
Date: Thu, 10 Jan 2013 14:19:18 -0500
Thank you all for your suggestions. Keith's (below) provided the answer. Editing those entries in the config made everything work.

Pete.

On 01/10/2013 12:50 PM, [email protected] wrote:
Dear Kate, Hinko
     I agree with Andrew here.  The solution is to edit the CONFIG_SITE
files.  I have just been through getting EPICS building on 64-bit
Ubuntu12.
I had to make the following changes (see attached small patch files)

Change X11_LIB location in configure/os/CONFIG_SITE.linux-x86_64.linux-x8_64
  (extensions_config_Ubuntu12.patch)

Correct probe1_1_7_0 Makefile to group X* libraries correctly by Motif/X11
  (probe1_1_7_0-Ubuntu12.patch)
  [ old versions of other extensions may need this as well ]

Correct Makefiles for SDDS, SDSSepics 2.11 to handle default SOA behavior
  (got these from SDDS maintainer - may be added to newer releases)
   (SDDS.2.11-Ubuntu12.patch, SDDSepics.2.11-Ubuntu12.patch)

All but the config patch should were for older Linux releases as well

    Keith Thorne
    LIGO CDS Software Engineer

Kate, Hinko,

On 2013-01-10 Hinko Kocevar wrote:
ln -snf /usr/lib/i386-linux-gnu/libXt.a /usr/lib/libXt.a
On 01/10/2013 04:18 AM, Kate Feng wrote:
ln -f -s /usr/lib/.../libxt.a libXt.a
It should /never/ be necessary to create soft-links like that, you just
have
to edit your extensions/configure/CONFIG_SITE file or if you're sharing a
build tree between multiple architectures the appropriate
extensions/configure/os/CONFIG_SITE.<arch>.<arch> files to tell the build
system where the relevant libraries can be found.  Once you have correctly
set
the X11_LIB and/or MOTIF_LIB variables (and the _INC variables if
necessary)
for one product (say medm) it is then correct for any other products (say
StripTool) that you build in the same extensions tree.

This should be the more friendly solution that Hinko was asking for.

- Andrew
--
There is no such thing as a free lunch.  When invited for lunch,
it is best to check if you are there to eat, or to be eaten.
-- Clive Robinson


--
D. Peter Siddons
Detector Development Group Leader
NSLS, Bldg. 725D
Photon Sciences Directorate,
Brookhaven National Laboratory
Upton, NY 11973

email: [email protected]
Phone: (631) 344-2738


References:
medm build D Peter Siddons
Re: medm build Kate Feng
Re: medm build Hinko Kocevar
Re: medm build Andrew Johnson
Re: medm build keith . thorne

Navigate by Date:
Prev: RE: dbScan.c: periodicTask( ), initOnce( ), ... Hu, Yong
Next: Re: routing Pavel Maslov
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: medm build keith . thorne
Next: Re: medm build Hinko Kocevar
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·