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=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,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=ham 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 3F6C31F463 for ; Mon, 6 Jan 2020 07:33:31 +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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=Y7utx wD6XZ7GNi5ujbm5/wuG7NcZBjZr03BAOcnwIHxRqTk03EDp2T50YytuKur5cZBKA XxlPDdeSK8Y3J5Pzfhf1DTmCb3yBt6ONUSVfraPSaC/AZX16VmK+4xVw5UhZgzJx TaPIahLpnbMd4UrZ2MNKy3nC7wVngLP4ab5U0I= 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:from:to:cc:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=5lqiDp5k8zC NuGpIq4gkqs6nsRA=; b=ZbZLgktysVsk3PtujysK/ljYZ3LGERP2vUxMVdgPD29 dqvQ3/9usV96kDy7leRpJbkshi9jQSjvTJZow2aJ38qfTIR9HPAy8lVZrq/l9pb5 qez4D4SMHIis3MfHWYqgeGeBpV4ApAP66LsDTDcIlONF/JiyrCSdueofA4w1QKsQ = Received: (qmail 25527 invoked by alias); 6 Jan 2020 07:33:28 -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 25519 invoked by uid 89); 6 Jan 2020 07:33:28 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: albireo.enyo.de From: Florian Weimer To: Jason Yang Cc: libc-alpha@sourceware.org Subject: Re: A question on glibc backwards compatibility References: <2e35fa4e-7b88-ddeb-ddd4-bb87d9ad9ebb@gmail.com> Date: Mon, 06 Jan 2020 08:32:26 +0100 In-Reply-To: <2e35fa4e-7b88-ddeb-ddd4-bb87d9ad9ebb@gmail.com> (Jason Yang's message of "Mon, 6 Jan 2020 11:59:32 +0900") Message-ID: <8736ctca5x.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain * Jason Yang: > 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? We expect glibc 2.5 built with a matching compiler and kernel headers to work on current kernels, at least on the major architectures.