Where is libstdc .so

You need to run 'apt-file update' first. I have done that, when I do it says: File is up-to-date. Ignoring source without Contents File: a link they won't let me post Or File is up-to-date. Downloading Index a link No Index available. Downloading complete file a link I am still getting the same error when I try to run Psychonauts. Improve this question. Community Bot 1. UsagiYojimbo UsagiYojimbo 2 2 gold badges 5 5 silver badges 13 13 bronze badges. Add a comment. Active Oldest Votes.

To install it, type: sudo apt-get install apt-file Then you have to update the index. Improve this answer. Read above answer exactly. Not sure what I did differently, but it apt-file find worked this time. I get the list of packages. All operations on the re-opened fs would fail, or at least act very strangely, especially if fs reached the EOF state on the previous file.

You had to insert a call to fs. Update: For GCC 4. Mainly, that option tries to enforce object-oriented programming, while the Standard Library isn't necessarily trying to be OO. If they become visible in the same namespace as other comparison functions e.

This was discussed on the mailing list; Nathan Myers sums things up here. Do not report problems with -v2 to the -v3 mailing list. For GCC versions 3. Starting with version 3. If you see compilation errors containing messages about foo Concept and something to do with a constraints member function, then most likely you have violated one of the requirements for types used during instantiation of template containers and functions.

Since GCC 5. With some versions of valgrind this pool will be shown as "still reachable" when the process exits, e.

Later versions of valgrind know how to free this pool as the process exits, and so won't show any "still reachable" memory. In the past, a few people reported that the standard containers appear to leak memory when tested with memory checkers such as valgrind.

Under some non-default configurations the library's allocators keep free memory in a pool for later reuse, rather than deallocating it with delete Although this memory is always reachable by the library and is never lost, memory debugging tools can report it as a leak.

If you want to test the library for memory leaks please read Tips for memory leak hunting first. See the Containers chapter. If you have found a bug in the library and you think you have a working fix, then send it in! In addition to the description, the patch, and the ChangeLog entry, it is a Good Thing if you can additionally create a small test program to test for the presence of the bug that your patch fixes. Bugs have a way of being reintroduced; if an old bug creeps back in, it will be caught immediately by the testsuite - but only if such a test exists.

While there are arguments for iterators to be implemented in that manner, A they aren't very good ones in the long term, and B they were never guaranteed by the Standard anyway. In particular, string is not from SGI and makes no use of their "rope" class although that is included as an optional extension , neither is valarray nor some others.

See the link on backwards compatibility and link on evolution. Please refer to the Contributing section in our manual. A single CPU design may suffer multiple ABIs designed by different development tool vendors who made different choices, or even by the same vendor for different target applications or compiler versions. In practice every ABI omits details that compiler implementers consciously or accidentally must choose for themselves.

That ABI definition suffices for compilers to generate code so a program can interact safely with an OS and its lowest-level libraries. Users usually want an ABI to encompass more detail, allowing libraries built with different compilers or different releases of the same compiler! Those ABIs cover low-level details such as virtual function implementation, struct inheritance layout, name mangling, and exception handling. It makes defining a complete ABI a much bigger undertaking, and requires not just documenting library implementation details, but carefully designing those details so that future bug fixes and optimizations don't force breaking the ABI.

There are ways to help isolate library implementation details from the ABI, but they trade off against speed. Active 4 months ago. Viewed 89 times. Here is the current sources. Done Building dependency tree Reading state information Done Building data structures Done This package is not able to be installed Dependency is not satisfiable: gcc Improve this question.

Red-Roo Red-Roo 3 4 4 bronze badges. So for now I just wish to maintain it as best as I can. Add a comment. Newbie 15 points. Log in to join the conversation. Pro points. Daryl Herzmann.

ZS Newbie 15 points. Zing Zing Shishak. I was unaware of other repositories GM Community Member 37 points. Govindarajan M S. Guru points. This should include the caveat that the host must have Internet access and be connected to RHN.

AS Newbie 5 points. Alex Santos. Thank you! WM Community Member 41 points.