From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: multipath-tools: broken build system + warnings
Date: Wed, 07 Mar 2018 23:37:16 +0100 [thread overview]
Message-ID: <1520462236.11340.23.camel@suse.com> (raw)
In-Reply-To: <14bb2d20-3ace-909c-9c7c-99fc577dcc08@gmail.com>
On Wed, 2018-03-07 at 23:30 +0100, Xose Vazquez Perez wrote:
> On 03/07/2018 10:16 PM, Martin Wilck wrote:
>
> > On Wed, 2018-03-07 at 17:40 +0100, Xose Vazquez Perez wrote:
> > > Hi,
> > >
> > > It has to type "make" *twice* to build the full
> > > source code.
> >
> > Hm, strange. I need to double check. It doesn't happen with my tree
> > AFAICS.
>
> These are removed by "make":
> rm random.o weightedpath.o ontap.o hp_sw.o hds.o sysfs.o rdac.o
> const.o datacore.o emc.o iet.o
> rm tur.o emc_clariion.o hp_sw.o rdac.o readsector0.o cciss_tur.o
> rm nvme.o
>
Yes. That used to be the case before too, but now, on second
invocation, "make" sees the generated dependency file and thus builds
again.
I have a fix for it. Will post soon.
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2018-03-07 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 16:40 multipath-tools: broken build system + warnings Xose Vazquez Perez
2018-03-07 21:16 ` Martin Wilck
2018-03-07 22:30 ` Xose Vazquez Perez
2018-03-07 22:37 ` Martin Wilck [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=1520462236.11340.23.camel@suse.com \
--to=mwilck@suse.com \
--cc=Bart.VanAssche@wdc.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=xose.vazquez@gmail.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 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.