[openib-general] Conflicting typedefs for "ib_gid_t"

mlakshmanan at silverstorm.com mlakshmanan at silverstorm.com
Mon Aug 14 11:51:23 PDT 2006


>  
> This is a similar but more mainstream example of the conflicts.  A previous one was reported last week in terms of CM. Still not sure of the best resolution for this.
>  
> Do you really need both includes ?
>  

The userspace tool shows a textual representation of a HCA port's capability mask. So it 
requires the port capability bit definitions in ib_types.h. And I require mad.h for the MAD API.

> -- Hal

Thanks,

Madhu
> 
> ________________________________
> 
> From: openib-general-bounces at openib.org on behalf of Lakshmanan, Madhu
> Sent: Mon 8/14/2006 12:19 PM
> To: openib-general at openib.org
> Subject: [openib-general] Conflicting typedefs for "ib_gid_t"
> 
> 
> 
> 
> 
> In .../include/infiniband/mad.h,  it is:
> 
>     typedef uint8_t ib_gid_t[16];
> 
> In .../include/infiniband/iba/ib_types.h, it is:
> 
>     #include <complib/cl_packon.h>
>     typedef union _ib_gid
>     {
>         uint8_t raw[16];
>         struct _ib_gid_unicast
>         {
>             ib_gid_prefix_t prefix;
>             ib_net64_t      interface_id;
> 
>         } PACK_SUFFIX unicast;
> 
>         struct _ib_gid_multicast
>         {
>             uint8_t         header[2];
>             uint8_t         raw_group_id[14];
> 
>         } PACK_SUFFIX multicast;
> 
>     } PACK_SUFFIX ib_gid_t;
>     #include <complib/cl_packoff.h>
> 
> I need to include both files for a user space tool and I'm getting a compile error due to the conflict. Is it not the norm for a user space application to include both files?
> Appreciate any thoughts on this.
> 
> Madhu Lakshmanan
> Silverstorm Technologies, Inc.
> mlakshmanan at silverstorm.com      
> 
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
> 
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
> 
> 
> 
> 







More information about the general mailing list