A Racket source build got tripped up by my user dir for the "8.1" installation name
20 views
Skip to first unread message
Nathaniel W Griswold
May 21, 2021, 9:16:52 AM5/21/21
to racke...@googlegroups.com
Hello,
I was doing an in-place build from a clean git tree reset to exactly the v8.1 tag.
I got a bunch of errors right before the packages make phase where it was spitting out errors about packages in my user's package dir that i have installed from release distribution for the "8.1" installation name.
I thought this was weird because i though everything was supposed to be building for the "development" installation name.
This was before racket/etc/config.rktd was put in place. That file did not exist at the time of the errors.
When i moved my users "8.1" dir away temporarily and reran make, the build resumed properly and put a config.rktd in place with "development" installation-name.
I think this might be a bug in the build scripts. Somehow they are paying attention to the 8.1 directory. I did not have another racket in my path, i don't think it was finding it but maybe that is what happened.
Any ideas? If not maybe i'll spend some time investigating further.
Nate
I was doing an in-place build from a clean git tree reset to exactly the v8.1 tag.
I got a bunch of errors right before the packages make phase where it was spitting out errors about packages in my user's package dir that i have installed from release distribution for the "8.1" installation name.
I thought this was weird because i though everything was supposed to be building for the "development" installation name.
This was before racket/etc/config.rktd was put in place. That file did not exist at the time of the errors.
When i moved my users "8.1" dir away temporarily and reran make, the build resumed properly and put a config.rktd in place with "development" installation-name.
I think this might be a bug in the build scripts. Somehow they are paying attention to the 8.1 directory. I did not have another racket in my path, i don't think it was finding it but maybe that is what happened.
Any ideas? If not maybe i'll spend some time investigating further.
Nate
Nathaniel W Griswold
May 21, 2021, 10:49:45 AM5/21/21
to racke...@googlegroups.com
>
> I was doing an in-place build from a clean git tree reset to exactly the v8.1 tag.
>
> I got a bunch of errors right before the packages make phase where it was spitting out errors about packages in my user's package dir that i have installed from release distribution for the "8.1" installation name.
It is reproducible. Basically i just have a ~/Library/Racket/8.1 dir with some stuff in it and the build fails during bootstrap on raco setup when for some reason it starts to care about my regular non-development "8.1" dir.
> I was doing an in-place build from a clean git tree reset to exactly the v8.1 tag.
>
> I got a bunch of errors right before the packages make phase where it was spitting out errors about packages in my user's package dir that i have installed from release distribution for the "8.1" installation name.
That shouldn't happen right?
Log is attached.
Matthew Flatt
May 21, 2021, 11:06:48 AM5/21/21
to Nathaniel W Griswold, racke...@googlegroups.com
At Fri, 21 May 2021 09:49:39 -0500, Nathaniel W Griswold wrote:
> It is reproducible. Basically i just have a ~/Library/Racket/8.1 dir
> with some stuff in it and the build fails during bootstrap on raco
> setup when for some reason it starts to care about my regular
> non-development "8.1" dir.
>
> That shouldn't happen right?
Right. This looks like a problem with the CS initial install step. It
> It is reproducible. Basically i just have a ~/Library/Racket/8.1 dir
> with some stuff in it and the build fails during bootstrap on raco
> setup when for some reason it starts to care about my regular
> non-development "8.1" dir.
>
> That shouldn't happen right?
should use `--no-user` for that step, but it doesn't. I'll push a
repair.
Meanwhile, I guess you have workarounds already, but if you need a
better one, change "racket/src/cs/c/Makefile.in" where it has
SETUP_SETUP_FLAGS = @INSTALL_SETUP_FLAGS@ $(PLT_SETUP_OPTIONS) $(PLT_ISO)
to put `--no-user` in place of `@INSTALL_SETUP_FLAGS@`. The longer-term
repair is to fix `INSTALL_SETUP_FLAGS` in "configure".
Reply all
Reply to author
Forward
0 new messages