unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: Conflict with HDF5 libraries
Date: Sat, 21 Mar 2009 22:14:59 +0100	[thread overview]
Message-ID: <87k56id1d8.fsf@gnu.org> (raw)
In-Reply-To: 698EDC07-174A-4215-8036-5356A57EDF7E@physics.queensu.ca

Hello,

Sorry for the late reply.

Mark Patterson <mpatterson@physics.queensu.ca> writes:

> GUILE scmconfig-64.h near line 83 has:
>   typedef long long long_long;
> I tracked the origin of this line to gen-scmconfig.c, line 287 and it
> is present in the recent 1.8.6 release.

As you may have noticed, this is enclosed in:

  #if (SCM_ENABLE_DEPRECATED == 1)

I.e., Guile 1.8 configured with `--disable-deprecated' doesn't have this
problem.

I suggest that we leave it in the 1.8 series for compatibility and
remove it altogether in the next stable series.  Opinions?

Thanks,
Ludo'.





  parent reply	other threads:[~2009-03-21 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 17:21 Conflict with HDF5 libraries Mark Patterson
2009-02-05  9:50 ` Marijn Schouten (hkBst)
2009-02-05 16:33 ` Ken Raeburn
2009-03-21 21:14 ` Ludovic Courtès [this message]
2009-03-22 13:57   ` Andy Wingo

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=87k56id1d8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@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).