1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 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 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: medm build |
From: | Torsten Bögershausen via Tech-talk <[email protected]> |
To: | Florian Feldbauer <[email protected]>, "Johnson, Andrew N." <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Fri, 7 Dec 2018 10:26:29 +0100 |
Hej, You can have a look here: (Which packets to install) https://github.com/jeonghanlee/pkg_automation/blob/master/pkg_automation.bash Or here: https://github.com/jeonghanlee/extensions.git Or here: https://github.com/EuropeanSpallationSource/extensions/tree/paths_for_Debian In other words, I think it makes sense to have a script, which does install all packages needed, and then you may need to patch the Makefile (or any better integration of this patch, needed for Debian 9 at least): cat patches/Xp_is_not_needed.p0.patch diff --git medm/Makefile medm/Makefile index 007ec46..3950a2c 100644 --- medm/Makefile +++ medm/Makefile @@ -170,7 +170,7 @@ USR_LIBS_solaris = Xm12 Xt Xmu X11 Xext Xm12_DIR = $(MOTIF_LIB) endif -USR_LIBS_Linux = Xm Xt Xp Xmu X11 Xext +USR_LIBS_Linux = Xm Xt Xmu X11 Xext #Xp is not available and not needed on Linux Mint 18 #USR_LIBS_Linux = Xm Xt Xmu X11 Xext Andrew, Would it make sense to have a ./configure script in extensions/ ? I may be able to provide a pacth & pull request some day.. On 07/12/18 10:00, Florian Feldbauer via Tech-talk wrote:
Hey Andrew,I'm not using MEDM but libXt-dev is not listed for Ubuntu on the webpage. Maybe it is a dependency of one of the other packages?I just checked which package contains libXt.so and found libXt-dev.Usually the lib packages contain libXXX.so.VERSION and the corresponding development packages contain the libXXX.so and libXXX.a files.If the linker doesn't find the shared object it tries the static one. I guess that's why the error message quotes> *** No rule to make target `/usr/lib64/libXt.a', needed by `medm'. Cheers, Florian Am 06.12.2018 um 18:26 schrieb Johnson, Andrew N.:Hi Florian,Is this in addition to the list of packages given on the MEDM web-page <https://epics.anl.gov/extensions/medm/index.php> ? That does mention Ubuntu 14.04 which is what I was testing against when I added that list.Strictly speaking the build says it's looking for libXt.a but it should be happy with a copy of libXt.so instead, unless you have configured the build for static linking.- Andrew On 12/6/18 4:55 AM, Florian Feldbauer via Tech-talk wrote:Hey, at least under debian, you need to install the package libxt-dev. Guess it's the same under Ubuntu. Hope this helps! Cheers, Florian On 12/6/18 11:33 AM, nieyg--- via Tech-talk wrote:I just tried to build medm using epics base-3.14.12.5 on Ubuntu 14.04. It gives an error:*** No rule to make target `/usr/lib64/libXt.a', needed by `medm'. I suspect a configuration error. Any suggestions? Thanks ------------------------------------------------------------------------ [email protected]-- Dr. Florian Feldbauer Ruhr-Universität Bochum Experimentalphysik I AG Fach-Nr. 125 Universitätsstr. 150 D-44801 Bochum Office: NB 2/134 Phone: (+49)234 / 32-23563 Fax: (+49)234 / 32-14170-- Arguing for surveillance because you have nothing to hide is no different than making the claim, "I don't care about freedom of speech because I have nothing to say." -- Edward Snowdon