From: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: libmlx5 doesn't build on s390x
Date: Thu, 23 Mar 2017 14:08:33 -0400 [thread overview]
Message-ID: <5264980a-10fa-5c18-ff3a-2f2774c60eb6@redhat.com> (raw)
In-Reply-To: <20170323170228.GG29811-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On 2017-03-23 1:02 PM, Jason Gunthorpe wrote:
> On Thu, Mar 23, 2017 at 12:57:37PM -0400, Jarod Wilson wrote:
>> Not sure. From rpm's perspective, I'm trying arch s390x, but maybe gcc is
>> actually calling it s390.
>
> The output from build/CMakeFiles/CMakeError.log might help
>
> As well as this output:
>
> $ gcc -dM -E - < /dev/null
Unfortunately, this is sort of a black box situation for me at the
moment. I'm submitting the builds to our build system, which hands the
build job off to all relevant architectures. I can probably get a
reservation on an s390x system and poke manually though.
--
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
prev parent reply other threads:[~2017-03-23 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 12:51 libmlx5 doesn't build on s390x Jarod Wilson
[not found] ` <afe64964-4f10-0a00-0891-b97bf2c60b50-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-23 16:06 ` 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 [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=5264980a-10fa-5c18-ff3a-2f2774c60eb6@redhat.com \
--to=jarod-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@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