如何在Kali Linux 2017.1 64位系统安装lib32stdc++6？

Hey there, let's work through this frustrating lib32stdc++6 installation issue you're hitting on Kali 2017.1 64-bit—critical for getting Flutter to play nice. Here are some targeted steps to try, since the standard --fix-missing flag isn't cutting it:

1. First, Enable the 32-bit (i386) Architecture #

Kali's 64-bit build doesn't always have the i386 architecture enabled by default, which is required to pull 32-bit packages like lib32stdc++6. Run these commands:

dpkg --add-architecture i386
apt-get update

This tells your system to look for 32-bit packages in the repositories.

2. Clean Up Package Caches and Retry Installation #

Corrupted or outdated cache files might be blocking the install. Clear them out first, then refresh and try again:

apt-get clean
apt-get autoclean
apt-get update --fix-missing
apt-get install lib32stdc++6

This ensures you're pulling the latest available package info and aren't stuck with broken cached files.

3. Switch to Kali's Archive Repositories (Critical for Old Versions) #

Kali Linux 2017.1 is pretty outdated—official rolling repositories no longer host packages for this release. You'll need to point your system to the archived sources:

1. Open your sources list file:

   nano /etc/apt/sources.list
   

2. Replace all existing lines with these archive sources (for Kali "Sana", which corresponds to 2017.1):

   deb http://old.kali.org/kali sana main non-free contrib
   deb-src http://old.kali.org/kali sana main non-free contrib
   

3. Save and exit (Ctrl+O, then Ctrl+X in nano), then update and install:

   apt-get update
   apt-get install lib32stdc++6
   

4. Manual Deb Package Installation (Last Resort) #

If apt still can't locate the package, download it directly from the archive and install manually:

# Download the correct deb for Kali 2017.1
wget http://old.kali.org/kali/pool/main/g/gcc-6/lib32stdc++6_6.3.0-18kali1_i386.deb
# Install the package
dpkg -i lib32stdc++6_6.3.0-18kali1_i386.deb
# Fix any missing dependencies
apt-get -f install

The main issue here is likely that your 2017.1 system is pointing to modern, rolling repositories that no longer support such an old release. Switching to the archived sources should resolve the package availability problem that --fix-missing couldn't handle on its own.

内容的提问来源于stack exchange，提问作者MohOuss