Hello,
* Jan Nieuwenhuizen wrote on Sun, Mar 20, 2011 at 09:08:20AM CET:
It would be nicer still if looking in /usr at compile/build time could
be turned off (from your use cases that seems to be possible), or
be turned off for $DESTDIR builds. That could be done with a single
flag. It
Ralf Wildenhues schreef op zo 20-03-2011 om 09:21 [+0100]:
Bruno already explained why it is not a good idea to let DESTDIR
be the indicator of whether to look in /usr or not.
Ouch, I think I missed that. Does someone have a pointer?
Also, why look in /usr before looking in gcc's library
* Jan Nieuwenhuizen wrote on Sun, Mar 20, 2011 at 09:34:37AM CET:
Ralf Wildenhues schreef op zo 20-03-2011 om 09:21 [+0100]:
Bruno already explained why it is not a good idea to let DESTDIR
be the indicator of whether to look in /usr or not.
Ouch, I think I missed that. Does someone
Hello!
Andy Wingo wi...@pobox.com writes:
It's true that a simple command-line argument and fluid could work, but
the situation will get more complicated, so we will need some part of
Guile to define the host and target triplets. That's the questions I
was really asking: where in Guile to
Hi :)
On Sun 20 Mar 2011 14:50, l...@gnu.org (Ludovic Courtès) writes:
There’s already ‘%host-type’.
Ah, cool.
However, I don’t think defining ‘%target-type’ would make sense
since:
1. Of the GNU triplet, only the $target_arch matters for bytecode;
2. You can really choose at
Hi!
Andy Wingo wi...@pobox.com writes:
On Sun 20 Mar 2011 14:50, l...@gnu.org (Ludovic Courtès) writes:
[...]
However, I don’t think defining ‘%target-type’ would make sense
since:
1. Of the GNU triplet, only the $target_arch matters for bytecode;
2. You can really choose at
Hello Unicode fellows! :-)
Mark H Weaver m...@netris.org writes:
Andy Wingo wi...@pobox.com writes:
Ludovic, Andy and I discussed this on IRC, and came to the conclusion
that UTF-8 should be the encoding assumed by functions such as
scm_c_define, scm_c_define_gsubr,
On Sun 20 Mar 2011 22:31, l...@gnu.org (Ludovic Courtès) writes:
What I meant to say here, is that via a couple of knobs akin to
‘current-target-endianness’, you could actually cross-build for any
target.
Yes, provided you have the compiler of course.
Thus ‘%target-type’ would be
Hi Mark,
Mark H Weaver m...@netris.org writes:
l...@gnu.org (Ludovic Courtès) writes:
We keep wide (UTF-32) stringbufs as-is, but we change narrow stringbufs
to UTF-8, along with a flag that indicates whether it is known to be
ASCII-only.
The whole point of the narrow/wide distinction was
Hi!
Thanks for the brave threading debugging. :-)
Andy Wingo wi...@pobox.com writes:
No, the issue is elsewhere, that the thread-exit handlers were not being
called
I just tried with 60582b7c2a495957012f9a20cd8691dc6307a850 and
‘on_thread_exit’ /is/ called after something like
Hey!
Andy Wingo wi...@pobox.com writes:
it has a pleasant subject-verb-object when you say it: Guido, compile
my-file.scm.
Is the pun[*] intended? :-)
FWIW I’m happy with the verbose name and I fear the joke wouldn’t be to
everyone’s taste. I’d also be happy with a shorter name, though.
Hi Andy,
On Thu, 17 Mar 2011, Andy Wingo wrote:
[...]
(1) Please provide a means by which the debugger prompt (recursive REPL)
can be turned off/on. Both a 'hook' (like COMMON-LISP:DEBUGGER-HOOK
plus COMMON-LISP:ABORT) or a REPL command would be OK with me.
I mis-type too
12 matches
Mail list logo
