unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: [Fwd: autogen 5.9.8 doesn't build on IA64] -- libguile conflict
Date: Tue, 14 Jul 2009 09:14:17 -0700	[thread overview]
Message-ID: <668c430c0907140914o2cc46016h555d3d484a4ef863@mail.gmail.com> (raw)
In-Reply-To: <87zlb767tt.fsf@arudy.ossau.uklinux.net>

On Tue, Jul 14, 2009 at 12:29 AM, Neil Jerram<neil@ossau.uklinux.net> wrote:
> Bruce Korb <bruce.korb@gmail.com> writes:
>
>> 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
>
> Hi Bruce,
>
> This is a known problem, and on my list for addressing quite soon.
> Debian has a patch, which I guess would work for you too, so you may
> want to look at trying that.
>
> Regards,
>        Neil

Hi Neil,

It isn't clear to me how to patch autogen to cope with the issue,
unless I can detect the problem with some configury magic and
force autogen to not #include setjmp.h.  I think it is easier to just
require a different version of guile.  Anyway, my question is:

  How do I detect the broken installation of Guile?

that way, I can fiddle the configury stuff to do one thing or the other.
Thanks -Bruce




      reply	other threads:[~2009-07-14 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 20:17 [Fwd: autogen 5.9.8 doesn't build on IA64] -- libguile conflict Bruce Korb
2009-07-14  7:29 ` Neil Jerram
2009-07-14 16:14   ` Bruce Korb [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=668c430c0907140914o2cc46016h555d3d484a4ef863@mail.gmail.com \
    --to=bruce.korb@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).