From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Autoconf-like #defines in distributed header file
Date: Mon, 05 Aug 2002 11:30:43 -0500 [thread overview]
Message-ID: <87u1m9w9n0.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <15694.26481.139868.27521@meddo.cs.uu.nl> (Han-Wen Nienhuys's message of "Mon, 5 Aug 2002 13:54:24 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> out/version.hh:6:1: let op: "PACKAGE_NAME" redefined
> In file included from /users/hanwen/usr/pkg/guile/include/libguile/__scm.h:157,
> from /users/hanwen/usr/pkg/guile/include/libguile.h:50,
> from /users/hanwen/usr/pkg/guile/include/guile/gh.h:50,
> from include/lily-guile.hh:18,
> from include/parse-scm.hh:6,
> from lexer.ll:31:
> /users/hanwen/usr/pkg/guile/include/libguile/scmconfig.h:562:1: let op: this is the location of the previous definition
>
>
> In any case, I think this should be fixed (I'll look into the
> discussion when mail.gnu.org becomes alive again.)
OK. I believe I've fixed this (at least the egregious PACKAGE_* bits)
in 1.5. This is a temp fix, but it's moving in the direction I
outlined in my previous msg about scmconfig.h/config.h, etc.
See the ChangeLog(s) for more details on the current modifications,
and please let me know if this doesn't address the problem at least to
the point that it's no longer release-critical.
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
prev parent reply other threads:[~2002-08-05 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 16:52 Autoconf-like #defines in distributed header file rm
2002-08-05 11:54 ` Han-Wen Nienhuys
2002-08-05 16:30 ` Rob Browning [this message]
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=87u1m9w9n0.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).