command-not-found depends GCC_4.2.0

Bug #195491 reported by Stephen Balousek
2
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: command-not-found

$ gcc-.3 -v

KABOOOM!!!

Whoops, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/ubuntu/+source/command-not-found
Please include the following information with the report:
/usr/local/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
Traceback (most recent call last):
  File "/usr/lib/command-not-found", line 10, in <module>
    from CommandNotFound import CommandNotFound
  File "/usr/lib/python2.5/site-packages/CommandNotFound/__init__.py", line 1, in <module>
    from CommandNotFound import CommandNotFound
  File "/usr/lib/python2.5/site-packages/CommandNotFound/CommandNotFound.py", line 7, in <module>
    import apt_pkg
ImportError: /usr/local/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)
Python version: 2.5.1 final 0
-bash: gcc-.3: command not found

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

Revision history for this message
Stephen Balousek (s-balousek) wrote :

This was caused by an installation of GCC-3.3 into /usr/local when GCC-4.2 was installed in /usr.

Changed in command-not-found:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.