<?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: Run time can't find libstdc++.so in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062740#M94640</link>
    <description>&lt;P&gt;&amp;gt;That's what threw me when the dependencies started calling out libstdc++.&lt;BR /&gt;&lt;BR /&gt;You'll have to rebuild them.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Here's my current link cmd line:&lt;BR /&gt;aCC +DD64 -b -o libfcl.so -L/opt/aCC/lib&lt;BR /&gt;&lt;BR /&gt;There are no IPF libs here remove it.&lt;BR /&gt;&lt;BR /&gt;-lCsup -lstd -lstream -lc -ldld -lcl&lt;BR /&gt;&lt;BR /&gt;This is completely broken. You have the -AP libs and they are in the wrong order. The correct link order is:&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/10946/distributing.htm#linking" target="_blank"&gt;http://docs.hp.com/en/10946/distributing.htm#linking&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Or -lstd_v2 -lCsup -lunwind -lm&lt;BR /&gt;You can leave off -lm if not needed.&lt;BR /&gt;&lt;BR /&gt;NEVER EVER link with -lc.&lt;BR /&gt;And on IPF, -lcl should be -lunwind.&lt;/P&gt;</description>
    <pubDate>Sun, 25 Sep 2011 01:08:26 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2011-09-25T01:08:26Z</dc:date>
    <item>
      <title>Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062728#M94628</link>
      <description>Our application runs HP-UX on Itanium.  One of the libs I work on links with libstdc++.so and during run time we get the error: Unable to find library libstdc++.so.  Is this something we have to distribute with our application?&lt;BR /&gt;The build and test systems are both running: HP-UX B.11.23 U &lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;JJD</description>
      <pubDate>Wed, 29 Aug 2007 20:02:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062728#M94628</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-08-29T20:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062729#M94629</link>
      <description>Hello JJD,&lt;BR /&gt;&lt;BR /&gt;Assume Application libstdc++.so.* location is:&lt;BR /&gt;/opt/&lt;APP&gt;/lib/libstdc++.so.3&lt;BR /&gt;&lt;BR /&gt;Issue command:&lt;BR /&gt;# cd /usr/lib/hpux32&lt;BR /&gt;# ln -s /opt/&lt;APP&gt;/lib/libstdc++.so.3 libstdc++.so&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/APP&gt;&lt;/APP&gt;</description>
      <pubDate>Wed, 29 Aug 2007 23:27:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062729#M94629</guid>
      <dc:creator>TY 007</dc:creator>
      <dc:date>2007-08-29T23:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062730#M94630</link>
      <description>&amp;gt;Is this something we have to distribute with our application?&lt;BR /&gt;&lt;BR /&gt;Exactly.  This foreign devil lib doesn't come with the system.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;TY 007: # ln -s /opt/&lt;APP&gt;/lib/libstdc++.so.3 libstdc++.so&lt;BR /&gt;&lt;BR /&gt;While you could do this, it is probably better to include the path to /opt/&lt;APP&gt;/lib in the executable.  That way there is less things to change on the end user's system.&lt;/APP&gt;&lt;/APP&gt;</description>
      <pubDate>Thu, 30 Aug 2007 01:06:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062730#M94630</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-08-30T01:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062731#M94631</link>
      <description>Thanks for the replies, we will be including this module in with our application libraries.  &lt;BR /&gt;&lt;BR /&gt;Another question, if I may.&lt;BR /&gt;Is there a way to flush out these run time link issues during build time?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;JJD</description>
      <pubDate>Tue, 04 Sep 2007 07:08:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062731#M94631</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-09-04T07:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062732#M94632</link>
      <description>This is a follow-up on my previous posting.&lt;BR /&gt;&lt;BR /&gt;I am also getting some Unsatisfied data symbol errors during run time.  Is there a way to flush these out during link time?&lt;BR /&gt;&lt;BR /&gt;Thanks again,&lt;BR /&gt;JJD</description>
      <pubDate>Tue, 04 Sep 2007 08:06:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062732#M94632</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-09-04T08:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062733#M94633</link>
      <description>&amp;gt;Is there a way to flush out these run time link issues during build time?&lt;BR /&gt;&lt;BR /&gt;If you link with the -Wl,+b,path option to give the runtime path and you install there, you can at least make sure it runs.  I'm not sure this is build time as you wanted?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;I am also getting some Unsatisfied data symbol errors during run time. Is there a way to flush these out during link time?&lt;BR /&gt;&lt;BR /&gt;If you link with -Wl,-Bimmediate, you'll get these runtime unsats.  Of course you'll need to install and run the application.  And you then need to use "chatr -B deferred" to put put it back.&lt;BR /&gt;&lt;BR /&gt;The linker does have the -Wl,+vshlibunsats option to print out shlib unsats.</description>
      <pubDate>Tue, 04 Sep 2007 11:11:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062733#M94633</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-09-04T11:11:43Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062734#M94634</link>
      <description>Thanks again Dennis, this worked great.  Now on to the next step, is there any documentation on what symbols are in what libs?  Here's a sample of what I'm seeing:&lt;BR /&gt;&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "std::__rw_std_streams" in file CC_PropertySet.o&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_SetIP" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_SetGR" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_GetIP" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_GetGR" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "std::basic_ostream&lt;CHAR&gt; &amp;gt;::_C_opfx()" in file CC_PropertySet.o&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "__udivdi3" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "__divdi3" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_RaiseException" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_GetRegionStart" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "std::ios_base::_C_sync_with_stdio" in file CC_PropertySet.o&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "std::ios_base::_C_unsafe_clear(int,int)" in file CC_PropertySet.o&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "std::basic_istream&lt;CHAR&gt; &amp;gt;::_C_unsafe_get(long*,int,int)" in file /builds/Prebuilt/HPia64/icu/3.2/lib/libicuio.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_end" in file /usr/lib/hpux32/libc.so.1&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "std::basic_istream&lt;CHAR&gt; &amp;gt;::_C_ipfx(int)" in file /builds/Prebuilt/HPia64/icu/3.2/lib/libicuio.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_Resume" in file CC_Accessor.o&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "main" in file /usr/lib/hpux32/libc.so.1&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_GetLanguageSpecificData" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_DeleteException" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;19 warnings.&lt;BR /&gt;Completion of ./cc_common_build.sh build script&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/CHAR&gt;&lt;/CHAR&gt;&lt;/CHAR&gt;</description>
      <pubDate>Tue, 04 Sep 2007 13:36:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062734#M94634</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-09-04T13:36:31Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062735#M94635</link>
      <description>At run time it is not as bad (probably the library path is a bit more complete) but I still get the following and can't trace down the home library for them.&lt;BR /&gt;&lt;BR /&gt;        symbol not found: _ZSt16__rw_std_streams        (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZNSt8ios_base18_C_sync_with_stdioE   (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZTVSt14__rw_exception        (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZNSs9__nullrefE      (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZTVN4__rw17__rw_thread_errorE        (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZTIN4__rw17__rw_thread_errorE        (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZNSt6locale9_C_globalE       (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;        symbol not found: _ZSt16__rw_std_streams        (/u1/IBM/InformationServer/Server/DSComponents/lib/libicuio.so.32)&lt;BR /&gt;        symbol not found: _ZNSt8ios_base18_C_sync_with_stdioE   (/u1/IBM/InformationServer/Server/DSComponents/lib/libicuio.so.32)&lt;BR /&gt;bash-2.03$&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Sep 2007 15:58:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062735#M94635</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-09-04T15:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062736#M94636</link>
      <description>&lt;P&gt;You are appropriately hosed. You are mixing g++ and aC++.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;is there any documentation on what symbols are in what libs?&lt;BR /&gt;&lt;BR /&gt;Why look up documentation when you can scan the libs:&lt;BR /&gt;$ nm -pxAN /usr/lib/hpux64/lib* /usr/local/lib/hpux64/lib* | grep -e foo1 -e foo2&lt;BR /&gt;(Or use grep -f and put the symbols in a file.)&lt;BR /&gt;&lt;BR /&gt;Were you creating an executable or shlib (with -b)?&lt;BR /&gt;&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_Unwind_SetIP" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;&lt;BR /&gt;This is why I don't use -Wl,+vshlibunsats. This is defined in libunwind. And it shouldn't have been listed. (I assume g++ is smart enough to include -lunwind.)&lt;BR /&gt;&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "__udivdi3" in file /usr/local/lib/hpux64/libstdc++.so&lt;BR /&gt;&lt;BR /&gt;This lib is broken. It was linked incorrectly and should have its own copy of these functions.&lt;BR /&gt;&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "_end" in file libc.so.1&lt;BR /&gt;ld: (Warning) Unsatisfied symbol "main"&lt;BR /&gt;&lt;BR /&gt;These are found in your executable.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;At run time it is not as bad (probably the library path is a bit more complete)&lt;BR /&gt;&lt;BR /&gt;No, because +vshlibunsats gives too much info. There is a better tool for PA32, show_remaining_imports:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1115429" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1115429&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1151071" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1151071&lt;/A&gt;&lt;BR /&gt;But you need show_remaining_imports_elf which I haven't attached yet.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;but I still get the following and can't trace down the home library for them.&lt;BR /&gt;symbol not found: _ZSt16__rw_std_streams (/u1/IBM/InformationServer/ASBNode/lib/cpp/libfcl.so)&lt;BR /&gt;&lt;BR /&gt;It should be obvious. ;-) They come from aC++, not your foreign devil g++. The nm(1) fragment above would have told you that.&lt;BR /&gt;&lt;BR /&gt;You must not use libfcl.so and libicuio.so.32 in your g++ application, or you must port everything to aC++. I doubt IBM would port those libs to g++ or C for you.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Sep 2011 01:07:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062736#M94636</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2011-09-25T01:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062737#M94637</link>
      <description>Thanks Dennis,&lt;BR /&gt;The libfcl.so is the component I'm porting to HP Itanium.  This shared lib is ported across a number of OS platforms but this is the first time for this module on HPUX Itanium. &lt;BR /&gt;&lt;BR /&gt;I'm not surprised some g++ got in there, some of the libs we use are from open source projects.&lt;BR /&gt;&lt;BR /&gt;I'll give some of your suggestions a try.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;JJD&lt;BR /&gt;dorak@us.ibm.com</description>
      <pubDate>Tue, 04 Sep 2007 17:34:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062737#M94637</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-09-04T17:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062738#M94638</link>
      <description>&amp;gt;I'm not surprised some g++ got in there, some of the libs we use are from open source projects.&lt;BR /&gt;&lt;BR /&gt;It seems like you are saying this backward.  The title of your thread says "I'm using g++, not aC++".  Unless you mistakenly added -lstdc++?</description>
      <pubDate>Tue, 04 Sep 2007 22:22:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062738#M94638</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-09-04T22:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062739#M94639</link>
      <description>I think I may have mislead you.  I am building using aCC.  That's what threw me when the dependencies started calling out libstdc++.  &lt;BR /&gt;&lt;BR /&gt;Here's my current link cmd line:&lt;BR /&gt;&lt;BR /&gt;aCC +DD64 -b   -o libfcl.so\&lt;BR /&gt;       CC_Accessor.o . . . CC_Threads.o fcl.o -L/builds/Prebuilt/HPia64/icu/3.2/lib -L/builds/Prebuilt/HPia64/xml4c5_6_3-hpia64/lib -L/opt/aCC/lib -lxml4c -licuuc -licui18n -licutu -licuio -lCsup -lstd -lstream -lc -ldld -lcl&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;JJD</description>
      <pubDate>Wed, 05 Sep 2007 11:07:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062739#M94639</guid>
      <dc:creator>John Dorak</dc:creator>
      <dc:date>2007-09-05T11:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Run time can't find libstdc++.so</title>
      <link>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062740#M94640</link>
      <description>&lt;P&gt;&amp;gt;That's what threw me when the dependencies started calling out libstdc++.&lt;BR /&gt;&lt;BR /&gt;You'll have to rebuild them.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Here's my current link cmd line:&lt;BR /&gt;aCC +DD64 -b -o libfcl.so -L/opt/aCC/lib&lt;BR /&gt;&lt;BR /&gt;There are no IPF libs here remove it.&lt;BR /&gt;&lt;BR /&gt;-lCsup -lstd -lstream -lc -ldld -lcl&lt;BR /&gt;&lt;BR /&gt;This is completely broken. You have the -AP libs and they are in the wrong order. The correct link order is:&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/10946/distributing.htm#linking" target="_blank"&gt;http://docs.hp.com/en/10946/distributing.htm#linking&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Or -lstd_v2 -lCsup -lunwind -lm&lt;BR /&gt;You can leave off -lm if not needed.&lt;BR /&gt;&lt;BR /&gt;NEVER EVER link with -lc.&lt;BR /&gt;And on IPF, -lcl should be -lunwind.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Sep 2011 01:08:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/run-time-can-t-find-libstdc-so/m-p/4062740#M94640</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2011-09-25T01:08:26Z</dc:date>
    </item>
  </channel>
</rss>

