public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: linux-2.5 tree no longer builds.
Date: Fri, 06 Feb 2004 17:20:07 +0000	[thread overview]
Message-ID: <20040206172007.GA19538@lnx-holt> (raw)

It appears that the following:

ChangeSet 1.1532.9.160 2004/02/04 10:54:15 akpm@osdl.org
  [PATCH] Fix ptrace in the vsyscall dso area
  
  From: Roland McGrath <roland@redhat.com>
  
  The #include is the part of this patch that matters, so the #ifdef below
  works.

breaks the linux.bkbits.net/linux-2.5 tree for ia64 with the following:

arch/ia64/ia32/elfcore32.h:20: conflicting types for `elf_gregset_t'
include/asm/elf.h:160: previous declaration of `elf_gregset_t'
arch/ia64/ia32/elfcore32.h:22: conflicting types for `elf_fpregset_t'
include/asm/elf.h:163: previous declaration of `elf_fpregset_t'
arch/ia64/ia32/elfcore32.h:23: conflicting types for `elf_fpxregset_t'
include/asm/elf.h:157: previous declaration of `elf_fpxregset_t'
In file included from arch/ia64/ia32/binfmt_elf32.c:22:
arch/ia64/ia32/elfcore32.h:69:1: warning: "ELF_CORE_COPY_REGS" redefined
In file included from include/linux/elf.h:5,
                 from include/linux/mm.h:15,
                 from arch/ia64/ia32/binfmt_elf32.c:15:
include/asm/elf.h:169:1: warning: this is the location of the previous definition



I commented out the #include in linux/mm.h and everything builds fine.
I haven't booted it yet.

Does anybody have a correct fix?

Thanks,
Robin Holt

             reply	other threads:[~2004-02-06 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 17:20 Robin Holt [this message]
2004-02-06 18:31 ` linux-2.5 tree no longer builds Martin Hicks

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=20040206172007.GA19538@lnx-holt \
    --to=holt@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox