From: Christian Kniep <C.Kniep-Pt+Xe7GJXK+P2YhJcF5u+nqWYbMAw+HU@public.gmane.org>
To: sebastien dugue <sebastien.dugue-6ktuUTfB/bM@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: infiniband-diags needs libibmad with 'mad_dump_mlnx_ext_port_info'
Date: Thu, 03 May 2012 10:55:09 +0200 [thread overview]
Message-ID: <4FA247ED.2030702@science-computing.de> (raw)
In-Reply-To: <20120503095144.708d32a6@b012350-ux>
Salut Sébastian,
omg, I am stupid... :)
Found the bad files:
/usr/lib64/libibmad.so
/usr/lib64/libibmad.so.5
/usr/lib64/libibmad.so.5.1.2
'yum erase libibmad' solved my problem.
Merci
Christian
Am 03.05.2012 09:51, schrieb sebastien dugue:
>
> Hi Christian,
>
> On Thu, 3 May 2012 06:26:04 +0000 (UTC)
> Christian Kniep <c.kniep@science-computing.de> wrote:
>
>> Hey list,
>>
>> I just compiled the newest version of libibumad,-ibmad, opensm and
>> infiniband-diags and I got an error I am not able to eliminate.
>> ####
>> checking for mad_dump_mlnx_ext_port_info in -libmad... no
>> configure: error: mad_dump_mlnx_ext_port_info() not found.
>> diags require libibmad with mad_dump_mlnx_ext_port_info support.
>> ####mad_dump_mlnx_ext_port_info
>> My installation on centos6.2 is discribed here:
>> https://github.com/ChristianKniep/QNIB/wiki/Installation
>>
>> How could I fix this?
>
> what does config.log tells you regarding the check for mad_dump_mlnx_ext_port_info?
>
> has libibmad been installed in the standard place? Maybe configure is finding an old
> libibmad that's previously been installed (and without mad_dump_mlnx_ext_port_info).
>
> Also beware of the lib vs lib64 thingy.
>
> Regards,
>
> Sébastien.
>
>>
>> Thanks & kind regards
>> Christian
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Freundliche Gruesse
Christian Kniep
_______________________________creating IT solutions
Christian Kniep, B.Sc. Inf science + computing ag
Senior Systems Engineer Hagellocher Weg 73
CAx Professional Services D-72070 Tuebingen, Germany
phone +49(0)7071 9457-283 fax +49(0)7071 9457-411
teamline +49(0)7071 9457-681 www.science-computing.de
--
Vorstandsvorsitzender/Chairman of the board of management:
Gerd-Lothar Leonhart
Vorstand/Board of Management:
Dr. Bernd Finkbeiner, Michael Heinrichs,
Dr. Arno Steitz, Dr. Ingrid Zech
Vorsitzender des Aufsichtsrats/
Chairman of the Supervisory Board:
Philippe Miltin
Sitz/Registered Office: Tuebingen
Registergericht/Registration Court: Stuttgart
Registernummer/Commercial Register No.: HRB 382196
next prev parent reply other threads:[~2012-05-03 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 6:26 infiniband-diags needs libibmad with 'mad_dump_mlnx_ext_port_info' Christian Kniep
[not found] ` <loom.20120503T081916-361-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2012-05-03 7:51 ` sebastien dugue
2012-05-03 8:55 ` Christian Kniep [this message]
[not found] ` <4FA247ED.2030702-Pt+Xe7GJXK+P2YhJcF5u+nqWYbMAw+HU@public.gmane.org>
2012-05-03 8:59 ` sebastien dugue
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=4FA247ED.2030702@science-computing.de \
--to=c.kniep-pt+xe7gjxk+p2yhjcf5u+nqwybmaw+hu@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastien.dugue-6ktuUTfB/bM@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