<?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: compiling bash 4.0.033 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538753#M678656</link>
    <description>Our servers are managed by another company (CSC), and I have to make a formal request that has to approved... too complicated.&lt;BR /&gt;&lt;BR /&gt;I was able to build 64 bit versions of the build time dependencies for bash (gettext, libiconv, make and libtermcap). Does the reply from Dennis (Handly) mean that building a 64 bit version is hopeless, or could the sources be tweaked?&lt;BR /&gt;&lt;BR /&gt;Thank you all for the replies.</description>
    <pubDate>Tue, 24 Nov 2009 20:47:29 GMT</pubDate>
    <dc:creator>Denis Laroche</dc:creator>
    <dc:date>2009-11-24T20:47:29Z</dc:date>
    <item>
      <title>compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538748#M678651</link>
      <description>$ uname -a&lt;BR /&gt;HP-UX wcalqa1w B.11.11 U 9000/800 &lt;BR /&gt;&lt;BR /&gt;I'm trying to build a 64 bit version of bash 4.0.033 on this machine from the source distribution found of the HP porting center (&lt;A href="http://hpux.connect.org.uk)." target="_blank"&gt;http://hpux.connect.org.uk).&lt;/A&gt; It works until ld is run to create the bash executable and then I get the following errors.&lt;BR /&gt;&lt;BR /&gt;ld: Unsatisfied symbol "__strtoull" in file ./builtins/libbuiltins.a[printf.o]&lt;BR /&gt;ld: Unsatisfied symbol "__strtoll" in file general.o&lt;BR /&gt;&lt;BR /&gt;The bash distribution has two files, strtoll.c and strtoull.c, that define strtoll() and strtoull() properly after the configure script is run. The objects of those two C files have strtoll and strtoull, which I can see with nm.&lt;BR /&gt;&lt;BR /&gt;Could somebody explain to me where are references to __strtoll and __strtoull coming from, even if nothing in the bash source files is referencing those two symbols?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for any help.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Nov 2009 03:23:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538748#M678651</guid>
      <dc:creator>Denis Laroche</dc:creator>
      <dc:date>2009-11-24T03:23:37Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538749#M678652</link>
      <description>&amp;gt;Could somebody explain to me where are references to __strtoll and __strtoull coming from&lt;BR /&gt;&lt;BR /&gt;There are some macros in &lt;INTTYPES.H&gt; that turn strtoimax and strtoumax to those unsats.&lt;BR /&gt;Unfortunately this fails in 64 bit mode because you should just use strtol or strtoul there.&lt;/INTTYPES.H&gt;</description>
      <pubDate>Tue, 24 Nov 2009 05:57:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538749#M678652</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-11-24T05:57:47Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538750#M678653</link>
      <description>Why not using the depot from &lt;A href="http://hpux.connect.org.uk/hppd/hpux/Shells/bash-4.0.033/" target="_blank"&gt;http://hpux.connect.org.uk/hppd/hpux/Shells/bash-4.0.033/&lt;/A&gt; ?</description>
      <pubDate>Tue, 24 Nov 2009 06:42:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538750#M678653</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-24T06:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538751#M678654</link>
      <description>I don't have root access to this server. There is a non privileged moded described in the documentation of SD-UX, but that didn't work for me.&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply.&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Nov 2009 12:12:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538751#M678654</guid>
      <dc:creator>Denis Laroche</dc:creator>
      <dc:date>2009-11-24T12:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538752#M678655</link>
      <description>Hi Denis:&lt;BR /&gt;&lt;BR /&gt;I presume that you fetched the build-time dependencies, too since to create a fully executable package those will have to be compiled too.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I don't have root access to this server. There is a non privileged moded described in the documentation of SD-UX, but that didn't work for me.&lt;BR /&gt;&lt;BR /&gt;May I suggest (along the lines of Torsten's thinking) that you ask your Server Administrator to install a pre-built binary for you from the Porting Centre.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Nov 2009 13:01:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538752#M678655</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-11-24T13:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538753#M678656</link>
      <description>Our servers are managed by another company (CSC), and I have to make a formal request that has to approved... too complicated.&lt;BR /&gt;&lt;BR /&gt;I was able to build 64 bit versions of the build time dependencies for bash (gettext, libiconv, make and libtermcap). Does the reply from Dennis (Handly) mean that building a 64 bit version is hopeless, or could the sources be tweaked?&lt;BR /&gt;&lt;BR /&gt;Thank you all for the replies.</description>
      <pubDate>Tue, 24 Nov 2009 20:47:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538753#M678656</guid>
      <dc:creator>Denis Laroche</dc:creator>
      <dc:date>2009-11-24T20:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538754#M678657</link>
      <description>&amp;gt;Does the reply from Dennis (Handly) mean that building a 64 bit version is hopeless, or could the sources be tweaked?&lt;BR /&gt;&lt;BR /&gt;It should be trivial:&lt;BR /&gt;1) #undef those macros.  Find why you are using strtoimax?&lt;BR /&gt;2) Define __strtoll and __strtoull and have them either call your function, or call the ones for long: strtol and strtoul.</description>
      <pubDate>Wed, 25 Nov 2009 00:31:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538754#M678657</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-11-25T00:31:14Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538755#M678658</link>
      <description>Ok thanks, I'll give it a try as soon as I have a chance.</description>
      <pubDate>Wed, 25 Nov 2009 02:02:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538755#M678658</guid>
      <dc:creator>Denis Laroche</dc:creator>
      <dc:date>2009-11-25T02:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538756#M678659</link>
      <description>It worked!&lt;BR /&gt;&lt;BR /&gt;$ which bash&lt;BR /&gt;/home/limpet/ex36672/tools/hppa64/bin/bash&lt;BR /&gt;$ file /home/limpet/ex36672/tools/hppa64/bin/bash&lt;BR /&gt;/home/limpet/ex36672/tools/hppa64/bin/bash:     ELF-64 executable object file - PA-RISC 2.0 (LP64)&lt;BR /&gt;&lt;BR /&gt;Most of the tests in the bash test suite succeded.&lt;BR /&gt;&lt;BR /&gt;Thanks again to all for your replies.&lt;BR /&gt;</description>
      <pubDate>Sun, 29 Nov 2009 15:51:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538756#M678659</guid>
      <dc:creator>Denis Laroche</dc:creator>
      <dc:date>2009-11-29T15:51:36Z</dc:date>
    </item>
    <item>
      <title>Re: compiling bash 4.0.033</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538757#M678660</link>
      <description>&amp;gt;It worked!&lt;BR /&gt;&lt;BR /&gt;If you are happy with the answers you were given, please read the following about how to assign points:&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;</description>
      <pubDate>Mon, 30 Nov 2009 08:34:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/compiling-bash-4-0-033/m-p/4538757#M678660</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-11-30T08:34:55Z</dc:date>
    </item>
  </channel>
</rss>

