On Sun, 17 Nov 2019 at 20:27, Reuben Thomas wrote:
> On Sun, 17 Nov 2019 at 06:35, Matthew Flatt wrote:
>
>> At Sat, 16 Nov 2019 18:32:00 +, Reuben Thomas wrote:
>> > On Sat, 16 Nov 2019 at 15:06, Matthew Flatt wrote:
>> >
>> > >
>> > > The checked-in `configure` scripts are generated by "m
On Sun, 17 Nov 2019 at 06:35, Matthew Flatt wrote:
> At Sat, 16 Nov 2019 18:32:00 +, Reuben Thomas wrote:
> > On Sat, 16 Nov 2019 at 15:06, Matthew Flatt wrote:
> >
> > >
> > > The checked-in `configure` scripts are generated by "make-configure" in
> > > "racket/src/ac", and that script does
At Sat, 16 Nov 2019 18:32:00 +, Reuben Thomas wrote:
> On Sat, 16 Nov 2019 at 15:06, Matthew Flatt wrote:
>
> >
> > The checked-in `configure` scripts are generated by "make-configure" in
> > "racket/src/ac", and that script doesn't refer to "start/configure.ac".
> >
>
> Thanks for the confi
On Sat, 16 Nov 2019 at 15:06, Matthew Flatt wrote:
>
> The checked-in `configure` scripts are generated by "make-configure" in
> "racket/src/ac", and that script doesn't refer to "start/configure.ac".
>
Thanks for the confirmation. What about start/install2.ac?
--
https://rrt.sc3d.org
--
You
At Fri, 15 Nov 2019 21:33:17 +, "'Reuben Thomas' via Racket Users" wrote:
> I've looked into it and I can't work out what start/*.ac are used.
Ah, right again. That explains why I didn't update "start/configure.ac"
to use "path.m4". It's because "start/configure.ac" isn't supposed to
exist. I
On Thu, 14 Nov 2019 at 19:59, Reuben Thomas wrote:
> On Thu, 14 Nov 2019 at 12:51, Matthew Flatt wrote:
>
>> At Wed, 13 Nov 2019 21:58:24 +, "'Reuben Thomas' via Racket Users"
>> wrote:
>> > While looking into implementing this, I discovered that
>> `racket/src/start/
>> > configure.ac`, whi
On Thu, 14 Nov 2019 at 12:51, Matthew Flatt wrote:
> At Wed, 13 Nov 2019 21:58:24 +, "'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
>
At Wed, 13 Nov 2019 21:58:24 +, "'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 othe
On Wed, 13 Nov 2019 at 13:40, Matthew Flatt wrote:
>
> Maybe the solution is to add `--disable-prefix` and have the top-level
> makefile use that along with `--enable-origtree`?
>
Sounds good to me.
While looking into implementing this, I discovered that `racket/src/start/
configure.ac`, which
At Tue, 12 Nov 2019 22:47:33 +, Reuben Thomas wrote:
> Is there
> some reason configure can't test `enable_origtree`? Is there some time the
> build system is supposed to build in-tree even without --enable-origtree?
> If so, could it test `"${prefix}" = "NONE" -o "${enable_origtree}" = "yes"`?
On Tue, 12 Nov 2019 at 17:53, Matthew Flatt wrote:
> At Thu, 7 Nov 2019 23:14:52 +, "'Reuben Thomas' via Racket Users"
> wrote:
> > I have a CONFIG_SITE environment variable which contains the following
> line:
> >
> > test "$prefix" = NONE && prefix="$HOME_LOCAL"
> >
> > (HOME_LOCAL is set t
At Thu, 7 Nov 2019 23:14:52 +, "'Reuben Thomas' via Racket Users" wrote:
> I have a CONFIG_SITE environment variable which contains the following line:
>
> test "$prefix" = NONE && prefix="$HOME_LOCAL"
>
> (HOME_LOCAL is set to $HOME/.local)
>
> Things then go wrong because racket/src/start/
I have a CONFIG_SITE environment variable which contains the following line:
test "$prefix" = NONE && prefix="$HOME_LOCAL"
(HOME_LOCAL is set to $HOME/.local)
Things then go wrong because racket/src/start/configure.ac code relies on
prefix still being set to NONE in order to finally set prefix t
13 matches
Mail list logo
