From: Vladimir Sokolovsky <vlad-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Jim Schutt <jaschut-4OHPYypu0djtX7QSmKvirg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rds-devel-N0ozoZBvEnrZJqsBc5GL+g@public.gmane.org
Subject: Re: rds-tools issue starting with OFED-1.5.2-20100718-0600.tgz
Date: Thu, 29 Jul 2010 10:08:48 +0300 [thread overview]
Message-ID: <4C512900.2050107@dev.mellanox.co.il> (raw)
In-Reply-To: <1280264327.4816.18.camel-mgfCWIlwujvg4c9jKm7R2O1ftBKYq+Ku@public.gmane.org>
Jim Schutt wrote:
snip
> rds-tools:
> -http://www.openfabrics.org/~vlad/ofed_1_5/rds-tools/rds-tools-1.5-1.src.rpm
> +http://www.openfabrics.org/downloads/rds-tools/rds-tools-2.0.3.tar.gz
>
>
>
> It also looks like, from
> http://oss.oracle.com/git/?p=agrover/rds-tools.git;a=summary
>
> that rds-tools now builds into two RPMs, rds-tools and rds-devel,
> but the OFED build scripts don't seem to know about that change.
>
> I'd like to learn how to write apps that use RDS, so I thought
> I needed rds.h to compile against, in hopes of running against the
> latest upstream kernel RDS. But, I can't seem to get it from
> the 1.5.2 daily snapshot, as a rds-devel rpm isn't getting installed.
>
> Is there somewhere else to get the appropriate rds.h from?
>
> Thanks -- Jim
>
Hi Jim,
Thank you for reporting this issue.
I added rds-devel support to OFED-1.5.2. It will be available in today's daily build.
Regards,
Vladimir
--
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:[~2010-07-29 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 20:58 rds-tools issue starting with OFED-1.5.2-20100718-0600.tgz Jim Schutt
[not found] ` <1280264327.4816.18.camel-mgfCWIlwujvg4c9jKm7R2O1ftBKYq+Ku@public.gmane.org>
2010-07-29 7:08 ` Vladimir Sokolovsky [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=4C512900.2050107@dev.mellanox.co.il \
--to=vlad-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=jaschut-4OHPYypu0djtX7QSmKvirg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rds-devel-N0ozoZBvEnrZJqsBc5GL+g@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