From: Clinton Ebadi <clinton@unknownlamer.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: ttn's build system [was: Extended -e syntax]
Date: Wed, 10 Mar 2004 17:28:19 -0500 [thread overview]
Message-ID: <200403101728.31114.clinton@unknownlamer.org> (raw)
In-Reply-To: <87n06uvuy4.fsf@ivanova.rotty.yi.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 06 March 2004 10:47, Andreas Rottmann wrote:
> Clinton Ebadi <clinton@unknownlamer.org> writes:
> > I've been trying to get guile-pg to compile and it hasn't been
> > working out too well...ttn uses his new build system stuff with
> > guile-pg and they only work with Guile 1.4.x unless Guile has
> > support for his extended -e syntax.
> Have you already started this? I'm especially interested in the
> build-system, and will break that out into a separate piece, since I
> intend to use it for the Guile-Library thing and possible at a later
> point in Guile-Gnome. I can't wait for this being perhaps eventually
> integrated into Guile (I suspect this might take *some* time to
> happen). So if you haven't started tackling "porting" the build
> system, it *might* make sense to wait for what I'll produce, which
> will be a piece of software building on Guile, but not integrated into
> guile-tools. This means just shipping it with Guile in the future,
> making guile-tools tie it in, could be an alternative of a direct
> port, avoiding duplicate effort.
I haven't started to work on the build system stuff so I'll focus on other
stuff for now (modsup and friends).
- --
http://unknownlamer.org
AIM:unknownlamer IRC:unknown_lamer@freenode#hprog
I use Free Software because I value freedom over features.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAT5aMdgGh8PQDV0sRAh9UAJ0QLDHlH4y0aYgwssoi5/3jGTD7kACgo9OV
w2PU+lnOA2IfAkknrVTZEGU=
=9Ou9
-----END PGP SIGNATURE-----
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-10 22:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 3:32 Extended -e syntax Clinton Ebadi
2004-03-01 5:04 ` Andreas Rottmann
2004-03-01 11:10 ` Thien-Thi Nguyen
2004-03-01 14:27 ` Arch and Guile Andreas Rottmann
2004-03-01 19:04 ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14 ` ITLA Andreas Rottmann
2004-03-01 21:55 ` ITLA Tom Lord
2004-03-02 0:11 ` ITLA Andreas Rottmann
2004-03-02 2:50 ` ITLA Tom Lord
2004-03-02 14:04 ` ITLA Andreas Rottmann
2004-03-02 3:26 ` ITLA Miles Bader
2004-03-03 11:22 ` ITLA Neil Jerram
2004-03-03 11:55 ` ITLA Andreas Rottmann
2004-03-04 13:55 ` Archive of library modules for Guile Andreas Rottmann
2004-03-04 20:49 ` Neil Jerram
2004-03-04 23:00 ` Andreas Rottmann
2004-03-07 17:33 ` Thamer Al-Harbash
2004-03-07 18:17 ` Thien-Thi Nguyen
2004-03-01 23:07 ` Arch and Guile Thien-Thi Nguyen
2004-03-02 0:23 ` Andreas Rottmann
2004-03-03 13:01 ` Thien-Thi Nguyen
2004-03-01 11:21 ` Extended -e syntax Thien-Thi Nguyen
2004-03-01 20:20 ` Christopher Cramer
2004-03-02 4:55 ` Clinton Ebadi
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
2004-03-10 18:59 ` ttn's build system Andreas Rottmann
2004-03-10 22:28 ` Clinton Ebadi [this message]
2004-03-10 23:22 ` ttn's build system [was: Extended -e syntax] Tom Lord
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=200403101728.31114.clinton@unknownlamer.org \
--to=clinton@unknownlamer.org \
--cc=guile-devel@gnu.org \
--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).