From owner-freebsd-ports@freebsd.org Fri Aug 19 14:54:39 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 889F3BBD16E for ; Fri, 19 Aug 2016 14:54:39 +0000 (UTC) (envelope-from mokhi64@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12898144C for ; Fri, 19 Aug 2016 14:54:39 +0000 (UTC) (envelope-from mokhi64@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id o80so44854617wme.1 for ; Fri, 19 Aug 2016 07:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AuMoawMCMJ4/Acv2ppd2/pX+V6abgsbpLHc8V/pWFhc=; b=cI2PelChd0Mm6l+gwBBJOrz5/J+FCnfihlchRWOJ0UqymC3hOOf6mALJgtqL9YFZtC 88bFbqbloCXqNwIPISRkZ3U1kOASjau3iqNXPac4mLM+TcYluGkRN1RnfUxXnITc5ahI yaD19H0vTI/gVfCU+qShZ/t45LrxM7reFnkC+0L2m2lE+QJ9S7RV+bqPK14vLwdlnT2F iW4OCgr8n7ooxHc4Fb+wAdMbgnn9HlVwRJTAZZuhN9DTS75lp3XVNDOHplfLOzx5jpED f4FcYLKbuQRp5CGiXwHetKJPmgZQqESx6byWB9dyShr5ejKd9WJjPYEnrgsbyO/cuJ6e CWsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AuMoawMCMJ4/Acv2ppd2/pX+V6abgsbpLHc8V/pWFhc=; b=YDuAH6oh92sSwHS4vi8u1mZpmislvBdi/CSMAme2grtP133QEHTl48Satj7Zzle3P1 O0bB5JBDOVS8V6u3ny2aXzS7FXoS5//XXWAtw564iSGjGUR6q0EBM/fcjKoXng4tTCaf MlSjhteMeqlCj72KBwxg73nQjhURNwZ+I72tWQgXnOMhQa2gn3v+OrS/TKC2by9BABzg qVpKXSic2SfELFds1GNExljIE5BEBsmLh2OxPAsA/vdqCGGKi5Pg/vRFhSGvZkQ73fB5 B0tm+AGtsLgFafcENQQio4en9qkJIMcLk+Qz+WtP9aT0ipd8/ml844C/aw7OQz2Te3CA vFUQ== X-Gm-Message-State: AEkooutx3HSOXJXQ3cGxjIfs+/oqGsSxuSqcLurRUYuY8l6CVC13/0DKSEiRNnVRBDFMACiOWclUOgXWs1wpkw== X-Received: by 10.194.240.4 with SMTP id vw4mr6620101wjc.134.1471618477401; Fri, 19 Aug 2016 07:54:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.70.131 with HTTP; Fri, 19 Aug 2016 07:54:36 -0700 (PDT) In-Reply-To: References: From: mokhi Date: Fri, 19 Aug 2016 19:24:36 +0430 Message-ID: Subject: Re: how did BSD libc make binary compatibility promise beetween freebsd version? To: kang joni Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2016 14:54:39 -0000 If you mean using libc/libc++ API in FreeBSD with no break, This is what FreeBSD provides by symbol versioning to provide same/compatible API in different versions. This means If you have a program that uses an API [printf(3) for example] on FreeBSD 9, and a change made on that API in FreeBSD 10, you can be sure that change is compatible and doesn't break what you had expected till now. This is being implemented using symbol versioning. I'm not sure that i understand your question correct :) This is my answer to my interpretation of your question ;) [and also based on my interpretation of FreeBSD's behaviors and codes :D] Also as a side-note i guess freebsd-current@ is more helpful for you question's answer. Best regards, Mokhi.