Svadev mailing list

[geremy condra <debatem1 AT gmail.com>]

On Mon, Oct 3, 2011 at 12:06 PM, Matthew Wala 
<wala1 AT illinois.edu>
 wrote:

<snip>

>
> I guess I wasn't clear. I meant replacing all the SAFECode runtime
> library parameters with the static versions.
>
> So use something like:
>
> clang -g -fmemsafety -o test test.c /usr/local/lib/libsc_dbg_rt.a
> /usr/local/lib/libpoolalloc_bitmap.a /usr/local/lib/libgdtoa.a
> -lstdc++

Ah, sorry, I misunderstood. The great news is that it seems to work,
which I admit has me very excited. It does emit a seemingly endless
stream of errors, but I can work with that. Is there something I'm
missing with getting shared libraries to work, though? If possible it
would be my preferred approach.

> What sort of errors are you getting with the 2.7 version? It uses a
> different tool but you have to link in the same libraries.

It looked like an API change. I'll get you the errors tonight- would
be sooner, but I don't want to mess up this machine now that I have
safecode working on it.

Geremy Condra