{"id":34661,"date":"2025-11-20T10:01:06","date_gmt":"2025-11-20T07:01:06","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/openwrt-libgcc_s-so-1-hatasi-elf-sinifi-sorunlari-ve-cozumleri\/"},"modified":"2025-11-20T10:01:06","modified_gmt":"2025-11-20T07:01:06","slug":"openwrt-libgcc_s-so-1-hatasi-elf-sinifi-sorunlari-ve-cozumleri","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/openwrt-libgcc_s-so-1-hatasi-elf-sinifi-sorunlari-ve-cozumleri\/","title":{"rendered":"OpenWrt libgcc_s.so.1 Hatas\u0131: ELF S\u0131n\u0131f\u0131 Sorunlar\u0131 ve \u00c7\u00f6z\u00fcmleri"},"content":{"rendered":"

<\/p>\n

OpenWrt tabanl\u0131 cihaz\u0131n\u0131zda bir uygulama \u00e7al\u0131\u015ft\u0131rmak isterken aniden “error while loading shared libraries: libgcc_s.so.1: wrong ELF class: ELFCLASS32”<\/b> hatas\u0131yla kar\u015f\u0131la\u015ft\u0131n\u0131z m\u0131? Bu hata mesaj\u0131, \u00f6zellikle g\u00f6m\u00fcl\u00fc sistemler ve cross-compilation d\u00fcnyas\u0131na yeni ad\u0131m atanlar i\u00e7in olduk\u00e7a kafa kar\u0131\u015ft\u0131r\u0131c\u0131 olabilir. Ne yapaca\u011f\u0131n\u0131z\u0131 bilmedi\u011finizde, bu t\u00fcr bir uyumsuzluk sadece projenizi yava\u015flatmakla kalmaz, ayn\u0131 zamanda ciddi bir moral bozuklu\u011funa da yol a\u00e7abilir. Ancak endi\u015felenmeyin, bu makale size bu sorunun k\u00f6kenlerini anlaman\u0131z ve kal\u0131c\u0131 \u00e7\u00f6z\u00fcmler bulman\u0131z i\u00e7in ad\u0131m ad\u0131m rehberlik edecek.<\/p>\n

Bu makalede, \u00f6ncelikle hatan\u0131n ne anlama geldi\u011fini, OpenWrt ba\u011flam\u0131nda neden ortaya \u00e7\u0131kt\u0131\u011f\u0131n\u0131 ve sonras\u0131nda bu teknik bilmecenin nas\u0131l \u00e7\u00f6z\u00fclece\u011fini detayl\u0131 bir \u015fekilde inceleyece\u011fiz. Ayr\u0131ca, ger\u00e7ek d\u00fcnya senaryolar\u0131yla konuyu peki\u015ftirecek, ileri d\u00fczey ipu\u00e7lar\u0131yla gelecekte benzer sorunlarla kar\u015f\u0131la\u015fmaman\u0131z\u0131 sa\u011flayacak bilgiler sunaca\u011f\u0131z. Haz\u0131rsan\u0131z, OpenWrt’deki payla\u015f\u0131ml\u0131 k\u00fct\u00fcphane uyumsuzluklar\u0131n\u0131n gizemini \u00e7\u00f6zmeye ba\u015flayal\u0131m!<\/p>\n

Bu karma\u015f\u0131k hatay\u0131 anlamak i\u00e7in, \u00f6ncelikle baz\u0131 temel kavramlar\u0131 derinlemesine kavramak gereklidir. OpenWrt, y\u00f6nlendiriciler ve di\u011fer g\u00f6m\u00fcl\u00fc cihazlar i\u00e7in \u00f6zel olarak tasarlanm\u0131\u015f, Linux tabanl\u0131 a\u00e7\u0131k kaynakl\u0131 bir i\u015fletim sistemidir. K\u00fc\u00e7\u00fck boyutuna ra\u011fmen, tam \u00f6zellikli bir Linux \u00e7ekirde\u011fi sunar ve bu da onu IoT cihazlar\u0131ndan a\u011f cihazlar\u0131na kadar geni\u015f bir yelpazede kullan\u0131labilir k\u0131lar. Ancak, bu k\u00fc\u00e7\u00fck cihazlarda uygulama geli\u015ftirmek, standart masa\u00fcst\u00fc Linux da\u011f\u0131t\u0131mlar\u0131na g\u00f6re baz\u0131 \u00f6zel zorluklar bar\u0131nd\u0131r\u0131r.<\/p>\n

Payla\u015f\u0131ml\u0131 k\u00fct\u00fcphaneler (shared libraries), modern i\u015fletim sistemlerinin vazge\u00e7ilmez bir par\u00e7as\u0131d\u0131r. Uygulamalar\u0131n ihtiya\u00e7 duydu\u011fu ortak fonksiyonlar\u0131 (\u00f6rne\u011fin, bir dosyay\u0131 okuma, a\u011f ba\u011flant\u0131s\u0131 kurma gibi) ayr\u0131 dosyalar halinde bar\u0131nd\u0131r\u0131rlar. Bu k\u00fct\u00fcphaneler, bir uygulama \u00e7al\u0131\u015ft\u0131\u011f\u0131nda dinamik olarak y\u00fcklenir ve b\u00f6ylece her uygulaman\u0131n kendi kopyas\u0131n\u0131 ta\u015f\u0131mas\u0131 yerine bellekte tek bir kopyan\u0131n payla\u015f\u0131lmas\u0131 sa\u011flan\u0131r. Bu yakla\u015f\u0131m, hem disk alan\u0131ndan tasarruf edilmesini hem de bellek kullan\u0131m\u0131n\u0131n optimize edilmesini sa\u011flar. Linux sistemlerinde bu k\u00fct\u00fcphaneler genellikle .so<\/code> (shared object) uzant\u0131s\u0131na sahiptir ve hata mesaj\u0131m\u0131zda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz libgcc_s.so.1<\/code> de bunlardan biridir.<\/p>\n

Peki, libgcc_s.so.1<\/code> tam olarak nedir? Bu, GCC (GNU Compiler Collection) taraf\u0131ndan derlenen programlar\u0131n \u00e7al\u0131\u015fma zaman\u0131 deste\u011fi i\u00e7in kritik \u00f6neme sahip bir k\u00fct\u00fcphanedir. \u00d6zellikle, d\u00fc\u015f\u00fck seviyeli aritmetik i\u015flemler, istisna y\u00f6netimi ve \u00e7e\u015fitli di\u011fer C\/C++ \u00e7al\u0131\u015fma zaman\u0131 i\u015flevlerini i\u00e7erir. Bir program\u0131n bu k\u00fct\u00fcphaneyi bulamamas\u0131 veya uyumsuz bir s\u00fcr\u00fcm\u00fcn\u00fc bulmas\u0131, program\u0131n ba\u015flamamas\u0131na neden olur. \u0130\u015fte bu noktada ELF format\u0131<\/b> devreye girer. ELF (Executable and Linkable Format), Linux ve di\u011fer Unix benzeri sistemlerde y\u00fcr\u00fct\u00fclebilir dosyalar\u0131n, payla\u015f\u0131ml\u0131 k\u00fct\u00fcphanelerin ve \u00e7ekirdek mod\u00fcllerinin standart dosya bi\u00e7imidir. Bir ELF dosyas\u0131, dosyan\u0131n mimarisi (\u00f6rn. ARM, MIPS, x86), bit boyutu (32-bit veya 64-bit) ve di\u011fer \u00f6nemli meta veriler hakk\u0131nda bilgiler i\u00e7eren bir ba\u015fl\u0131k (header) ta\u015f\u0131r. \u0130\u015fletim sistemi, bir program\u0131 veya k\u00fct\u00fcphaneyi y\u00fcklemeye \u00e7al\u0131\u015ft\u0131\u011f\u0131nda, bu ba\u015fl\u0131\u011f\u0131 okur ve sistemin mimarisiyle uyumlu olup olmad\u0131\u011f\u0131n\u0131 kontrol eder.<\/p>\n

Hata mesaj\u0131ndaki “wrong ELF class: ELFCLASS32”<\/b> ifadesi tam olarak bu uyumsuzlu\u011fu i\u015faret eder. Bu ifade, sistemin bekledi\u011fi ELF s\u0131n\u0131f\u0131ndan (\u00f6rne\u011fin, 64-bit bir sistemde 64-bit bir k\u00fct\u00fcphane) farkl\u0131 olarak 32-bit bir ELF s\u0131n\u0131f\u0131na sahip bir k\u00fct\u00fcphane (ELFCLASS32<\/code>) buldu\u011funu belirtir. Bu durum, genellikle 64-bit bir i\u015flemci mimarisine sahip bir OpenWrt cihaz\u0131nda, yanl\u0131\u015fl\u0131kla 32-bit bir mimariye g\u00f6re derlenmi\u015f bir k\u00fct\u00fcphaneyi kullanmaya \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131zda ortaya \u00e7\u0131kar. Ya da tam tersi, 32-bit bir cihazda 64-bit bir k\u00fct\u00fcphane kullanmaya \u00e7al\u0131\u015f\u0131yorsunuzdur. G\u00f6m\u00fcl\u00fc sistemlerde, i\u015flemci mimarileri (MIPS, ARM, PowerPC vb.) ve bunlar\u0131n bit boyutlar\u0131 (32-bit veya 64-bit) b\u00fcy\u00fck farkl\u0131l\u0131klar g\u00f6sterir, bu da cross-compilation s\u0131ras\u0131nda dikkatli olmay\u0131 zorunlu k\u0131lar.<\/p>\n

“wrong ELF class” Hatas\u0131n\u0131n Temel Nedenleri Nelerdir?<\/h2>\n

OpenWrt ortam\u0131nda “error while loading shared libraries: libgcc_s.so.1: wrong ELF class: ELFCLASS32”<\/b> hatas\u0131n\u0131n temelinde yatan nedenleri anlamak, do\u011fru \u00e7\u00f6z\u00fcme ula\u015fman\u0131n ilk ad\u0131m\u0131d\u0131r. Bu hata genellikle \u00fc\u00e7 ana senaryo etraf\u0131nda \u015fekillenir:<\/p>\n

    \n
  1. Cross-Compilation (\u00c7apraz Derleme) Uyumsuzluklar\u0131:<\/b> En yayg\u0131n nedenlerden biri, uygulamay\u0131 veya k\u00fct\u00fcphaneyi yanl\u0131\u015f hedef mimari i\u00e7in derlemektir. OpenWrt cihaz\u0131n\u0131z\u0131n i\u015flemcisi (\u00f6rne\u011fin, MIPS32, ARMv7, ARMv8\/AArch64) kendi geli\u015ftirme ortam\u0131n\u0131z\u0131n i\u015flemcisinden (genellikle x86_64) farkl\u0131d\u0131r. Bir uygulamay\u0131 kendi bilgisayar\u0131n\u0131zda derledi\u011finizde, bu genellikle bilgisayar\u0131n\u0131z\u0131n mimarisi i\u00e7in (native) derlenir. Ancak bu uygulamay\u0131 veya onun ba\u011f\u0131ml\u0131 k\u00fct\u00fcphanelerini do\u011frudan OpenWrt cihaz\u0131na kopyalad\u0131\u011f\u0131n\u0131zda, hedef cihaz\u0131n mimarisiyle uyumsuzluk nedeniyle bu hatay\u0131 al\u0131rs\u0131n\u0131z. \u00d6rne\u011fin, 64-bit bir ARM i\u015flemciye sahip bir OpenWrt router’a, 32-bit MIPS mimarisi i\u00e7in derlenmi\u015f bir libgcc_s.so.1<\/code> kopyalamak, bu hatay\u0131 tetikleyecektir.<\/li>\n
  2. Yanl\u0131\u015f Toolchain veya SDK Kullan\u0131m\u0131:<\/b> OpenWrt i\u00e7in uygulama geli\u015ftirmenin do\u011fru yolu, o cihaza ve OpenWrt s\u00fcr\u00fcm\u00fcne \u00f6zel olarak haz\u0131rlanm\u0131\u015f bir Software Development Kit (SDK) veya Buildroot kullanmakt\u0131r. Bu SDK’lar, hedef mimariye uygun derleyiciler (cross-compilers), k\u00fct\u00fcphaneler ve ba\u015fl\u0131k dosyalar\u0131 (header files) i\u00e7erir. E\u011fer yanl\u0131\u015f bir SDK (\u00f6rne\u011fin, farkl\u0131 bir mimariye ait veya farkl\u0131 bir OpenWrt s\u00fcr\u00fcm\u00fcne ait) kullan\u0131l\u0131rsa veya manuel olarak y\u00fcklenen k\u00fct\u00fcphaneler yanl\u0131\u015f kaynaktan gelirse, k\u00fct\u00fcphanelerin ELF s\u0131n\u0131flar\u0131 hedef cihaz\u0131n bekledi\u011fiyle uyu\u015fmayabilir. \u00d6zellikle, 32-bit ve 64-bit uyumsuzluklar\u0131 bu durumda s\u0131k\u00e7a g\u00f6r\u00fcl\u00fcr.<\/li>\n
  3. Manuel K\u00fct\u00fcphane Y\u00fcklemelerinde Yap\u0131lan Hatalar:<\/b> Bazen kullan\u0131c\u0131lar, eksik k\u00fct\u00fcphaneleri manuel olarak internetten indirip cihaz\u0131n \/usr\/lib<\/code> veya \/lib<\/code> dizinine kopyalamaya \u00e7al\u0131\u015f\u0131r. \u0130nternetten rastgele bulunan bir k\u00fct\u00fcphanenin, cihaz\u0131n\u0131z\u0131n mimarisi ve bit boyutuyla birebir uyumlu olmas\u0131 \u00e7ok d\u00fc\u015f\u00fckt\u00fcr. Bu t\u00fcr manuel m\u00fcdahaleler, \u00e7al\u0131\u015fan bir sistemde bile uyumsuz k\u00fct\u00fcphanelerin \u00fczerine yaz\u0131lmas\u0131na ve daha geni\u015f sistem karars\u0131zl\u0131klar\u0131na yol a\u00e7abilir. Bu senaryo, hatan\u0131n en s\u0131k kar\u015f\u0131la\u015f\u0131ld\u0131\u011f\u0131 durumlardan biridir, \u00e7\u00fcnk\u00fc kullan\u0131c\u0131lar genellikle sorunu \u00e7\u00f6zmek i\u00e7in en h\u0131zl\u0131 yolu ararlar ve bu da \u00e7o\u011fu zaman yanl\u0131\u015f k\u00fct\u00fcphane se\u00e7imine yol a\u00e7ar.<\/li>\n<\/ol>\n

    Vaka Analizi: Ahmet’in Ak\u0131ll\u0131 Ev Sens\u00f6r\u00fc Projesi<\/h3>\n

    Ahmet, evindeki s\u0131cakl\u0131k ve nem verilerini okuyan k\u00fc\u00e7\u00fck bir C program\u0131 yazd\u0131. Program\u0131, g\u00fc\u00e7l\u00fc Intel Core i7 i\u015flemcisine sahip 64-bit Linux geli\u015ftirme bilgisayar\u0131nda sorunsuz bir \u015fekilde derledi ve test etti. Amac\u0131, bu program\u0131 OpenWrt kurulu 32-bit MIPS mimarisine sahip TP-Link router’\u0131nda \u00e7al\u0131\u015ft\u0131rmakt\u0131. Program\u0131 scp<\/code> ile router’a kopyalad\u0131ktan sonra \u00e7al\u0131\u015ft\u0131rmaya \u00e7al\u0131\u015ft\u0131\u011f\u0131nda, an\u0131nda “error while loading shared libraries: libgcc_s.so.1: wrong ELF class: ELFCLASS32”<\/b> hatas\u0131yla kar\u015f\u0131la\u015ft\u0131. Ahmet’in program\u0131 elbette kendi 64-bit x86_64 mimarisi i\u00e7in derlenmi\u015fti ve OpenWrt router’\u0131, bu program\u0131n ihtiya\u00e7 duydu\u011fu libgcc_s.so.1<\/code> k\u00fct\u00fcphanesini kendi \u00fczerinde (32-bit MIPS i\u00e7in) bulam\u0131yordu. Hata mesaj\u0131ndaki ELFCLASS32<\/code> k\u0131sm\u0131, asl\u0131nda Ahmet’in program\u0131n\u0131n (ve dolay\u0131s\u0131yla dolayl\u0131 yoldan bekledi\u011fi k\u00fct\u00fcphanenin) 32-bit ELF format\u0131nda olmas\u0131 gerekti\u011fini, ancak kendisinin 64-bit bir sistemde \u00e7al\u0131\u015ft\u0131\u011f\u0131 yan\u0131lg\u0131s\u0131na d\u00fc\u015ft\u00fc\u011f\u00fcn\u00fc veya 32-bit bir sisteme 64-bit bir binary ta\u015f\u0131maya \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6stermiyordu. Daha ziyade, OpenWrt sistemindeki mevcut libgcc_s.so.1<\/code>‘in 32-bit oldu\u011funu, ancak Ahmet’in program\u0131n\u0131n beklentisinin farkl\u0131 oldu\u011funu belirtiyordu. Asl\u0131nda, Ahmet’in kendi bilgisayar\u0131nda derledi\u011fi uygulama 64-bit x86_64 ELF s\u0131n\u0131f\u0131ndayd\u0131. Router’da \u00e7al\u0131\u015ft\u0131rmaya \u00e7al\u0131\u015ft\u0131\u011f\u0131nda ise, router’\u0131n 32-bit MIPS mimarisiyle uyu\u015fmayan bir 64-bit x86_64 uygulamas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmaya \u00e7al\u0131\u015ft\u0131 ve bu uygulama da router’\u0131n 32-bit MIPS libgcc_s.so.1<\/code>‘ini y\u00fckleyemedi\u011fi i\u00e7in hata verdi. K\u0131sacas\u0131, Ahmet’in uygulamas\u0131 router’\u0131n bekledi\u011fi t\u00fcrden (32-bit MIPS) de\u011fildi ve bu y\u00fczden onunla birlikte gelen k\u00fct\u00fcphaneleri kullanamad\u0131. Bu vaka, cross-compilation’\u0131n \u00f6nemini ve do\u011fru toolchain kullan\u0131m\u0131n\u0131n kritikli\u011fini a\u00e7\u0131k\u00e7a ortaya koymaktad\u0131r.<\/p>\n

    Sorunu Nas\u0131l Te\u015fhis Edebiliriz? Ad\u0131m Ad\u0131m \u0130nceleme<\/h2>\n

    Hatan\u0131n temel nedenlerini anlad\u0131\u011f\u0131m\u0131za g\u00f6re, \u015fimdi bu sorunu nas\u0131l te\u015fhis edece\u011fimize odaklanal\u0131m. Do\u011fru te\u015fhis, do\u011fru \u00e7\u00f6z\u00fcme ula\u015fman\u0131n anahtar\u0131d\u0131r. A\u015fa\u011f\u0131daki ad\u0131mlar\u0131 uygulayarak OpenWrt cihaz\u0131n\u0131zdaki ve problem yaratan dosyalardaki uyumsuzluklar\u0131 belirleyebilirsiniz.<\/p>\n

    1. Problemli Dosyan\u0131n ELF S\u0131n\u0131f\u0131n\u0131 ve Mimarini Kontrol Etme<\/h3>\n

    Hata mesaj\u0131, libgcc_s.so.1<\/code> dosyas\u0131n\u0131n ELFCLASS32<\/code> oldu\u011funu belirtiyor. Bu, k\u00fct\u00fcphanenin 32-bit bir mimari i\u00e7in derlendi\u011fi anlam\u0131na gelir. Ancak as\u0131l soru \u015fudur: Cihaz\u0131n\u0131z bu k\u00fct\u00fcphanenin 32-bit versiyonunu mu bekliyor, yoksa 64-bit mi? Ve daha da \u00f6nemlisi, cihaz\u0131n\u0131z\u0131n i\u015flemci mimarisi nedir? Bu bilgileri edinmek i\u00e7in file<\/code> komutunu kullanaca\u011f\u0131z.<\/p>\n

    Ad\u0131m 1.1: OpenWrt cihaz\u0131n\u0131zdaki libgcc_s.so.1<\/code> dosyas\u0131n\u0131 kontrol edin.<\/b><\/p>\n

    \nfile \/usr\/lib\/libgcc_s.so.1\n<\/pre>\n
    <\/code><\/p>\n
    Bu komutun \u00e7\u0131kt\u0131s\u0131 \u015f\u00f6yle bir \u015fey olabilir:<\/p>\n
    \n\/usr\/lib\/libgcc_s.so.1: ELF 32-bit LSB shared object, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked, stripped\n<\/pre>\n
    <\/code><\/p>\n
    Bu \u00e7\u0131kt\u0131dan anlad\u0131\u011f\u0131m\u0131z: libgcc_s.so.1<\/code> bir 32-bit<\/b>, MIPS<\/b> mimarisi i\u00e7in derlenmi\u015f payla\u015f\u0131ml\u0131 k\u00fct\u00fcphanedir. E\u011fer bu \u00e7\u0131kt\u0131 sizin router'\u0131n\u0131z\u0131n ger\u00e7ek mimarisi ve bit boyutuyla uyu\u015fmuyorsa, sorun buradad\u0131r. \u00d6rne\u011fin, e\u011fer router'\u0131n\u0131z 64-bit ARM mimarisine sahipse, bu 32-bit MIPS k\u00fct\u00fcphanesi yanl\u0131\u015f olacakt\u0131r.<\/p>\n
    Ad\u0131m 1.2: \u00c7al\u0131\u015ft\u0131rmaya \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131z uygulaman\u0131n (veya di\u011fer ba\u011f\u0131ml\u0131 k\u00fct\u00fcphanelerin) ELF s\u0131n\u0131f\u0131n\u0131 kontrol edin.<\/b><\/p>\n
    E\u011fer hatay\u0131 kendi derledi\u011finiz bir uygulama y\u00fcz\u00fcnden al\u0131yorsan\u0131z, o uygulaman\u0131n da mimarisini kontrol etmelisiniz:<\/p>\n
    \nfile \/path\/to\/your\/application\n<\/pre>\n
    <\/code><\/p>\n
    \u00d6rne\u011fin, \u00e7\u0131kt\u0131n\u0131n \u015f\u00f6yle oldu\u011funu varsayal\u0131m:<\/p>\n
    \n\/path\/to\/your\/application: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter \/lib\/ld-musl-aarch64.so.1, stripped\n<\/pre>\n
    <\/code><\/p>\n
    Bu durumda, uygulaman\u0131z 64-bit ARM (aarch64)<\/b> mimarisi i\u00e7in derlenmi\u015fken, yukar\u0131daki libgcc_s.so.1<\/code> \u00e7\u0131kt\u0131s\u0131 32-bit MIPS<\/b> idi. \u0130\u015fte bu tam olarak bir uyumsuzluk durumudur! 64-bit ARM uygulamas\u0131, kendisiyle uyumlu 64-bit ARM libgcc_s.so.1<\/code> beklerken, sistemde 32-bit MIPS versiyonunu buluyor ve bu da \"wrong ELF class\"<\/b> hatas\u0131na yol a\u00e7\u0131yor.<\/p>\n
    2. OpenWrt Cihaz\u0131n\u0131z\u0131n Ger\u00e7ek Mimarisini Belirleme<\/h3>\n
    Hatan\u0131n kayna\u011f\u0131n\u0131 anlamak i\u00e7in OpenWrt cihaz\u0131n\u0131z\u0131n i\u015flemci mimarisini kesin olarak bilmeniz gerekir. Bunu \u00f6\u011frenmenin birka\u00e7 yolu vard\u0131r:<\/p>\n