public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdma-core packaging and multilib
Date: Tue, 14 Mar 2017 12:17:08 -0600	[thread overview]
Message-ID: <20170314181708.GA25495@obsidianresearch.com> (raw)
In-Reply-To: <bb6b2274-a120-6a16-0025-4c0b1b090029-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Tue, Mar 14, 2017 at 02:02:15PM -0400, Jarod Wilson wrote:

> Report from TEST_MULTILIB:
> [BAD] [ibacm] Subpackage ibacm is not multilib-clean for x86_64 vs i686: 2
> files have non-equal 32/64bit content:
>   /usr/share/man/man7/ibacm_prov.7.gz
>   /etc/rdma/ibacm_opts.cfg

Yep

> ibacm_prov.7.gz on x86_64 vs i686:
> ...
> -2. be installed under a configured directory, eg., /usr/lib64/ibacm;
> +2. be installed under a configured directory, eg., /usr/lib/ibacm;
> ...
> 
> Similar for ibacm_opts.cfg:
> 
> -# provider_lib_path /usr/lib64/ibacm
> +# provider_lib_path /usr/lib/ibacm
> 
> Not sure what the ideal resolution is for this. I'd rather not put in the
> wrong path for one arch or the other, and I think lib64 isn't used
> universally by all 64-bit distros.

cmake substitutes in the correct path string at build time.

If you want these files to be identical then we cannot include the
path names at all, just put place holders and say to run 'ib_acme -D
. -O' to learn the configured value.

Jason
--
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-03-14 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 18:02 rdma-core packaging and multilib Jarod Wilson
     [not found] ` <bb6b2274-a120-6a16-0025-4c0b1b090029-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-14 18:17   ` Jason Gunthorpe [this message]
     [not found]     ` <20170314181708.GA25495-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-15 16:34       ` Doug Ledford
     [not found]         ` <79c87a2b-6b8e-d2f3-0246-bb549c52f8f3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-15 16:45           ` 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=20170314181708.GA25495@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=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