<?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: Distinguishing the bundled and optional C compilers in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097961#M90753</link>
    <description>.</description>
    <pubDate>Sat, 15 Mar 2008 02:53:51 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2008-03-15T02:53:51Z</dc:date>
    <item>
      <title>Distinguishing the bundled and optional C compilers</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097958#M90750</link>
      <description>&lt;!--!*#--&gt;I'm working on the C compiler identification&lt;BR /&gt;section of a "configure" script.&lt;BR /&gt;&lt;BR /&gt;On all systems, I can use the __hpux macro to&lt;BR /&gt;identify HP-UX.&lt;BR /&gt;&lt;BR /&gt;On old PA-RISC systems, I can use __HP_cc to&lt;BR /&gt;distinguish between the bundled and optional C&lt;BR /&gt;compilers.&lt;BR /&gt;&lt;BR /&gt;On IA64 systems, __HP_cc is defined even with&lt;BR /&gt;the bundled C compiler.&lt;BR /&gt;&lt;BR /&gt;Is there a reliable macro I can use for this on&lt;BR /&gt;IA64, or do I need to start scanning stderr for&lt;BR /&gt;"(Bundled)" when I try to use some exotic&lt;BR /&gt;feature (in the code or on the command line)?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;For example:&lt;BR /&gt;&lt;BR /&gt;dy # uname -a&lt;BR /&gt;HP-UX dy B.11.11 U 9000/785 2012616114 unlimited-user license&lt;BR /&gt;&lt;BR /&gt;dy # cat cct.c&lt;BR /&gt;#include &lt;STDIO.H&gt;&lt;BR /&gt;&lt;BR /&gt;main()&lt;BR /&gt;{&lt;BR /&gt;#ifdef __hpux&lt;BR /&gt;    printf( " __hpux\n");&lt;BR /&gt;#endif /* def __hpux */&lt;BR /&gt;&lt;BR /&gt;#ifdef __HP_cc&lt;BR /&gt;    printf( " __HP_cc\n");&lt;BR /&gt;#endif /* def __HP_cc */&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;dy # cc -o cct cct.c&lt;BR /&gt;&lt;BR /&gt;dy # ./cct&lt;BR /&gt; __hpux&lt;BR /&gt;dy # &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;dyi # uname -a&lt;BR /&gt;HP-UX dyi B.11.31 U ia64 4235313755 unlimited-user license&lt;BR /&gt;&lt;BR /&gt;dyi # cc -o cct cct.c&lt;BR /&gt;&lt;BR /&gt;dyi # ./cct&lt;BR /&gt; __hpux&lt;BR /&gt; __HP_cc&lt;BR /&gt;dyi #&lt;/STDIO.H&gt;</description>
      <pubDate>Fri, 14 Mar 2008 20:11:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097958#M90750</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-14T20:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Distinguishing the bundled and optional C compilers</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097959#M90751</link>
      <description>It's very simple, the bundled C compiler is in /usr/ccs/bin/cc_bundled.&lt;BR /&gt;The fully functional compiler is in /opt/aCC/bin/cc on IPF and /opt/ansic/bin/cc on PA.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Is there a reliable macro I can use for this on IA64, or do I need to start scanning stderr for "(Bundled)" when I try to use some exotic feature &lt;BR /&gt;&lt;BR /&gt;Since you aren't suppose to be using the bundled C compiler, there is no easy way to tell the difference.  So other than maintaining a list of values for __HP_cc, you'll have to look for "(Bundled)".&lt;BR /&gt;&lt;BR /&gt;&amp;gt;On old PA-RISC systems, I can use __HP_cc&lt;BR /&gt;&lt;BR /&gt;This probably won't work on 11.31.</description>
      <pubDate>Fri, 14 Mar 2008 22:38:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097959#M90751</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-03-14T22:38:56Z</dc:date>
    </item>
    <item>
      <title>Re: Distinguishing the bundled and optional C compilers</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097960#M90752</link>
      <description>&amp;gt; [...] you aren't suppose[d] to be using the&lt;BR /&gt;&amp;gt; bundled C compiler [...]&lt;BR /&gt;&lt;BR /&gt;Who supposes that?  Someone who knows me not&lt;BR /&gt;well?&lt;BR /&gt;&lt;BR /&gt;&amp;gt; &amp;gt;On old PA-RISC systems, I can use __HP_cc&lt;BR /&gt;&lt;BR /&gt;&amp;gt; This probably won't work on 11.31.&lt;BR /&gt;&lt;BR /&gt;Sure enough.  Well, fine.  I'll just look for&lt;BR /&gt;"(Bundled)" then.  Thanks.</description>
      <pubDate>Sat, 15 Mar 2008 02:52:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097960#M90752</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-15T02:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: Distinguishing the bundled and optional C compilers</title>
      <link>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097961#M90753</link>
      <description>.</description>
      <pubDate>Sat, 15 Mar 2008 02:53:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/distinguishing-the-bundled-and-optional-c-compilers/m-p/5097961#M90753</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-03-15T02:53:51Z</dc:date>
    </item>
  </channel>
</rss>

