From: Mark Patterson <mpatterson@physics.queensu.ca>
To: bug-guile@gnu.org
Subject: Conflict with HDF5 libraries
Date: Wed, 4 Feb 2009 12:21:49 -0500 [thread overview]
Message-ID: <698EDC07-174A-4215-8036-5356A57EDF7E@physics.queensu.ca> (raw)
Hello,
I've run into a conflict between guile (1.8.5) and HDF5 (1.8.1) on
Fedora 10. I'll post on both mailing lists as I'm not sure who is in
the best position to fix it.
HDF5 H5public.h near line 127 has:
#if H5_SIZEOF_LONG_LONG>0
# define long_long long long
... snip ...
#endif
which is still present in the latest 1.8.2 release.
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.
If HDF5 is loaded before guile, the typedef becomes:
typedef long long long long
which confuses gcc (and me). As a temporary fix, I added:
#undef long_long
just before the typedef in scmconfig-64. It is not clear to me which
approach for dealing with long_long is correct or how they can be made
to play well together.
I was trying to build MPB (http://ab-initio.mit.edu/wiki/index.php/
MPB) which is a nice piece of software that requires both guile and
HDF5.
Thank you,
Mark Patterson
next reply other threads:[~2009-02-04 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 17:21 Mark Patterson [this message]
2009-02-05 9:50 ` Conflict with HDF5 libraries Marijn Schouten (hkBst)
2009-02-05 16:33 ` Ken Raeburn
2009-03-21 21:14 ` Ludovic Courtès
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=698EDC07-174A-4215-8036-5356A57EDF7E@physics.queensu.ca \
--to=mpatterson@physics.queensu.ca \
--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).