From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-2.7 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF, FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 9A46F1F463 for ; Mon, 6 Jan 2020 02:59:41 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:message-id:date:mime-version :content-type:content-transfer-encoding; q=dns; s=default; b=d58 HOy8ysiW7Rk6Qzl5ODvos+ChbjVxzcjXLzsVZLJvk/ALn/+wVtiGWgfgcpHWBSi+ 1R2+zRHhZhYzVgEvgEosKhnFOOh7MMfATVhEzZQ0ljy8IWjW6+Vyem879sWeQpg+ fOMHoc/dLiMMs8KP0sBL/RhlkVGwNAp1iafgN48Y= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:message-id:date:mime-version :content-type:content-transfer-encoding; s=default; bh=+WN+85Z5p sIrlTEsTUlqSypSSw4=; b=BzLYPe5W8+w3NAeAu/Cul4zvQ9kVbcRan/LcWOBy7 maKhHioM0Mybzx5QHaG3plWs85HNjJtUaxCpKO0k7FnL/sNyuVOiFSfCfZ993978 bR/UZHnEdOgiHONmLiP8u3hG5SKeY7meGTlaBtA9cRl1dROBIW+iIcXV4amUQdKG 1E= Received: (qmail 38620 invoked by alias); 6 Jan 2020 02:59:39 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 38611 invoked by uid 89); 6 Jan 2020 02:59:38 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-pf1-f177.google.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=p0IuCllk8NSfz47/jMnWx95Q8uiPNkUq41a8ERVWkus=; b=UEJo5/GTaL7GCZ/EEtIMecU4klPPjP1NSfP2T4XM81jOZOxLQkGJH0bzzBliAI2Qv4 ZDZRPodXX2B29dizA+nMtZZpsJbWWeYSwvXWjgVHCS4AGLou35FFa6+lJSRBdUU6U13K Wx55sgxw45mLMAc1KTvVP3rqN0hKNnzEPyWL7GMHZQFUahAqggcxsnOwL++tVEo6JFHC QGPKfqZ+7aSz2cMWETMJ1Bie4if3ho3/kiNInUHmhqPK++XasAjw+O5MBVz9rd7RpZkH oQJJKGhw5IeFSHe0O/xAHsX0zod69nFm+WoTSG/Ac73B8QbJnkeDAZmS6pGieB+RekKG 5e6A== To: libc-alpha@sourceware.org From: Jason Yang Subject: A question on glibc backwards compatibility Message-ID: <2e35fa4e-7b88-ddeb-ddd4-bb87d9ad9ebb@gmail.com> Date: Mon, 6 Jan 2020 11:59:32 +0900 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Dear Developers: I knew that glibc has very good backwards compatibility. But I have an issue during my development. I use very old glibc(version 2.5) to compile my own developed dynamic library and use it on newer kernel, some weird issues happen. Here, I could not explain these issues in details because there are so much code involved. But my question is that, glibc backwards compatibility is strict support? or if there are any(few) exceptions? If there are exceptions where can I find them? Sincerely looking forward to your response. Regards Jason