Experimental Physics and Industrial Control System
|
Subject: |
caRepeater object code not cross-compiled in R3.14.12.2 |
|
From: |
Rod Nussbaumer <[email protected]> |
|
To: |
EPICS Tech Talk <[email protected]> |
|
Date: |
Wed, 21 Nov 2012 09:57:19 -0800 |
Hi all.
Did I do something wrong?
My $EPICS_HOST_ARCH is linux-x86. I've added to
configure/os/CONFIG_SITE.linux-x86.Common the line:
CROSS_COMPILER_TARGET_ARCHS = linux-arm
In configure/os/CONFIG_SITE.linux-x86.linux-arm, I've set $GNU_DIR &
$GNU_TARGET to identify the name and location of my cross toolchain.
The build completes normally, and in bin/linux-arm I see a small number
of channel access tools, as well as a script to launch caRepeater, but
no caRepeater binaries. The tools built for the cross-compiled
architecture seem to work normally. My target architecture is a full-on
Linux host, which may run multiple IOC applications, and should be using
caRepeater.
Thanks.
Rod Nussbaumer
ISAC Controls, TRIUMF
Vancouver, Canada
- Replies:
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Dirk Zimoch
- Re: caRepeater object code not cross-compiled in R3.14.12.2 Jack Smith
- Navigate by Date:
- Prev:
RE: asynPortDriver epicsMutex error Mark Rivers
- Next:
Re: 3.14 v.s. 3.15 vs. v4 Jack Smith
- 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
- Navigate by Thread:
- Prev:
RE: asynPortDriver epicsMutex error Mark Rivers
- Next:
Re: caRepeater object code not cross-compiled in R3.14.12.2 Dirk Zimoch
- 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