public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: libmlx5 doesn't build on s390x
Date: Thu, 23 Mar 2017 08:51:21 -0400	[thread overview]
Message-ID: <afe64964-4f10-0a00-0891-b97bf2c60b50@redhat.com> (raw)

Not sure if it's intentional, but in my adventure of the past day or two 
to get rdma-core v13 building across all the arches I need to build it 
for, I discovered that the mlx5 bits silently don't build on s390x. No 
build failure, they just aren't attempted, so far as I can see. The only 
sign of failure was when rpm %files globs failed to locate mlx5 bits.

I noted that mlx4 has some s390x-specific trickery in 
providers/mlx4/mmio.h, and wondered if something similar was required 
for mlx5, or if "does not work on s390x and isn't expected to" is the 
norm. Currently, my builds are excluding mlx5 support on s390x due to 
the current state.

-- 
Jarod Wilson
jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
--
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

             reply	other threads:[~2017-03-23 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 12:51 Jarod Wilson [this message]
     [not found] ` <afe64964-4f10-0a00-0891-b97bf2c60b50-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-23 16:06   ` libmlx5 doesn't build on s390x Yishai Hadas
     [not found]     ` <36a02b19-5b50-10f6-f3da-13d4a67f50c2-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-03-23 16:50       ` Jarod Wilson
     [not found]         ` <22f0dfe4-bf35-02cf-df73-ef7b59295015-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-23 16:58           ` Jason Gunthorpe
     [not found]             ` <20170323165800.GC29811-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-23 18:12               ` Jarod Wilson
2017-03-23 16:10   ` Jason Gunthorpe
     [not found]     ` <20170323161017.GB29811-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-23 16:57       ` Jarod Wilson
     [not found]         ` <100aafc9-21a6-8aed-47c3-220f0feb82b1-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-23 17:02           ` Jason Gunthorpe
     [not found]             ` <20170323170228.GG29811-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-23 18:08               ` Jarod Wilson

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=afe64964-4f10-0a00-0891-b97bf2c60b50@redhat.com \
    --to=jarod-h+wxahxf7alqt0dzr+alfa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox