All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@valinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gnu-efi-1.1 released
Date: Thu, 15 Feb 2001 20:21:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005154@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205639@msgid-missing>

On Mon, Oct 30, 2000 at 01:55:19PM -0800, Stephane Eranian wrote:
> 
> Hi All,
> 
> I have uploaded version 1.1 of the gnu-efi package on our FTP site.
> 

Here is a patch to define INTERFACE_DECL for gcc.


H.J.
---
--- gnu-efi-1.1/inc/ia32/efibind.h.type	Mon Oct  9 17:49:02 2000
+++ gnu-efi-1.1/inc/ia32/efibind.h	Thu Feb 15 12:07:16 2001
@@ -206,3 +206,19 @@ typedef uint32_t   UINTN;
             (_if)->LoadInternal(type, name, entry)
 
 #endif /*  EFI_FW_NT  */
+
+/* 
+ *  Some compilers don't support the forward reference construct:
+ *   typedef struct XXXXX
+ * 
+ *  The following macro provide a workaround for such cases.
+ */
+#ifdef __GNUC__
+#define INTERFACE_DECL(x) struct x
+#else
+#ifdef NO_INTERFACE_DECL
+#define INTERFACE_DECL(x)
+#else
+#define INTERFACE_DECL(x) typedef struct x
+#endif
+#endif
--- gnu-efi-1.1/inc/ia64/efibind.h.type	Mon Oct  9 17:49:02 2000
+++ gnu-efi-1.1/inc/ia64/efibind.h	Thu Feb 15 12:05:34 2001
@@ -156,3 +156,18 @@ typedef uint64_t   UINTN;
 #define LOAD_INTERNAL_DRIVER(_if, type, name, entry)    \
         (_if)->LoadInternal(type, name, entry)
 
+/* 
+ *  Some compilers don't support the forward reference construct:
+ *   typedef struct XXXXX
+ * 
+ *  The following macro provide a workaround for such cases.
+ */
+#ifdef __GNUC__
+#define INTERFACE_DECL(x) struct x
+#else
+#ifdef NO_INTERFACE_DECL
+#define INTERFACE_DECL(x)
+#else
+#define INTERFACE_DECL(x) typedef struct x
+#endif
+#endif


  reply	other threads:[~2001-02-15 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30 21:55 [Linux-ia64] gnu-efi-1.1 released Stephane Eranian
2001-02-15 20:21 ` H . J . Lu [this message]
2001-02-16 10:38 ` Andreas Schwab
2001-02-16 16:30 ` H . J . Lu

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-105590693005154@msgid-missing \
    --to=hjl@valinux.com \
    --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.