>Probably too dumb actually - this makes sense under Solaris where /usr/ucb/cc
>aborts with exit status 1, because the compiler isn't bundled. I provided
>binaries to J.F. Gournay, so he probably doesn't have SUNWspro. However, the CPP
>in /usr/ccs/lib should work, so the simple answer is probably to create a symbolic
>link to it named cc in some BURT-searched directory (will this work?).
It will if it can deal with the flags that burt sends to what it thinks
is called 'cc' you might have to write a shell named cc that strips off
the -E flag.
>>I have no idea why this is so... It makes no sense to me.
>
>It does if you realise that the binaries he is using were copied from APS's
>/usr/local/epics/extensions/bin/solaris directory, where they were compiled
>against X11R5 rather than openwin. I can't build BURT here because it won't
>compile using g++.
The new one should compile with gcc. However, I still have zero clue
why burtrb needs anything from X... the gooey thing obviously needs X
stuff, but the command line stuff sure shouldn't.
--John Winans
- References:
- Re: Burt and km under Solaris Andrew Johnson
- Navigate by Date:
- Prev:
Field type Andy Kozubal
- Next:
Re: Field type Jeff Hill
- 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: Burt and km under Solaris Andrew Johnson
- Next:
Re: Burt and km under Solaris J.F. Gournay
- 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
|