Re: [racket-users] Re: Upgrading Racket

2018-10-03 Thread James Platt
It turns out that the solution was to delete previously compiled code in various places. I guess that things I was trying to run were trying to link to something, besides standard libraries, compiled under Racket 6.10. On Oct 3, 2018, at 3:48 PM, Philip McGrath wrote: > Seeing that you're on

Re: [racket-users] Re: Upgrading Racket

2018-10-03 Thread Philip McGrath
Seeing that you're on Mac, `which raco` should help to confirm what version of raco you have installed. (Interestingly, raco doesn't seem to support the `--version` flag, which I think it probably should. `racket --version` does work, but it's possible, albeit unlikely, that you could be have a

Re: [racket-users] Re: Upgrading Racket

2018-10-02 Thread James Platt
I'm just now getting back to this after returning from Racketcon. I ran `raco setup` as the user and again as root and it did not solve the problem. So then I tried `raco setup -c` but this gave permission errors (unlike the previous commands). so I ran `sudo raco setup -c' and then `sudo