Subject: |
Re: Building EPICS on Linux |
From: |
"Janet B. Anderson" <[email protected]> |
Date: |
Fri, 11 Jun 1999 10:17:44 -0500 |
Geoff,
We tried to fix this as problem for all host architectures by adding
the WIND_HOST_TYPE definition in the files CONFIG_HOST_ARCH.<hostarch>.
I think that the definition in the CONFIG_HOST_ARCH.Linux must be
incorrect
and you need to fix it. You need to set WIND_HOST_TYPE to the
description for Linux that you find in the tornado host
directory. On our solaris machine that directory contains the
following subdirectories -
usr/local/vw/tornado101/host :ls
include/ resource/ sun4-solaris2/ tcl/
man/ src/ sun4-sunos4/
so we put the definition WIND_HOST_TYPE = sun4-solaris2
into CONFIG_HOST_ARCH.solaris and the line WIND_HOST_TYPE = sun4-sunos4
into the CONFIG_HOST_ARCH.sun4 file.
I think you may be the first person to do an vx cross-compile on a
Linux host and the WIND_HOST_TYPE definition in CONFIG_HOST_ARCH.Linux
was never correct.
Hope this helps.
Janet
P.S. Before we found out from Rozelle Wright at LANL that setting
WIND_HOST_TYPE would fix the problem, at APS we put the following
soft link for as into the tornado directory structure and that also
solved the problem.
/usr/local/vw/tornado101/host/sun4-solaris2/lib/gcc-lib/m68k-wrs-vxworks/cygnus-2.7.2-960126
:
ll
drwxr-sr-x 3 vw 512 Sep 2 1997 ../
lrwxrwxrwx 1 other 67 Mar 22 1998 as ->
/usr/local/vw/tornado101/host/sun4-solaris2/
m68k-wrs-vxworks/bin/as*
-rwxr-xr-x 1 vw 1890436 Apr 1 1997 cc1*
-rwxr-xr-x 1 vw 1991568 Apr 1 1997 cc1obj*
-rwxr-xr-x 1 vw 2447768 Apr 1 1997 cc1plus*
-rwxr-xr-x 1 vw 116132 Apr 1 1997 cpp*
-rwxr-xr-x 1 vw 66704 Apr 1 1997 ld*
-rw-r--r-- 1 vw 31424 Apr 1 1997 libgcc.a
drwxr-sr-x 3 vw 512 Sep 2 1997 m68000/
drwxr-sr-x 2 vw 512 Sep 2 1997 msoft-float/
-rw-r--r-- 1 vw 3415 Apr 1 1997 specs
/usr/local/vw/tornado101/host/sun4-solaris2/lib/gcc-lib/m68k-wrs-vxworks/cygnus-2.7.2-960126
:
Geoff Savage wrote:
>
> We are attempting to setup an EPICS build enviroment on a PC running
> Linux. I have run into two difficulties.
> 1. I had to add an extra -B<bin path> to GCC. This specifies the
> location of the cross assembler, as.
> 2. The build stops with an error.
> ***No rule to make target `../../bin/mv162/vxWorks', needed by
> `buildInstall'. Stop.
>
> Now the questions:
> We use gcc as for cross compiles and for host compiles. How do I keep
> the two separate with hacking the GCC command line?
>
> Is there a clean way to remove the error message about vxWorks? Do I
> have to modify the iocCore vxworks makefile?
>
> Thanks in advance.
>
> Geoff Savage
- Navigate by Date:
- Prev:
New epics list server (fwd) Ron MacKenzie
- Next:
Labview as a Channel Access Server Ron Chestnut
- 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: Building EPICS on Linux William Lupton
- Next:
Re: Building EPICS on Linux Bill Lavender
- 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
|