All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma-core_15-1_amd64.changes ACCEPTED into unstable
Date: Tue, 14 Nov 2017 19:58:43 +0100	[thread overview]
Message-ID: <1510685923.4026.41.camel@profitbricks.com> (raw)
In-Reply-To: <20171114184719.GC4263-uk2M96/98Pc@public.gmane.org>

Am Dienstag, den 14.11.2017, 11:47 -0700 schrieb Jason Gunthorpe:
> On Tue, Nov 14, 2017 at 11:51:01AM +0100, Benjamin Drung wrote:
> 
> > * Non-Linux architectures: One package is marked as architechture
> > "any"
> > instead of "linux-any". Thus the builds are tried on non-Linux
> > archs.
> > Expect a patch to come.
> 
> Yep
> 
> > * Architecture NOT able to do coherent DMA: Some providers will be
> > disabled and the install target fail to install the missing
> > providers.
> 
> I'm surprised, can you point me at a build log? I belive the cmake
> side should work?

Here is the build overview:
https://buildd.debian.org/status/package.php?p=rdma-core
The individual build logs are referenced from there.

There is already a Debian bug report for it:
https://bugs.debian.org/881731

You might want to answer to that report.

> I suppose we have a bit of a Debian problem here as things like
> mlx5dv will not compile on certain arches but their outputs are
> directly refenced in the debian/*.install files.. Do you know how to
> handle that?

There is no elegant way to handle that. The most elegant way I can come
up with is:

1) Have two install files debian/foo.install.full and
debian/foo.install.no-coherent-dma

2) Determine the build architecture in debian/rules and set
VARIANT=full or VARIANT=no-coherent-dma depending on the architecture.

3) Extent dh_auto_configure:

    cp debian/foo.install.$(VARIANT) debian/foo.install

4) Do the clean in dh_auto_clean:

    rm -f debian/foo.install

Any better idea?

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-11-14 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 23:00 rdma-core_15-1_amd64.changes ACCEPTED into unstable, unstable Debian FTP Masters
     [not found] ` <E1eENiD-000EaM-BG-zBwJlDMnrE7yUObV3Cmqeti2O/JbrIOy@public.gmane.org>
2017-11-14  2:37   ` Jason Gunthorpe
     [not found]     ` <20171114023711.GA22633-uk2M96/98Pc@public.gmane.org>
2017-11-14  7:20       ` Leon Romanovsky
     [not found]         ` <20171114072056.GP18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-14 10:51           ` rdma-core_15-1_amd64.changes ACCEPTED into unstable Benjamin Drung
     [not found]             ` <1510656661.4026.23.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 11:01               ` Leon Romanovsky
2017-11-14 18:47               ` Jason Gunthorpe
     [not found]                 ` <20171114184719.GC4263-uk2M96/98Pc@public.gmane.org>
2017-11-14 18:58                   ` Benjamin Drung [this message]
     [not found]                     ` <1510685923.4026.41.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-17 23:31                       ` Jason Gunthorpe

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=1510685923.4026.41.camel@profitbricks.com \
    --to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.