From: Randolph Chung <tausq@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] epilogue count exceeds number of nested prologues
Date: Tue, 09 Apr 2002 05:23:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905424@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905403@msgid-missing>
> For some reason, I don't see this in my configure.in. Was this added
> by the Debian patch? In principle, it's a good idea to check for this
> macro, but I the check needs to be different. To get it to compile,
> FFI_STATIC_CLOSURE() would have to be declared at the outermost level.
> Alternatively, perhaps you can just grep for this macro in ffi.h (I
> think autoconf has support for doing this).
<sigh> you are right, i will go poke the Debian maintainer about this
now. Sorry for the diversion.
randolph
next prev parent reply other threads:[~2002-04-09 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 0:17 [Linux-ia64] epilogue count exceeds number of nested prologues Randolph Chung
2002-04-08 15:52 ` David Mosberger
2002-04-08 17:25 ` David Mosberger
2002-04-09 4:46 ` David Mosberger
2002-04-09 5:00 ` David Mosberger
2002-04-09 5:09 ` Randolph Chung
2002-04-09 5:23 ` Randolph Chung [this message]
2002-04-09 5:56 ` Jeff Licquia
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590701905424@msgid-missing \
--to=tausq@debian.org \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.