On Mon, Jul 11, 2022 at 4:06 PM Marc Culler <[email protected]> wrote: > > On Mon, Jul 11, 2022 at 10:01 AM Dima Pasechnik <[email protected]> wrote: >> >> >> One way to fix it is to re-create ./configure from ./bootstrap > > > The problem with this is that the bootstrap script in beta5 generates > warnings about the exact same commands, but then it still goes ahead and > produces a configure script that requires those missing commands.
that's a bug in ./bootstrap then. (Frankly speaking I am sick and tired of that "no deps" setup we are supposed to maintain, it's such a timesink... Why are build tools a problem to have ?) Does ./bootstrap -D provide a better ./configure ? > > - Marc > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/CALcZXRHg%3DDdQE9E9pPTYaNXLp222pEFy7c98ZDHuKAEgJm%3Djvw%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAAWYfq2tAo-EHigFfxNdSjfYfkqTeYujzv3cfCQi99dQcHOuxw%40mail.gmail.com.
