All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hanson <jhanson@sgi.com>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm 2.0 and 2.1 compile error
Date: Wed, 28 Sep 2005 09:46:01 -0400	[thread overview]
Message-ID: <pan.2005.09.28.13.45.57.358668@sgi.com> (raw)
In-Reply-To: 17208.63983.493938.764444@cse.unsw.edu.au

On Tue, 27 Sep 2005 09:51:11 +0200, Neil Brown wrote:

> On Monday September 26, raid@a2000.nu wrote:
>> I am trying to compile mdadm 2.x (currently running version 1.12)
>> 
>> On "make" I get the following fatal error for both 2.0 and 2.1:
>> 
>> In file included from super0.c:31:
>> /usr/include/asm/byteorder.h:6:2: #warning using private kernel header; 
>> include <endian.h> instead!
>> make: *** [super0.o] Error 1
>> 
>> any idea ?
> 
> This means your distro is crazy.  endian.h does not contain the
> defines that I need from byteorder.h.
> Just remove the '-Werror' from the Makefile and try again.

That resolved it for me.  Distro is RHEL 4 in my testing.
-- 
-----------------------------------------------------------------------
Jeff Hanson - jhanson@sgi.com - Field Technical Analyst

You can choose a ready guide in some celestial voice. 
If you choose not to decide, you still have made a choice. 
You can choose from phantom fears and kindness that can kill; 
I will choose a path that's clear 
I will choose freewill. - Lee/Lifeson/Peart



  reply	other threads:[~2005-09-28 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 20:20 mdadm 2.0 and 2.1 compile error Stephan van Hienen
2005-09-27  7:51 ` Neil Brown
2005-09-28 13:46   ` Jeff Hanson [this message]
2005-10-24 18:48   ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2005-09-23 17:03 Norman Schmidt

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=pan.2005.09.28.13.45.57.358668@sgi.com \
    --to=jhanson@sgi.com \
    --cc=linux-raid@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.