Re: [racket-users] JFYI, c-level assertion failures during build

Thanks! I've pushed a repair. At Sun, 26 Feb 2017 00:11:50 -0500, "'John Clements' via Racket Users" wrote: > > > On Feb 25, 2017, at 5:36 AM, Matthew Flatt wrote: > > > > Did a fresh checkout solve the problem? > > > > If not, can you show more context to clarify which packages are being > >

Re: [racket-users] JFYI, c-level assertion failures during build

Snapshot-based pkg builds are here: https://plt.eecs.northwestern.edu/pkg-build/ Robby On Sat, Feb 25, 2017 at 11:11 PM, 'John Clements' via Racket Users wrote: > >> On Feb 25, 2017, at 5:36 AM, Matthew Flatt wrote: >> >> Did a fresh checkout solve the problem? >> >> If not, can you show more

Re: [racket-users] JFYI, c-level assertion failures during build

> On Feb 25, 2017, at 5:36 AM, Matthew Flatt wrote: > > Did a fresh checkout solve the problem? > > If not, can you show more context to clarify which packages are being > built when the crash happens. (That is, the crash is possibly not task > in "1", which is shown here.) Even better, making

Re: [racket-users] JFYI, c-level assertion failures during build

Did a fresh checkout solve the problem? If not, can you show more context to clarify which packages are being built when the crash happens. (That is, the crash is possibly not task in "1", which is shown here.) Even better, making with `CPUS=1` would clearly identify the package where the compiler

[racket-users] JFYI, c-level assertion failures during build

I’m currently in a state where calling `make` in my top-level racket directory results in output ending thusly: … raco setup: 1 making: /cldr-bcp47/cldr/bcp47/data Assertion failed: (!(used && (pre_body->count == 1) && pre_body->vars[0]->optimize.known_val && ((Scheme_Type)(scheme_once_used_type