Re: [Osw-users] compile problems

[Amar <am...@pt...>]

Best way to update your local osw directory is:

cvs update -d osw

issued from the parent directory of you local osw.
This will only patch the parts of your directory that need updating, it also
remembers the compression and cvsroot settings from the original checkout
command without having to retype them.

I just did a fresh pull on my RH9 Linux with gcc 3.3 and things seemed to
work.  Ditto with OS X / gcc 3.3.
The latest version of the "offending" file oswBinop3b.cpp, should be 1.5. If
not, another update is probably required.

  -Amar



----- Original Message ----- 
From: "smoerk" <sm...@gm...>
To: "Amar" <am...@pt...>; <osw...@li...>
Sent: Friday, May 21, 2004 3:16 AM
Subject: Re: [Osw-users] compile problems


> Hello,
>
> I don't know, if you committed the fixes, but I have still the same
> problems on Debian Linux. BTW, what is the best command to update my
> local osw directory from cvs? should i do
>
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/osw co osw
>
> again or is there another cvs command?
>
> Amar wrote:
> > Nope, looks like there was a problem committing last OS X changes, will
try
> > to get that fixed this evening.
> >
> > ----- Original Message ----- 
> > From: "smoerk" <sm...@gm...>
> > To: <osw...@li...>
> > Sent: Thursday, May 20, 2004 1:32 PM
> > Subject: Re: [Osw-users] compile problems
> >
> >
> >
> >>I tried to update the cvs repository, but it didn't find any new files.
> >>I guess i have to wait some more hours until the anonymous cvs server is
> >>up to date.
> >>
> >>Amar wrote:
> >>
> >>>Checked in some fixes for binary operations on samples - initially
> >
> > developed
> >
> >>>on Windows, and this morning checked in the fixes to make it compile
> >
> > under
> >
> >>>gcc (Linux + OS X).  It compiled OK under OS X as of this morning.  Try
> >>>another fresh pull and let me know what happens.
> >>>
> >>> Thanks.
> >>>  -Amar