On Thu, 14 Nov 2019 at 19:59, Reuben Thomas <r...@sc3d.org> wrote:

> On Thu, 14 Nov 2019 at 12:51, Matthew Flatt <mfl...@cs.utah.edu> wrote:
>
>> At Wed, 13 Nov 2019 21:58:24 +0000, "'Reuben Thomas' via Racket Users"
>> wrote:
>> > While looking into implementing this, I discovered that
>> `racket/src/start/
>> > configure.ac`, which seems to have been introduced with the
>> introduction of
>> > CS, is not generated from racket/src/ac/*.m4, while all the other
>> > configure.ac's are.
>> >
>> > I guess this explains why the fix to `src/ac/path.m4` in commit
>> a56c984db0
>> > (inter alia) has not been applied to `start/configure.ac`?
>> >
>> > Since as far as I can tell, the putative `--disable-prefix` needs to be
>> > implemented in both `start/configure.ac` and `ac/path{,_arg}.m4`, I
>> thought
>> > it was worth sorting this out before trying to attempt the fix.
>>
>> Yes, it's definitely a mistake that "start/configure.ac" doesn't use
>> "src/ac/path.m4". (I must have lost track of that part when creating
>> "start/configure.ac" and other files out of the old single
>> "configure.ac".)
>>
>> A repair for that as part of adding `--disable-prefix` would be very
>> welcome.
>>
>
> I will look into that.
>

I've looked into it and I can't work out what start/*.ac are used. Having
read the various README.txt files and grepped around, I tried removing them
(start/configure.ac and start/install2.ac) and it didn't seem to prevent a
complete build from git checkout.

However, I see that some generated files like various "configure"s are
checked in, so maybe I'm overlooking something, a buried generated
reference to those files? (But I can't find install2 mentioned anywhere!)

-- 
https://rrt.sc3d.org

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAOnWdogvQBx%3DAx8O4M0nB1s%2BUSFT_W3ktqFyfq%2B4-6e0v%3D%3D6Ew%40mail.gmail.com.

Reply via email to