>
> > My aim is first to try building what you have rather than just looking at
> > the code which I did last time.
>
> Actually Konstatin succeded in building BRAD at pii3.brahms.bnl.gov,
> but as pointed out in the INSTALL file, the executables fail for some
> reason.
Correct. The crash happens in the C++ standard library, which is part
of gcc. As time permits, I will try to use different versions of gcc
for the builds, probably egcs-1.0.x and gcc-2.95.x, and see what happens.
> If anyone fells up to it, I would appriciate if you would try to build
> BRAD on a Solaris machine. I don't know if my code (or
> the Objectivity/ROOT code) is ANSI enough to comiple out of the
> box. Since most of the DAQ system, as far as I know, is running on
> Solaris, I believe it would be reasonable if BRAD also worked on that
> architecture.
I run on Solaris, but I use egcs-1.1.2 (soon to become gcc-2.95.x). And
AFAIK there is no Objy distribution for "sunos-gcc", only "sunos-sun c++".
So on Solaris, the DAQ and BRAD twains shall never meet.
> Also, Konstatin made a quite a lot of remarks concerning the CVS
> repositories for BRAHMS.
>
> I believe placing the CVS repository under the daq account is a bad
> idea. After all, only a hand full of people have access to this
> account, which depreciates broad development.
Let me clarify what was proposed- to put the combined online/daq CVS
repository on sun2.hirg.bnl.gov. "write" access would be limited to
those who have accounts on sun2 ("real unix" accounts or "CVS pserver"
accounts). "read-only" access could be allowed for everybody else.
I also like Christian's proposal:
> Rather, I would suggest
> a more open (and general) approach:
>
> The CVS repository should be placed somewhere public (in BRAHMS
> terms), like say /afs/rhic/brahms/BRAHMS_CVS. This repository could
> contain sub-reositories like `online', `offline', etc. Then `online'
> could contain the DAQ modules, as outlined by Konstantin. `offline'
> would contain `brat', `gbrahms', `egread', `brad'(?), etc. Phenix has
> a CVS repository layout that looks a lot like this. Maybe, we should
> allow (resd-only) checkouts for non-developers.
I like the idea of putting the online/daq repository on AFS, right next
to the offline repository, however,
On the BRAHMS counting house computers, I would like to avoid running
AFS, if at all possible. ("AFS is down again, Captain! The beam is great,
but all the computers are hung and we can't do a thing! Reboot! Reboot!").
Without direct AFS access it would be somewhat inconvinient to access
the the online and daq repository if it is on AFS. But it is not a show
stopper and there are ways around the problem.
I would like to hear more opinions- if most people are in the favour
of putting the online/daq repository on AFS, then we'll do it.
> Another point concerning CVS. Please use tags to mark releases. In
> that way, non-developers that checkout software, won't get the latest
> non-working buggy alpha version of the software. ...
As far as the DAQ repository is concerned, there are no formal releases.
The latest version in CVS is "it". If you find a bug, report it
directly to the author or on a mailing list or fix it (and check it back
into CVS).
-- Konstantin Olchanski Physics Department, Brookhaven National Laboratory, Long Island, New York olchansk@bnl.gov
This archive was generated by hypermail 2b29 : Tue Feb 01 2000 - 20:35:05 EST