<?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 Re: _XOPEN_SOURCE_EXTENDED question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284632#M672317</link>
    <description>&amp;gt;Can you tell me how I can incorporate this command line option in GCC prior to running the Qt configure script?&lt;BR /&gt;&lt;BR /&gt;I would have thought CXXFLAGS would do it.  Can you look in the Qt configure script?&lt;BR /&gt;&lt;BR /&gt;You could wrap this option with the compiler and then pass in something like:&lt;BR /&gt;./configure -platform hp-g++-64 cc="/opt/hp-gcc64/bin/g++ -muinx=93"&lt;BR /&gt;&lt;BR /&gt;But you would want to use the one for C++.</description>
    <pubDate>Wed, 15 Oct 2008 04:57:39 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2008-10-15T04:57:39Z</dc:date>
    <item>
      <title>_XOPEN_SOURCE_EXTENDED question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284628#M672313</link>
      <description>Hi All&lt;BR /&gt;&lt;BR /&gt;Here are my settings:&lt;BR /&gt;&lt;BR /&gt;uname –a: HP-UX HP-C8000 B.11.11 U 9000/785 220365262 unlimited-user license&lt;BR /&gt;&lt;BR /&gt;gcc: gcc (GCC) 4.3.1&lt;BR /&gt;&lt;BR /&gt;Qt config: ./configure –platform hp-g++-64 &lt;BR /&gt;&lt;BR /&gt;Here is my problem:&lt;BR /&gt;&lt;BR /&gt;Attempting to configure produces the following error.&lt;BR /&gt;&lt;BR /&gt;/opt/hp-gcc64/bin/g++ -c -o makefiledeps.o  -D_HPUX_SOURCE -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igener&lt;BR /&gt;ators/mac -I/space2/sources/trolltech/download/qt-x11-commercial-src-4.4.2/include -I/space2/sources/trolltech/download/&lt;BR /&gt;qt-x11-commercial-src-4.4.2/include/QtCore -I/space2/sources/trolltech/download/qt-x11-commercial-src-4.4.2/include -I/s&lt;BR /&gt;pace2/sources/trolltech/download/qt-x11-commercial-src-4.4.2/include/QtCore -I/space2/sources/trolltech/download/qt-x11-&lt;BR /&gt;commercial-src-4.4.2/src/corelib/global -I/space2/sources/trolltech/download/qt-x11-commercial-src-4.4.2/src/script -DQT&lt;BR /&gt;_NO_PCRE -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_BUILD_QMAKE -DQT_NO_COMPRESS -I/spac&lt;BR /&gt;e2/sources/trolltech/download/qt-x11-commercial-src-4.4.2/mkspecs/hpux-g++-64 -DHAVE_QCONFIG_CPP -DQT_NO_THREAD -DQT_NO_&lt;BR /&gt;QOBJECT -DQT_NO_GEOM_VARIANT  generators/makefiledeps.cpp&lt;BR /&gt;In file included from /usr/include/net/if.h:234,               from /space2/sources/trolltech/download/qt-x11-commercial-src-4.4.2/mkspecs/hpux-g++-64/qplatformdefs.h&lt;BR /&gt;:56,&lt;BR /&gt;                 from generators/makefiledeps.cpp:28:&lt;BR /&gt;/usr/include/net/if6.h:77: error: field 'iflru_addr' has incomplete type&lt;BR /&gt;/usr/include/net/if6.h:78: error: field 'iflru_dstaddr' has incomplete type&lt;BR /&gt;/usr/include/net/if6.h:118: error: field 'lifra_addr' has incomplete type&lt;BR /&gt;/usr/include/net/if6.h:119: error: field 'lifra_mask' has incomplete type&lt;BR /&gt;gmake: *** [makefiledeps.o] Error 1&lt;BR /&gt;&lt;BR /&gt;Tracking this through on my system:&lt;BR /&gt;&lt;BR /&gt;'iflru_addr', 'iflru_dstaddr', 'lifra_addr' and 'lifra_mask' are all instances of the sockaddr_ext struct which is defined in socket.h&lt;BR /&gt;&lt;BR /&gt;#if !defined(_XOPEN_SOURCE_EXTENDED)&lt;BR /&gt;struct sockaddr_ext {&lt;BR /&gt;        unsigned short  sa_family;      /* address family */&lt;BR /&gt;        char            sa_data[22];    /* up to 22 bytes of direct address */&lt;BR /&gt;};&lt;BR /&gt;#endif /* !_XOPEN_SOURCE_EXTENDED */&lt;BR /&gt;&lt;BR /&gt;I understand that _XOPEN_SOURCE_EXTENDED should not be defined thus allowing sockaddr_ext to be created but putting in a #ifdef _XOPEN_SOURCE_EXTENDED #ERROR blah blah #endif before the #include &lt;SYS&gt; call suggests that it is. I can't find where on my system this define is.&lt;BR /&gt;&lt;BR /&gt;Searching this forum the following thread seems to describe the same problem...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1223633162475+28353475&amp;amp;threadId=1089588" target="_blank"&gt;http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1223633162475+28353475&amp;amp;threadId=1089588&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;In this instance sys/socket.h is being included and I wonder if anyone could give any clarification on whether and why the flags suggested would be applicable in this instance?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Ed&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;&lt;/SYS&gt;</description>
      <pubDate>Fri, 10 Oct 2008 09:22:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284628#M672313</guid>
      <dc:creator>E. Brown</dc:creator>
      <dc:date>2008-10-10T09:22:03Z</dc:date>
    </item>
    <item>
      <title>Re: _XOPEN_SOURCE_EXTENDED question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284629#M672314</link>
      <description>&amp;gt; [...] the following thread seems to&lt;BR /&gt;&amp;gt; describe the same problem...&lt;BR /&gt;&lt;BR /&gt;And this one may be vaguely similar:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1275847" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1275847&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;(You don't need the "11" or "12", or the&lt;BR /&gt;"admit=" stuff when you cite a Forum item.)&lt;BR /&gt;&lt;BR /&gt;"cc -E" might help you track down which&lt;BR /&gt;system header file gets the evil&lt;BR /&gt;_XOPEN_SOURCE_EXTENDED macro defined in your&lt;BR /&gt;case.  I didn't persist in my persuit of a&lt;BR /&gt;good solution, however, so I have no really&lt;BR /&gt;satisfying advice to offer.</description>
      <pubDate>Fri, 10 Oct 2008 13:54:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284629#M672314</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-10-10T13:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: _XOPEN_SOURCE_EXTENDED question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284630#M672315</link>
      <description>&amp;gt;Steven: "cc -E" might help you track down which system header file gets the evil _XOPEN_SOURCE_EXTENDED macro defined in your case.&lt;BR /&gt;&lt;BR /&gt;If you are debugging macros, you need to roll out the big guns:&lt;BR /&gt;aCC -E -.i -Wp,-C,-G&lt;BR /&gt;Also with Integrity add +legacy_cpp.</description>
      <pubDate>Sat, 11 Oct 2008 03:04:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284630#M672315</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-10-11T03:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: _XOPEN_SOURCE_EXTENDED question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284631#M672316</link>
      <description>Hi Steven, Dennis &lt;BR /&gt;Firstly thanks for the advice. I have some more information regarding this problem. Taking a step back I wrote a short program which includes the following pre-processor directives at the head of the file.&lt;BR /&gt;&lt;BR /&gt;#ifdef _XOPEN_SOURCE&lt;BR /&gt;#error ** _XOPEN_SOURCE is defined **&lt;BR /&gt;#else&lt;BR /&gt;#error **  _XOPEN_SOURCE is NOT defined **&lt;BR /&gt;#endif&lt;BR /&gt;&lt;BR /&gt;#ifdef _XOPEN_SOURCE_EXTENDED&lt;BR /&gt;#error ** the value is _XOPEN_SOURCE_EXTENDED is defined **&lt;BR /&gt;#else&lt;BR /&gt;#error ** the value is _XOPEN_SOURCE_EXTENDED is NOT defined **&lt;BR /&gt;#endif&lt;BR /&gt; &lt;BR /&gt;I then compiled the program using first GCC 4.3.1 and secondly the HP aCC: HP ANSI C++ B3910B A.03.33. _XOPEN_SOURCE is not defined in both instances but _XOPEN_SOURCE_EXTENDED is defined for the GCC compilation which leads to my undefined sockaddr_ext struct. In the GCC documentation under HPPA options the following is statedâ ¦&lt;BR /&gt;&lt;BR /&gt;`-munix=UNIX-STD'&lt;BR /&gt;     Generate compiler predefines and select a startfile for the&lt;BR /&gt;     specified UNIX standard.  The choices for UNIX-STD are `93', `95'&lt;BR /&gt;     and `98'.  `93' is supported on all HP-UX versions.  `95' is&lt;BR /&gt;     available on HP-UX 10.10 and later.  `98' is available on HP-UX&lt;BR /&gt;     11.11 and later.  The default values are `93' for HP-UX 10.00,&lt;BR /&gt;     `95' for HP-UX 10.10 though to 11.00, and `98' for HP-UX 11.11 and&lt;BR /&gt;     later.&lt;BR /&gt;&lt;BR /&gt;     `-munix=93' provides the same predefines as GCC 3.3 and 3.4.&lt;BR /&gt;     `-munix=95' provides additional predefines for `XOPEN_UNIX' and&lt;BR /&gt;     `_XOPEN_SOURCE_EXTENDED', and the startfile `unix95.o'.&lt;BR /&gt;     `-munix=98' provides additional predefines for `_XOPEN_UNIX',&lt;BR /&gt;     `_XOPEN_SOURCE_EXTENDED', `_INCLUDE__STDC_A1_SOURCE' and&lt;BR /&gt;     `_INCLUDE_XOPEN_SOURCE_500', and the startfile `unix98.o'.&lt;BR /&gt;&lt;BR /&gt;     It is _important_ to note that this option changes the interfaces&lt;BR /&gt;     for various library routines.  It also affects the operational&lt;BR /&gt;     behavior of the C library.  Thus, _extreme_ care is needed in&lt;BR /&gt;     using this option.&lt;BR /&gt;&lt;BR /&gt;When I compile my test program with the '-muinx=93' switch both _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED are both undefined.&lt;BR /&gt;&lt;BR /&gt;Can you tell me how I can incorporate this command line option in GCC prior to running the Qt configure script? I have tried setting the CXXFLAGS and CPPFLAGS environment variables without success.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Ed&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Oct 2008 12:27:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284631#M672316</guid>
      <dc:creator>E. Brown</dc:creator>
      <dc:date>2008-10-14T12:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: _XOPEN_SOURCE_EXTENDED question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284632#M672317</link>
      <description>&amp;gt;Can you tell me how I can incorporate this command line option in GCC prior to running the Qt configure script?&lt;BR /&gt;&lt;BR /&gt;I would have thought CXXFLAGS would do it.  Can you look in the Qt configure script?&lt;BR /&gt;&lt;BR /&gt;You could wrap this option with the compiler and then pass in something like:&lt;BR /&gt;./configure -platform hp-g++-64 cc="/opt/hp-gcc64/bin/g++ -muinx=93"&lt;BR /&gt;&lt;BR /&gt;But you would want to use the one for C++.</description>
      <pubDate>Wed, 15 Oct 2008 04:57:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/xopen-source-extended-question/m-p/4284632#M672317</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-10-15T04:57:39Z</dc:date>
    </item>
  </channel>
</rss>

