From: Michael Tiedtke <michele.titke@o2online.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile 1.8 / Viper System Interface
Date: Fri, 26 Jun 2015 22:23:22 +0200 [thread overview]
Message-ID: <558DB4BA.7000103@o2online.de> (raw)
In-Reply-To: <20150626163630.05833f4d@capac>
On 26/06/2015 21:36, David Pirotte wrote:
> Hi Michael,
>
>> Sorry, you got me wrong. This is an announcement thread for those
>> interested.
> None of us is interested in guile-1.8, please use guile-2
>
> Cheers,
> David
Sorry, today I exterminated elisp and emacs support from my 1.8 branch.
Libtool is my pet, no matter what ...
(Don't take this seriously.)
* Bugs & Maintenance Issues
** Replay: UNIX tools are evil
*** Manual install of srfi/makeinstall
*** search tags: emacs, elisp, lisp, nil and validate.h contains
... which is only used once in list.c
*** gcc warnings should not be errors (configure.in?)
search for implicit definition warnings to pull out unwanted lisps
*** libtool is missing an (environment) variable
"export tool_oldlib=.libs/libguile.a" etc
*** Remove elisp
- remove directory lang
- remove file test-suite/tests/elisp.test
- remove all elisp from file configure
- remove lang from Makefile.am
- remove build-aux/elisp-comp
- remove elisp from all files
- move directory emacs to trash
- remove file libguile/lang.h and libguile/lang.c
** Rename libguile
** Removing readline
** Removing ELisp [2015-06-25 gio]
- rename SCM_NULL_OR_NIL_P to scm_is_null [2015-06-26 ven]
next prev parent reply other threads:[~2015-06-26 20:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 5:37 Guile 1.8 / Viper System Interface Michael Tiedtke
2015-06-26 6:39 ` David Pirotte
2015-06-26 10:16 ` Michael Tiedtke
2015-06-26 19:36 ` David Pirotte
2015-06-26 20:23 ` Michael Tiedtke [this message]
2015-06-27 21:10 ` Thien-Thi Nguyen
2015-06-28 10:12 ` Michael Tiedtke
2015-06-28 15:19 ` klaus schilling
2015-06-28 16:22 ` David Kastrup
2015-07-06 15:15 ` You can pick a flower! (was VSI) Michael Tiedtke
2016-08-25 15:34 ` Thien-Thi Nguyen
2015-06-28 20:18 ` Guile 1.8 / Viper System Interface Michael Titke
2015-06-28 20:18 ` Michael Tiedtke
2015-06-29 7:11 ` Marco Maggi
2015-06-29 7:55 ` David Kastrup
2015-06-29 8:56 ` Michael Tiedtke
2015-06-29 14:42 ` Tristan Colgate
2015-06-29 14:54 ` David Kastrup
2015-06-29 19:52 ` Michael Tiedtke
2015-06-29 20:15 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=558DB4BA.7000103@o2online.de \
--to=michele.titke@o2online.de \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).