unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Subject: Autoconf-like #defines in distributed header file
Date: Mon, 5 Aug 2002 13:54:24 +0200	[thread overview]
Message-ID: <15694.26481.139868.27521@meddo.cs.uu.nl> (raw)
In-Reply-To: <20020727165258.GA27310@www>


[just adding my 2 cents. I've ignored discussion till now.]

rm@fabula.de writes:
> 
> ... '#define's from the build phase of libguile leak into the
> software's build. '#define PACKAGE_VERSION ""' from scmconfig.h
> will override the softwares own version of the value and possibly
> introduce errant behaviour if the software uses this value for 
> its own version testing.

I just recompiled lilypnod with gcc3 and for some reason it
only now complains with .


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.)

-- 

Han-Wen Nienhuys   |   hanwen@cs.uu.nl    | http://www.cs.uu.nl/~hanwen/


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-08-05 11:54 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 [this message]
2002-08-05 16:30   ` Rob Browning

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=15694.26481.139868.27521@meddo.cs.uu.nl \
    --to=hanwen@cs.uu.nl \
    /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).