unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: guile-devel@gnu.org
Subject: [Fwd: autogen 5.9.8 doesn't build on IA64] -- libguile conflict
Date: Sat, 11 Jul 2009 13:17:26 -0700	[thread overview]
Message-ID: <4A58F356.5060304@sbcglobal.net> (raw)

Hi,

I just got this bug report for my project.
My version of the __scm.h header guards the definition of the type
with "#ifdef vms" and "#ifdef _CRAY1".  If there is a version of
lib guile around that doesn't guard it, could you let me know?
I'll make my project error or on an incompatible Guile in that case.

Thanks -Bruce

-------- Original Message --------
Subject: [ autogen-Bugs-2820112 ] autogen 5.9.8 doesn't build on IA64
Date: Sat, 11 Jul 2009 16:56:52 +0000
From: SourceForge.net <noreply@sourceforge.net>
To: noreply@sourceforge.net

Bugs item #2820112, was opened at 2009-07-11 16:56
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=103593&aid=2820112&group_id=3593

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: autogen
Group: autogen
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Bruce Korb (bkorb)
Summary: autogen 5.9.8 doesn't build on IA64

Initial Comment:
Invoking make on autogen 5.9.8 stops with the following error:
 'error: conflicting types for 'jmp_buf'. gcc 4.4.0 shows that
 the type is defined in both /usr/include/setjmp.h and guile's
 libguile/__scm.h. For IA64 those type definitions differ, indeed.
 Guile version I use: 1.8.7.




             reply	other threads:[~2009-07-11 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 20:17 Bruce Korb [this message]
2009-07-14  7:29 ` [Fwd: autogen 5.9.8 doesn't build on IA64] -- libguile conflict Neil Jerram
2009-07-14 16:14   ` Bruce Korb

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=4A58F356.5060304@sbcglobal.net \
    --to=bruce.korb@gmail.com \
    --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).