From: Rob Browning <rlb@defaultvalue.org>
Cc: rm@fabula.de, Han-Wen Nienhuys <hanwen@cs.uu.nl>,
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>,
guile-devel@gnu.org
Subject: Re: Release Guile, now ;-) [was:] Re: GC rewrite, first version.
Date: Fri, 02 Aug 2002 09:36:38 -0500 [thread overview]
Message-ID: <87n0s572fd.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <200208020609.g7269Hb21312@Mirddin.farlep.net> (Sergey Poznyakoff's message of "Fri, 02 Aug 2002 09:09:17 +0300")
Sergey Poznyakoff <gray@Mirddin.farlep.net> writes:
> Yes, they were. It's not the libguile/scmconfig.h itself that causes
> the problem, it's primarily the PACKAGE_.* defines that cause it. They
> appeared recently. I guess if you remove them or just move them to
> some private header, the problem will be solved. Another solution
> would be to protect each PACKAGE_ define by an #ifdef, e.g.:
>
> #ifndef PACKAGE_STRING
> /* Define to the full name and version of this package. */
> # define PACKAGE_STRING ""
> #endif
>
> then any application could easily override them in its config.h
Yeah, but these shouldn't even be there.
For now, can you tell which defines are the real trouble makers? Are
there others than PACKAGE_STRING? I'm wondering if we can just fix
the major offenders for now and then fix it *right* for 1.6.2.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-02 14:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 22:54 GC rewrite, first version Han-Wen
2002-07-28 16:40 ` Rob Browning
2002-07-29 20:11 ` Dirk Herrmann
2002-07-29 21:04 ` Rob Browning
2002-07-29 22:05 ` Han-Wen
2002-07-31 17:03 ` Dirk Herrmann
2002-07-31 18:02 ` Han-Wen Nienhuys
2002-07-31 21:15 ` Rob Browning
2002-08-01 9:20 ` Release Guile, now ;-) [was:] " rm
2002-08-01 16:27 ` Rob Browning
2002-08-01 16:44 ` rm
2002-08-01 18:37 ` Sergey Poznyakoff
2002-08-01 22:21 ` Rob Browning
2002-08-02 6:09 ` Sergey Poznyakoff
2002-08-02 14:36 ` Rob Browning [this message]
2002-08-02 17:29 ` Sergey Poznyakoff
2002-08-02 18:10 ` Bruce Korb
2002-08-02 19:50 ` Rob Browning
2002-08-03 7:13 ` Sergey Poznyakoff
2002-08-04 20:43 ` Bruce Korb
2002-08-04 20:57 ` Sergey Poznyakoff
2002-08-01 22:40 ` Rob Browning
2002-08-02 9:35 ` rm
2002-08-02 11:59 ` rm
2002-08-02 15:00 ` Rob Browning
2002-08-02 14:50 ` Rob Browning
2002-08-01 9:59 ` Han-Wen Nienhuys
2002-08-01 8:46 ` Marius Vollmer
2002-07-31 18:46 ` Neil Jerram
2002-08-01 9:58 ` Han-Wen Nienhuys
2002-07-28 16:51 ` Michael Livshin
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=87n0s572fd.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=dirk@sallust.ida.ing.tu-bs.de \
--cc=guile-devel@gnu.org \
--cc=hanwen@cs.uu.nl \
--cc=rm@fabula.de \
/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).