From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] ib/mgmt: fix build under windows stack
Date: Wed, 9 Jun 2010 09:48:00 +0300 [thread overview]
Message-ID: <20100609064800.GA20172@me> (raw)
In-Reply-To: <CF9C39F99A89134C9CF9C4CCB68B8DDF255F462DED-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 13:15 Wed 02 Jun , Hefty, Sean wrote:
> Fix warnings in windows build.
>
> These are typecasts in several places, with a couple additional changes
> needed to libibnetdisc. Windows uses ISO definitions instead of
> POSIX definitions, so calls like _read, _write, etc. are used on
> Windows instead of read, write. The result is that internal functions
> are renamed with an ibnd prefix.
>
> In order to handle ibdebug exported from libibmad, Windows need to mark
> the variable as a 'dllexport' from libibmad, but as 'dllimport' for users.
> Since libibnetdisc wants to 'dllimport' ibdebug from libibmad, while
> 'dllexporting its own functions, it requires a separate 'MAD_EXPORT' like
> definition to allow this.
>
> Signed-off-by: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Applied. Thanks.
Sasha
--
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-06-09 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 20:15 [PATCH] ib/mgmt: fix build under windows stack Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF255F462DED-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-06-09 6:48 ` Sasha Khapyorsky [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=20100609064800.GA20172@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.