From: Neil Brown <neilb@suse.de>
To: Maurice Hilarius <maurice@harddata.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm 2.6.5 compile issue
Date: Mon, 19 May 2008 12:09:45 +1000 [thread overview]
Message-ID: <18480.57705.875663.14438@notabene.brown> (raw)
In-Reply-To: message from Maurice Hilarius on Friday May 16
On Friday May 16, maurice@harddata.com wrote:
> Having grabbed sources for mdadm 2.6.5, we tried 'mdassemble.static'
> This does not really compile "as is" so it made for some head scratching moments.
>
> If I use MDASSEMBLE_AUTO=1 with make, then mdassemble,
> or mdassemble.static - which is now the same thing,
> does not link because sysfs.c is not on the list of mdassemble sources.
>
> It apparently needs to be.
>
> This was not the case in the past.
I was looking for an excuse to release 2.6.6 quickly as there was
something I forgot to include in 2.6.5.
This was the excuse. Try 2.6.6 :-)
Thanks,
NeilBrown
prev parent reply other threads:[~2008-05-19 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 21:56 mdadm 2.6.5 compile issue Maurice Hilarius
2008-05-19 2:09 ` Neil Brown [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18480.57705.875663.14438@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=maurice@harddata.com \
/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 NNTP newsgroup(s).