<?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: kernel rebuild using mk_kernel with ANSI C in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025670#M131489</link>
    <description>Hi,&lt;BR /&gt;are you sure you didn't change any parameter in the kernel ?&lt;BR /&gt;&lt;BR /&gt;Usually the kernel rebuild uses the internal C compiler, AFAIK, and the installation should have not changed anything.&lt;BR /&gt;&lt;BR /&gt;Try comparing /stand/system and /stand/system.prev, is there any difference (assuming just one kernel rebuild)?&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt; Massimo&lt;BR /&gt;</description>
    <pubDate>Thu, 17 Jul 2003 08:42:37 GMT</pubDate>
    <dc:creator>Massimo Bianchi</dc:creator>
    <dc:date>2003-07-17T08:42:37Z</dc:date>
    <item>
      <title>kernel rebuild using mk_kernel with ANSI C</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025669#M131488</link>
      <description>When I build a new kernel on an rp7410 with HP-UX 11i the size is approx. 26MB. After installation of ANSI C the rebuilt kernel is only 18MB. Will the new kernel work as efficiently as the larger one and why is there such a size difference.&lt;BR /&gt;Surely it would be better if kernel rebuilds always used the HP C compiler for consistency.</description>
      <pubDate>Wed, 16 Jul 2003 16:49:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025669#M131488</guid>
      <dc:creator>Pete Des Moulins</dc:creator>
      <dc:date>2003-07-16T16:49:36Z</dc:date>
    </item>
    <item>
      <title>Re: kernel rebuild using mk_kernel with ANSI C</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025670#M131489</link>
      <description>Hi,&lt;BR /&gt;are you sure you didn't change any parameter in the kernel ?&lt;BR /&gt;&lt;BR /&gt;Usually the kernel rebuild uses the internal C compiler, AFAIK, and the installation should have not changed anything.&lt;BR /&gt;&lt;BR /&gt;Try comparing /stand/system and /stand/system.prev, is there any difference (assuming just one kernel rebuild)?&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt; Massimo&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jul 2003 08:42:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025670#M131489</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-07-17T08:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: kernel rebuild using mk_kernel with ANSI C</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025671#M131490</link>
      <description>Installing ANSI-C on 11i doesnt require a reboot. The software does not have the is_reboot flag set, so why did you have a new kernel rebuilt ? &lt;BR /&gt;&lt;BR /&gt;something else you installed required the reboot and its changed the kernel. Depending on what changed the size of the kernel can change dramatically, as in your case. You need to find out why/what rebuilt your kernel.&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jul 2003 08:49:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025671#M131490</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-07-17T08:49:01Z</dc:date>
    </item>
    <item>
      <title>Re: kernel rebuild using mk_kernel with ANSI C</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025672#M131491</link>
      <description>Hi Pete&lt;BR /&gt;&lt;BR /&gt;are you looking at /stand/vmunix or /stand/build/vmunix_test,&lt;BR /&gt;&lt;BR /&gt;while building new kernel(mk_kernel)/stand/build/vmunix_test will be generated which will replace(move to) /stand/vmunix.&lt;BR /&gt;as long as kernel is building up without any problem and system is coming up with new kernel size of the file doesn't matter.</description>
      <pubDate>Thu, 17 Jul 2003 08:55:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025672#M131491</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2003-07-17T08:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: kernel rebuild using mk_kernel with ANSI C</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025673#M131492</link>
      <description>Without ANSI C installed using mk_kernel produces a /stand/build/vmunix_test of 26MB. After installing ANSI C and without any other changes, using mk_kernel produces a /stand/build/vmunix_test of 18MB. Using the "what" command on both versions of vmunix_test produces identical results. My real concern is that the smaller version of vmunix will be slower than the previous version. Has anyone any experience of this?</description>
      <pubDate>Thu, 17 Jul 2003 10:36:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025673#M131492</guid>
      <dc:creator>Pete Des Moulins</dc:creator>
      <dc:date>2003-07-17T10:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: kernel rebuild using mk_kernel with ANSI C</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025674#M131493</link>
      <description>Yes, we have experienced this also on some of our servers. For example, 2 identically built 11i servers (only difference is one has HP ANSI C installed) and vmunix is 17MB on the server with ANSI, and 26MB on the server without. We were worried by this also, but after checking it seems to be absolutely fine. Weve never had any problems on any our servers liek this.&lt;BR /&gt;All I can think is that ANSI-C implements newer libraries optimized for PA-RISC which thus reduces the kernel build size, and this is a positive bonus!&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Jul 2003 11:23:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-rebuild-using-mk-kernel-with-ansi-c/m-p/3025674#M131493</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-07-17T11:23:27Z</dc:date>
    </item>
  </channel>
</rss>

