Experimental Physics and
Industrial Control System

Rod Nussbaumer <[email protected]> · Sun, 25 Nov 2012 09:14:20 -0800

Hi, Dirk.

Thanks, that did the trick. I replaced PROD_HOST with PROD_DEFAULT and
built everything that way.
For target architectures that are Linux, it feels as if this should be
the default. Without having explored this very deeply, I wonder whether
the properties of $EPIC_HOST_ARCH shouldn't be applied to all Linux
target architectures. Is anyone using Linux targets in a way that this
would not make sense?

   ---  rod.

On 11/22/2012 12:39 AM, Dirk Zimoch wrote:
> Hello Rod,
> 
> In src/ca/Makefile, you find caRepeater in PROD_HOST. Thus it is not
> made for cross builds. Try to take it out and instead set
> PROD_DEFAULT = caRepeater
> PROD_vxWorks = -nil-
> This should build the caRepeater for all non-vxWorks architectures, not
> only for the host architecture.
> 
> Dirk
> 
> 
> On 21.11.2012 18:57, Rod Nussbaumer wrote:
>> 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
>>
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System