| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: cross-compiling v7.0.7 |
| From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Pierrick M Hanlet <hanlet at fnal.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Thu, 15 Jun 2023 17:23:20 +0000 |
|
Andrew suggested that multiple CROSS_COMPILER_TARGET_ARCHS
could be an issue. I have not done that, only a single one.
Mark
From: Pierrick M Hanlet <hanlet at fnal.gov>
Sent: Thursday, June 15, 2023 11:19 AM To: Mark Rivers <rivers at cars.uchicago.edu>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov> Subject: Re: cross-compiling v7.0.7 Hi Mark,
I do actually have these definitions: CROSS_COMPILER_TARGET_ARCHS=linux-arm_raspberrypi2 linux-arm_raspberrypi3 linux-arm_raspberrypi4 linux-arm_terasicsoc linux-arm_achilles linux-x86_64cross linux-x86_i486 linux-ppc_mvme8100 and CROSS_COMPILER_HOST_ARCHS=linux-x86_64 As mentioned before, if I have CROSS_COMPILER_TARGET_ARCHS empty, then there is no problem building for the host. Thank you, Pierrick On 6/15/23 10:16, Mark Rivers wrote: > Hi Pierrick, > > I am cross-compiling with base 7.0.7 (actually master on May 18) and it works fine for me cross-compiling for vxWorks-ppc32. I just made these changes to configure/CONFIG_SITE: > > diff --git a/configure/CONFIG_SITE b/configure/CONFIG_SITE > index 03ec6d1..12f5ab1 100644 > --- a/configure/CONFIG_SITE > +++ b/configure/CONFIG_SITE > @@ -96,14 +96,14 @@ > # Which target architectures to cross-compile for. > # Definitions in configure/os/CONFIG_SITE.<host>.Common > # may override this setting. > -CROSS_COMPILER_TARGET_ARCHS= > +CROSS_COMPILER_TARGET_ARCHS=vxWorks-ppc32 > > # If only some of your host architectures can compile the > # above CROSS_COMPILER_TARGET_ARCHS specify those host > # architectures here. If the combination is complicated, > # set CROSS_COMPILER_TARGET_ARCHS in the appropriate > # configure/os/CONFIG_SITE.<host>.Common files instead. > -CROSS_COMPILER_HOST_ARCHS= > +CROSS_COMPILER_HOST_ARCHS=linux-x86_64 > > # The 'runtests', 'tapfiles' and 'junitfiles' make targets normally only run > # self-tests for the EPICS_HOST_ARCH architecture. If the host can execute > > Mark > > > -----Original Message----- > From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Pierrick M Hanlet via Tech-talk > Sent: Thursday, June 15, 2023 6:08 AM > To: tech-talk at aps.anl.gov > Subject: cross-compiling v7.0.7 > > Greetings all, > Something broke, or I missed new instructions in building the modules in > v7.0.7 for cross-compiled platforms. > I'm building for several platforms. The host build is fine, but when the cross-compiled platforms start building a new RELEASE.linux-x86_64.local is created with "EPICS_BASE = ", i.e. > empty. I did not experience this with > v7.0.5. > Cheers, > Pierrick > > -- > Pierrick Hanlet > Fermi National Accelerator > Accelerator Front End Controls > +1-630-840-5555 -- lab > +1-312-687-4980 -- mobile > > "Whether you think you can or think you can't, you're right" -- Henry Ford > -- Pierrick Hanlet Fermi National Accelerator Accelerator Front End Controls +1-630-840-5555 -- lab +1-312-687-4980 -- mobile "Whether you think you can or think you can't, you're right" -- Henry Ford |