[M3devel] odbc errors

[Jay K]

Whereever you have it installed.
 
 
The Modula-3 libodbc* was perhaps in conflict with other libodbc*.
  There were at least warnings to this affect in some builds.
So it was renamed libm3odbc. However the old one isn't automatically deleted.
I think we can always delete it -- assuming that cm3 libraries aren't in the same directory as non-cm3 libraries but Olaf said not to.
 
 
If you look at your Solaris Tinderbox test results you will see some red I believe caused by this -- not deleting the old cm3 libodbc, whereever it is.
 
 
I /think/ this failure to /build/ the tests is why the red or orange status on Tinderbox instead of green.
But I'm not sure yet since I haven't gotten things to turn green yet.
Maybe we can only get green on the builds that don't run the tests?...er..yeah that would explain why only lastok builds are green and lastrelease builds are not..so I guess I can declare success on Linux x86/ppc/sparc..
 
 - Jay


________________________________
> From: hosking at cs.purdue.edu
> To: jay.krell at cornell.edu
> Date: Tue, 28 Jul 2009 09:39:45 -0400
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] odbc errors
>
> Umm, I am confused. On my niagara box I don't have /usr/local/cm3, so exactly what should I be deleting? And why?
>
> On 28 Jul 2009, at 05:35, Jay K wrote:
>
>
> odbc errors
>
> Tony, everyone, please read and then do like this:
>
> rm -rf /usr/local/cm3/pkg/*odbc*
> rm -rf /usr/local/cm3/lib/*odbc*
> cd root/cm3/m3-db
> rm -rf odbc
> cvs -z3 upd -dAP odbc
> cd odbc
> cm3
> cm3 -ship
>
>
> cd ~/work/cm3-inst
> find . | grep odbc | xargs rm
>
>
> - Jay
>