Stephen,
> I was wondering if anyone has gone through the process of compiling and
> running the cfitsio library functions under vxWorks running on an mv167
> (68K) target. I am attempting to do so, and am finding that everything
> compiles fine, but when I try and execute a task which opens a FITS
> image for reading, everything seems to hang at the ffopen function.
> I would be grateful to hear from anyone who has done this successfully.
Yes, and it was compiled and built in a number of places (since multiple copies
were checked out from CVS) at your very institution. We didn't use mv167, but we
did use a number of 68k architectures, so mv167 will not be any different. We
used it for the UFTI project. One place it can be found is
/sw4/npr/ukroot/ufti/src/fitsio. Talk to Alan Bridger about it (if you haven't
already).
The two suggestions I have are:
1. You need a large stack, since deep down it pops about 30k onto the stack -
this single function needs more stack than the default VxWorks stack size.
We run it with 100k stacks, but 50 k would probably be OK.
2. Make sure that you have NFS working on the directories you are writing to
and reading from.
There were a number of other little things, so use our source code, not yours.
Nick Rees
Joint Astronomy Centre Ph: +1 (808) 961-3756
660 N. Aohoku Place Fax: +1 (808) 961-6516
Hilo, HI. 96720 Internet: [email protected]
- Navigate by Date:
- Prev:
Re: setting scan rates Tim Mooney
- Next:
EPICS Software Distribution: What's new? Bakul Banerjee
- 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:
vxWorks/cfitsio question Steven Heddle
- Next:
setting scan rates Geoff Savage
- 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
|