Don't worry about that error in cap5, that is the last thing in base to
be built, and you don't need it.
Now that you have built EPICS base what happens when you try to build
you IOC application?
Mark
-----Original Message-----
From: Florian Feldbauer [mailto:[email protected]]
Sent: Thursday, September 30, 2010 8:58 AM
To: Mark Rivers
Cc: [email protected]
Subject: RE: Cross compiling EPICS for cris v10
Hello Mark,
On Thu, 30 Sep 2010, Mark Rivers wrote:
> Did you first build EPICS base, which according to your output should
be located in:
Does this mean, I have to build EPICS base after I have edited the
CONFIG_SITE file? If so, I haven't build EPICS base first. But if I try,
I
also get an error:
/usr/local/cris/bin/cris-axis-linux-gnu-gcc -c
-D_POSIX_C_SOURCE=199506L
-D_POSIX_THREADS -D_XOPEN_SOURCE=500 -D_cris_ -mlinux -DUNIX
-D_BSD_SOURCE -Dlinux -D_REENTRANT -ansi -O3 -Wall -D_REENTRANT
-D_GNU_SOURCE -fno-strict-aliasing -pipe -Wdeclaration-after-statement
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/include/gdbm -mno-mul-bug-workaround -march=v10 -g -mlinux
-fPIC -I. -I../O.Common -I. -I.. -I../../../include/os/Linux
-I../../../include
-I/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE
-isystem /usr/local/devboard-R2_20//target/cris-axis-linux-gnu/include
-isystem
/usr/local/devboard-R2_20//target/cris-axis-linux-gnu/usr/include
Cap5.c
cc1: unrecognized option `-Wdeclaration-after-statement'
make[3]: *** [Cap5.o] Error 1
make[3]: Leaving directory
`/usr/Epics/base-3.14.10/src/cap5/O.linux-cris_v10'
make[2]: *** [install.linux-cris_v10] Error 2
make[2]: Leaving directory `/usr/Epics/base-3.14.10/src/cap5'
make[1]: *** [cap5.install] Error 2
make[1]: Leaving directory `/usr/Epics/base-3.14.10/src'
make: *** [src.install] Error 2
>
>
../../../../base-3.14.10/include >
> How did you define EPICS_BASE in your IOC-tree configure/RELEASE file?
It looks to me like you defined it with a relative path? Try defining
it with an absolute path.
It was defined with a relative path. I've changed it.
>
> What is your EPICS_HOST_ARCH environment variable, linux-x86?
Yes, EPICS_HOST_ARCH is set to linux-x86
>
> Does the file ../../../../base-3.14.10/lib/linux-x86/librecIoc.a
exist? That's where it should be located according to the output I see.
Yes, this file exists.
>
> Normally you edit the CONFIG_SITE in EPICS base configure/ directory
to set global settings for all EPICS applications at your site.
>
> Mark
>
>
> ________________________________
>
> From: [email protected] on behalf of Florian Feldbauer
> Sent: Thu 9/30/2010 7:04 AM
> To: [email protected]
> Subject: Cross compiling EPICS for cris v10
>
>
>
> Hello,
>
> I'm triing to cross compile EPICS for a cris v10 architecture but
having
> some problems.
> We are using here EPICS base 3.14.10 and synApps 5.4.1 (StreamDevice
and
> Asyn).
> According to the README.cris in the EPICS bsae documentations one has
to
> edit the CONFIG_SITE files. Which one? The ones in the EPICS base
> directory, or the ones in the directory of my IOC-tree?
>
> I've tried the second option and ending up with the error message
>
> make[3]: Entering directory
> `/usr/Epics/slowCtrl_etrax/slowCtrlApp/src/O.linux-cris_v10'
> /usr/local/cris//bin/cris-axis-linux-gnu-gcc -c
> -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500
> -D_cris_ -mlinux -DUNIX -D_BSD_SOURCE -Dlinux -D_REENTRANT -ansi
-O3
> -Wall -mno-mul-bug-workaround -march=v10 -g -mlinux -fPIC -I.
> -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include
> -I../../../../base-3.14.10/include/os/Linux
> -I../../../../base-3.14.10/include
> -I../../../../synApps/synApps_5_4_1/support/sscan/2-6-4/include
> -I../../../../synApps/synApps_5_4_1/support/calc/2-7/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/asyn/4-10/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/stream/2-4/include
> -isystem /usr/local/devboard-R2_20//target/cris-axis-linux-gnu/include
> -isystem
/usr/local/devboard-R2_20//target/cris-axis-linux-gnu/usr/include
> ../xxxRecord.c
> /usr/local/cris//bin/cris-axis-linux-gnu-gcc -c
> -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500
> -D_cris_ -mlinux -DUNIX -D_BSD_SOURCE -Dlinux -D_REENTRANT -ansi
-O3
> -Wall -mno-mul-bug-workaround -march=v10 -g -mlinux -fPIC -I.
> -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include
> -I../../../../base-3.14.10/include/os/Linux
> -I../../../../base-3.14.10/include
> -I../../../../synApps/synApps_5_4_1/support/sscan/2-6-4/include
> -I../../../../synApps/synApps_5_4_1/support/calc/2-7/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/asyn/4-10/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/stream/2-4/include
> -isystem /usr/local/devboard-R2_20//target/cris-axis-linux-gnu/include
> -isystem
/usr/local/devboard-R2_20//target/cris-axis-linux-gnu/usr/include
> ../devXxxSoft.c
> /usr/local/cris//bin/cris-axis-linux-gnu-gcc -c
> -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500
> -D_cris_ -mlinux -DUNIX -D_BSD_SOURCE -Dlinux -D_REENTRANT -ansi
-O3
> -Wall -mno-mul-bug-workaround -march=v10 -g -mlinux -fPIC -I.
> -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include
> -I../../../../base-3.14.10/include/os/Linux
> -I../../../../base-3.14.10/include
> -I../../../../synApps/synApps_5_4_1/support/sscan/2-6-4/include
> -I../../../../synApps/synApps_5_4_1/support/calc/2-7/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/asyn/4-10/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/stream/2-4/include
> -isystem /usr/local/devboard-R2_20//target/cris-axis-linux-gnu/include
> -isystem
/usr/local/devboard-R2_20//target/cris-axis-linux-gnu/usr/include
> ../dbSubExample.c
> /usr/local/cris//bin/cris-axis-linux-gnu-gcc -c
> -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500
> -D_cris_ -mlinux -DUNIX -D_BSD_SOURCE -Dlinux -D_REENTRANT -ansi
-O3
> -Wall -mno-mul-bug-workaround -march=v10 -g -mlinux -fPIC -I.
> -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include
> -I../../../../base-3.14.10/include/os/Linux
> -I../../../../base-3.14.10/include
> -I../../../../synApps/synApps_5_4_1/support/sscan/2-6-4/include
> -I../../../../synApps/synApps_5_4_1/support/calc/2-7/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/asyn/4-10/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/stream/2-4/include
> -isystem /usr/local/devboard-R2_20//target/cris-axis-linux-gnu/include
> -isystem
/usr/local/devboard-R2_20//target/cris-axis-linux-gnu/usr/include
> ../slowCtrlHello.c
> /usr/local/cris//bin/cris-axis-linux-gnu-gcc -c
> -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500
> -D_cris_ -mlinux -DUNIX -D_BSD_SOURCE -Dlinux -D_REENTRANT -ansi
-O3
> -Wall -mno-mul-bug-workaround -march=v10 -g -mlinux -fPIC -I.
> -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include
> -I../../../../base-3.14.10/include/os/Linux
> -I../../../../base-3.14.10/include
> -I../../../../synApps/synApps_5_4_1/support/sscan/2-6-4/include
> -I../../../../synApps/synApps_5_4_1/support/calc/2-7/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/asyn/4-10/include
> -I/usr/Epics/synApps/synApps_5_4_1/support/stream/2-4/include
> -isystem /usr/local/devboard-R2_20//target/cris-axis-linux-gnu/include
> -isystem
/usr/local/devboard-R2_20//target/cris-axis-linux-gnu/usr/include
> ../initTrace.c
> make[3]: *** No rule to make target
> `../../../lib/linux-cris_v10/librecIoc.a', needed by
> `libslowCtrlSupport.a'. Stop.
> make[3]: Leaving directory
> `/usr/Epics/slowCtrl_etrax/slowCtrlApp/src/O.linux-cris_v10'
> make[2]: *** [install.linux-cris_v10] Error 2
> make[2]: Leaving directory `/usr/Epics/slowCtrl_etrax/slowCtrlApp/src'
> make[1]: *** [src.install] Error 2
> make[1]: Leaving directory `/usr/Epics/slowCtrl_etrax/slowCtrlApp'
> make: *** [slowCtrlApp.install] Error 2
>
> Can anyone tell me, what I did wrong?
>
> Best regards,
> Florian
>
- Replies:
- RE: Cross compiling EPICS for cris v10 Florian Feldbauer
- References:
- Cross compiling EPICS for cris v10 Florian Feldbauer
- RE: Cross compiling EPICS for cris v10 Mark Rivers
- RE: Cross compiling EPICS for cris v10 Florian Feldbauer
- Navigate by Date:
- Prev:
RE: Cross compiling EPICS for cris v10 Florian Feldbauer
- Next:
RE: Cross compiling EPICS for cris v10 Florian Feldbauer
- 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: Cross compiling EPICS for cris v10 Florian Feldbauer
- Next:
RE: Cross compiling EPICS for cris v10 Florian Feldbauer
- 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
|