[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: request review: branch "wingo"
From: |
Ludovic Courtès |
Subject: |
Re: request review: branch "wingo" |
Date: |
Tue, 31 Mar 2009 23:31:07 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.90 (gnu/linux) |
Hello,
Andy Wingo <address@hidden> writes:
> .scm.go:
> $(MKDIR_P) `dirname address@hidden
> $(top_builddir)/pre-inst-guile \
> -l $(top_builddir)/libguile/stack-limit-calibration.scm \
> $(top_srcdir)/scripts/compile -o "$@" "$<"
>
> This will run the compile script, but since there is no entry point
> (-e), you just load the compile script then exit. No compilation
> happens.
Ouch, indeed. Mea culpa!
>> Besides, there's the thread about cross-compilation where we mention
>> building the compiler with an already installed Guile that may have an
>> inappropriate stack limit.
>
> I don't think that is relevant. Since the Guile that is running would
> choose a stack size appropriate for it, based on the host getrlimit,
> there would be no problem.
The already-installed Guile wouldn't use getrlimit(2) since that would
be an old 1.8.
> Linking against uninstalled libtool libraries works fine, as long as you
> don't install.
That's right, but that seems awkward to me, except for tests.
> Pkg-config is designed for uninstalled operation, from
> pkg-config(1):
OK, I didn't know that. Sorry for talking too fast.
> I have that too, but it adds a step to the debugging cycle. I don't
> think there's any harm in supporting this additional mode of hacking,
> which is only for hackers in any case.
Well, yes.
Thanks,
Ludo'.