From: Michael Tiedtke <michele.titke@o2online.de>
To: guile-user@gnu.org
Subject: Re: Guile 1.8 / Viper System Interface
Date: Sun, 28 Jun 2015 12:12:39 +0200 [thread overview]
Message-ID: <558FC897.7060501@o2online.de> (raw)
In-Reply-To: <87381csvr6.fsf@zigzag.favinet>
On 27/06/2015 23:10, Thien-Thi Nguyen wrote:
> () David Pirotte <david@altosw.be>
> () Fri, 26 Jun 2015 16:36:30 -0300
>
> > 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
>
> I'm still interested. If the new fork can handle all the stuff
> (w/o breakage) at: <http://www.gnuvola.org/software/> then i
> have nothing against it.
>
I don't think it still is able evaluate elisp. My current reorganization
approach to the task at hand as included.
I'm just trying to remember how to compile and link C files w/o all the
auto-mess. That was
- cc hello.c (for one file)
- cc -o hello hello.c world.c ... (for n files)
and linking against a static library was ... well, there is time - a lot
of time. Do you want to have the current tarball?
* Bugs & Maintenance Issues
** TODO Remove mingw32 support
** TODO Trash Candidates
*** ice-9
**** emacs.scm
**** gds-server.scm
**** gds-client.scm
**** gap-buffer.scm
** TODO Rename libguile or guile first
* Revert
** Build Manualities
*** Manual install of srfi/makeinstall
*** make clean is sometimes not enough
- rm -r .libs/ .deps/ in libguile
*** TODO Remove lang.doc references
*** GNU libtool version match to system
- 2.4 instead of 2.4.2
- revision 1.3293 instead 1.3337
- in aclocal.m4 and in configure
- redo this everytime autconf is run
*** libtool is missing (environment) variables
"export tool_oldlib=.libs/libguile.a" etc.
** 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
** 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-28 10:12 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
2015-06-27 21:10 ` Thien-Thi Nguyen
2015-06-28 10:12 ` Michael Tiedtke [this message]
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=558FC897.7060501@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).