<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic gSOAP 2.8.3 Cross-Compilation in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/gSOAP-2-8-3-Cross-Compilation/m-p/204877#M11650</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone successfully cross-compiled gSOAP 2.8.3+ and created/ran a gSOAP server on the i.MX53 QSB? &amp;nbsp;I have successfully cross-compiled and installed gSOAP 2.8.3, but all server-side application fail because all gSOAP socket bind calls set the IPV6_V6ONLY socket option and then fail with the error ENOPROTOOPT (verified with strace).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know I have IPv6 support in my kernel (I'm running the 2.6.35.3 freescale linux kernel), because I enabled it in the kernel config and I can see the if_inet6 file in /proc/net. &amp;nbsp;Unfortunately, i can't simply use the latest release of gSOAP because the lastest doesn't work software. &amp;nbsp;Has anyone encountered this before or have any ideas? &amp;nbsp;Any help would be greatly appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Jan 2012 01:43:29 GMT</pubDate>
    <dc:creator>DonaldR_PooleJr</dc:creator>
    <dc:date>2012-01-20T01:43:29Z</dc:date>
    <item>
      <title>gSOAP 2.8.3 Cross-Compilation</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/gSOAP-2-8-3-Cross-Compilation/m-p/204877#M11650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone successfully cross-compiled gSOAP 2.8.3+ and created/ran a gSOAP server on the i.MX53 QSB? &amp;nbsp;I have successfully cross-compiled and installed gSOAP 2.8.3, but all server-side application fail because all gSOAP socket bind calls set the IPV6_V6ONLY socket option and then fail with the error ENOPROTOOPT (verified with strace).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know I have IPv6 support in my kernel (I'm running the 2.6.35.3 freescale linux kernel), because I enabled it in the kernel config and I can see the if_inet6 file in /proc/net. &amp;nbsp;Unfortunately, i can't simply use the latest release of gSOAP because the lastest doesn't work software. &amp;nbsp;Has anyone encountered this before or have any ideas? &amp;nbsp;Any help would be greatly appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Jan 2012 01:43:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/gSOAP-2-8-3-Cross-Compilation/m-p/204877#M11650</guid>
      <dc:creator>DonaldR_PooleJr</dc:creator>
      <dc:date>2012-01-20T01:43:29Z</dc:date>
    </item>
    <item>
      <title>Re: gSOAP 2.8.3 Cross-Compilation</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/gSOAP-2-8-3-Cross-Compilation/m-p/204878#M11651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Update&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;It seems that the only way around this is to comment out the &lt;EM&gt;#ifdef WITH_IPV6_V6ONLY&lt;/EM&gt; and &lt;EM&gt;#ifdef WITH_NO_IPV6_V6ONLY&lt;/EM&gt;&amp;nbsp;socket option code in the stdsoap2.c and stdsoap2.cpp files of the gsoap source. &amp;nbsp;Not sure why I would have to modify the gSOAP code if I didn't configure gSOAP with IPv6 enabled, but nonetheless it worked and I don't get anymore IPv6_V6ONLY bind errors from my gSOAP server apps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, I am using the Sourcery Codebench Lite Edition for ARM GNU/Linux version 2011.09-70.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jan 2012 15:23:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/gSOAP-2-8-3-Cross-Compilation/m-p/204878#M11651</guid>
      <dc:creator>DonaldR_PooleJr</dc:creator>
      <dc:date>2012-01-21T15:23:34Z</dc:date>
    </item>
  </channel>
</rss>

