> and for context:
>
> /sys/src/9107216
half of that is for obsolete pc drivers.
- erik
Thanks for the comments,
I dropped the volatile and that bit compiles,
I am getting close I think.
And in answer to charles, there is all sorts going on in there.
counting the semicolons gives:
Apache portable utils 16049
Apache portable runtime 24852
sqlite3
yeah i realized since. sorry
2012/11/21 Dan Cross
> On Wed, Nov 21, 2012 at 8:30 AM, Bence Fábián wrote:
>
>> 8c is for Plan9's C dialect.
>> Look into /sys/doc/ape.ps
>>
>
> This was not a useful answer to Steve's question.
>
> - Dan C.
>
>
>
On Wed, Nov 21, 2012 at 8:30 AM, Bence Fábián wrote:
> 8c is for Plan9's C dialect.
> Look into /sys/doc/ape.ps
>
This was not a useful answer to Steve's question.
- Dan C.
By which I meant that yes, it's legal ANSI C code to combine them. The
strange way the compiler implements volatile references probably led
to that odd diagnostic.
As I said, I'd try nopping the volatile.
On 21 November 2012 13:30, Charles Forsyth wrote:
> static is scope, volatile has dynamic ef
>static volatile svn_atomic_t cache_init_state = 0;
svn_atomic_t? has it got its own thread library? coroutines?
8c is for Plan9's C dialect.
Look into /sys/doc/ape.ps
2012/11/21 Steve Simon
> I'am trying (again) to build svn for plan9 native.
>
> 8c is blowing up with the error:
>
> bad in naddr: NAME cache_init_state
>
> the offending like is:
>
> static volatile svn_atomic_t cache_init_state
static is scope, volatile has dynamic effects, very dynamic. you
should be able to #define volatile
to nothing (-Dvolatile'=') and it will usually work. certainly for
statics and externals.
the one real effect it might have is on automatic variables if the
usage in conjunction
with setjmp is a litt
I'am trying (again) to build svn for plan9 native.
8c is blowing up with the error:
bad in naddr: NAME cache_init_state
the offending like is:
static volatile svn_atomic_t cache_init_state = 0;
Is this legal c code, static and volatile?
if it is anyone any ideas how to fix 8c - comp
