i have now added the following in epics-base
to configure/os/CONFIG_SITE.Common.linux-ppc64e6500:
OP_SYS_INCLUDES += -I$(SDKTARGETSYSROOT)/usr/include/tirpc
OP_SYS_LDLIBS += -ltirpc
Heinz
> On 20. May 2021, at 17:21, Heinz Junkes via Tech-talk <tech-talk at aps.anl.gov> wrote:
>
> Now I have the curious problem that I have the "normal” rpc.h on my host system (linux-x86_64)
> and therefore there with TIRPC=YES then the libtirpc.so of course is not found.
>
> But I have to use the rpcgen of den linux-host to generate the vxi11core_xdr.c
> And the host includes of course rpc/rpc.h which is then not found by linux-ppc64e6500.
>
> Heinz
>
>
>> On 20. May 2021, at 17:03, Hu, Yong <yhu at bnl.gov> wrote:
>>
>> I had the same problem on RHEL8 recently. It was reported here: https://github.com/epics-modules/asyn/issues/95
>>
>> If "TIRPC=YES" does not work for your cross compile, then you probably need to comment out all vxi11-related stuff in asyn/asyn/Makefile
>>
>> Good luck!
>> Yong
>>
>>
>> On 5/20/21, 10:43 AM, "Tech-talk on behalf of Pearson, Matthew R. via Tech-talk" <tech-talk-bounces at aps.anl.gov on behalf of tech-talk at aps.anl.gov> wrote:
>>
>>
>> Hi,
>>
>> I think I came across the same issue recently on RHEL8. There was a recent Asyn build option added, that you can set in CONFIG_SITE (or CONFIG_SITE.local):
>>
>> TIRPC=YES
>>
>> Which changes the include file search path to /usr/include/tirpc/
>>
>> Cheers,
>> Matt
>>
>> -----Original Message-----
>> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of junkes via Tech-talk
>> Sent: Thursday, May 20, 2021 10:22 AM
>> To: Tech talk <tech-talk at aps.anl.gov>
>> Subject: [EXTERNAL] asyn vxi11 rpc issue cross compile for yocto powerpc64-fsl-linux
>>
>> I am in the process of cross-compiling EPICS7 for powerpc64-fsl-linux.
>>
>> epics-base works great, also already some support-modules like sncseq, sscan, calc, busy …
>>
>> Now I just fail with asyn on the vxi11 part.
>>
>> rpc/rpc.h can only be found on the yocto-sysroot under usr/include/tirpc. Also I don't see any rpc-support like rpcgen etc..
>>
>> That may also be due to how it was built with yocto. But this part I have not yet understood and I use
>> recipes from ESS and am quite happy where I have now arrived with their help ;-)
>>
>> /opt/ifc14xx/2.6-4.14/sysroots/x86_64-fslsdk-linux/usr/bin/powerpc64-fsl-linux/powerpc64-fsl-linux-gcc -D_GNU_SOURCE -D_DEFAULT_SOURCE -DUSE_TYPED_RSET -DUSE_TYPED_DSET -DUSE_TYPED_DRVET -DBUILDING_asyn_API -D_ppc_64_ --sysroot=/opt/ifc14xx/2.6-4.14/sysroots/ppc64e6500-fsl-linux -mhard-float -mcpu=e6500 -DUNIX -Dlinux -O3 -Wall -Werror-implicit-function-declaration -DUSE_TYPED_RSET -DUSE_TYPED_DSET -DUSE_TYPED_DRVET -DHAVE_LSREC -DHAVE_CALCMOD -DHAVE_DEVINT64 -m64 --sysroot=/opt/ifc14xx/2.6-4.14/sysroots/ppc64e6500-fsl-linux -mhard-float -mcpu=e6500 -pipe -feliminate-unused-debug-types -fPIC -I. -I../O.Common -I. -I. -I../../asyn/drvAsynSerial/os/Linux -I../../asyn/drvAsynSerial/os/default -I.. -I../../asyn/asynDriver -I../../asyn/asynGpib -I../../asyn/drvAsynSerial -I../../asyn/interfaces -I../../asyn/miscellaneous -I../../asyn/asynPortDriver/exceptions -I../../asyn/asynPortDriver -I../../asyn/asynPortClient -I../../asyn/devEpics -I../../asyn/asynRecord -I../../asyn/vxi11 -I../../asyn/drvPrologixGPIB -I../../asyn/gsIP488 -I../../asyn/ni1014 -I../../asyn/devGpib -I../../include/compiler/gcc -I../../include/os/Linux -I../../include -I/home/yocto/EPICS/epics-support/seq-2.2.8/include -I/home/yocto/EPICS/epics-base/include/compiler/gcc -I/home/yocto/EPICS/epics-base/include/os/Linux -I/home/yocto/EPICS/epics-base/include -I/home/yocto/EPICS/epics-support/sscan/include -I/home/yocto/EPICS/epics-support/calc/include -I/home/yocto/EPICS/epics-support/autosave/include/os/Linux -I/home/yocto/EPICS/epics-support/autosave/include -I/home/yocto/EPICS/epics-support/busy/include -I/home/yocto/EPICS/epics-support/motor/include -c vxi11core_xdr.c
>> In file included from vxi11core_xdr.c:6:
>> vxi11core.h:9:10: fatal error: rpc/rpc.h: No such file or directory
>> #include <rpc/rpc.h>
>> ^~~~~~~~~~~
>> compilation terminated.
>>
>> Is there a variable/flag I can use to keep the vxi11 stuff out of the build process of asyn?
>>
>> Danke Heinz
>>
>>
>>
>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- References:
- asyn vxi11 rpc issue cross compile for yocto powerpc64-fsl-linux junkes via Tech-talk
- RE: [EXTERNAL] asyn vxi11 rpc issue cross compile for yocto powerpc64-fsl-linux Pearson, Matthew R. via Tech-talk
- Re: [EXTERNAL] asyn vxi11 rpc issue cross compile for yocto powerpc64-fsl-linux Hu, Yong via Tech-talk
- Re: [EXTERNAL] asyn vxi11 rpc issue cross compile for yocto powerpc64-fsl-linux Heinz Junkes via Tech-talk
- Navigate by Date:
- Prev:
Re: PVAccess equivalent to EPICS_CAS_INTF_ADDR_LIST environment variable question White, Greg via Tech-talk
- Next:
Re: [EXTERNAL] PVAccess equivalent to EPICS_CAS_INTF_ADDR_LIST environment variable question Hartman, Steven via Tech-talk
- 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: [EXTERNAL] asyn vxi11 rpc issue cross compile for yocto powerpc64-fsl-linux Heinz Junkes via Tech-talk
- Next:
Modbus & asynManager::queueLockPort queueRequest failed: port not connected Keara Louise Soloway via Tech-talk
- 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
|