Re: Burt and km under Solaris

[winans@aps.anl.gov (John R. Winans)]

>	I am using exactly the same files that I used under SunOS. 
>	I have now the following diagnostics :
>**** READ BURT LOGFILE
>--- Start processing files
>file >/home/sigx0/sig/ttf/burt/injector/inj1.req<
>preprocessing ... ERROR: BurtPreprocessFile() cc abended exit_status 1 signal 
>-1ERROR: process_command_line_args() could not preprocess non-SDDS file 
>>/home/sigx0/sig/ttf/burt/injector/inj1.req<
>
>when I try a backup

I suspect that this is due to the rumors that CPP (which BURT uses to do macro
substitutions) no longer operates on files that don't look like C programs.
Sorry, your CPP is too smart for BURT.  You might be able to get an older or
different one working by putting a different one in your path when running 
BURT.

The conmmand that BURT uses to preprocess the files is in burtcommon.cc.
If you are not using any macros (ya know #defines) in your BURT files, you 
could probably make a shell file named 'cc' in your path when running BURT
that simply contains "cat -;exit 0".  
If you are willing to recompile BURT, you could also ifdef out the system
command that runs the preprocessor.
If you wanna be really cute, you could even hack in a command line arg
to disable the call to cpp, or that defines an alternate preprocessing
command, etc...

>
>and :
>......
>STEERER_H0INJ1_ONbo ... ca_array_put() nelem 1 ... OK
>STEERER_H1INJ1_ONbo ... ca_array_put() nelem 1 ... OK
>STEERER_H2INJ1_ONbo ... ca_array_put() nelem 1 ... OK
>STEERER_H3INJ1_ONbo ... ca_array_put() nelem 1 ... OK
>flushing with ca_flush_io() ... OK
>--- End writes
>
>did not find any read only notify values ... NO OUTPUT FILE CREATED
>
>when I try a restore.


This is some kind-ok warning from CA.  I have never seen it before.  Perhaps
Jeff might have some insight on this one?  Is there something interesting 
about the field of interest of your PV named STEERER_H0INJ1_ONbo?  Is it 
really a BO?  If not is it an array with 0 elements in it or something like 
that?

>	Another point : burtrb and burtwb needs to link libXt.so.5.0  and 
>libX11.so.5.0 at startup. Why ? Moreover, Solaris 2.5 is delivered with
>libXt.so.4.0  and libX11.so.4.0 .


I have no idea why this is so... It makes no sense to me.

----------------------

If it is any consolation, I have been working on a complete burt rewrite that 
has just been committed at APS a few hours ago.  It does not use CPP, the C 
compiler or anything that has to do with X windows.  A possible down side
is that the file formats are different and I don't have a convert-o-matic at
this time.  In fact the ascii file version needs some more work before use...
I have had to concern myself with SDDS on the first release.

Info about file formats and such will be made available when I fix all the
new ascii features that I broke while hacking about the SDDS codes.

Oh yah, due to the impact of this change, the new burt is called burt2... I
wanted to call it ernie, but after having gotten away with antelope I thought
it might be pushing things.


--John Winans