From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rnickb731@gmail.com>
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com
 [IPv6:2607:f8b0:4864:20::d36])
 by sourceware.org (Postfix) with ESMTPS id 65F543857824
 for <libc-help@sourceware.org>; Thu, 17 Dec 2020 20:47:55 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 65F543857824
Received: by mail-io1-xd36.google.com with SMTP id q137so28864841iod.9
 for <libc-help@sourceware.org>; Thu, 17 Dec 2020 12:47:55 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=idxuuXXaZbjpEnDm8k0cBtSw6XUks/BpCbyI9hUwXEg=;
 b=iRMjU7ynrycGUs1aHIN+K2XwDm8HjVVBhQ6P8GJXHw91Mbn/osfDSt0GCamhMsDibe
 ET2WMhEzdyUFlcXLQ5gz1q+/Hi5g8AW0lf5EQ3qwCPNiCZW/mNhSWsORIKkY5zONhnfx
 61EK9CCwFewSGRKhD0S+8V39KjPxWVi4Ya6KYAjLdgPcvNnNa2stHMCz34kEnNRSkBbZ
 PJHEdrOwUxSMarVepdpWTkHUxqVxyjvGrXdQuyAjmp3t2n+RTLJEoL2qOyfI3soNz/Wb
 ZI1gXKpD2TNrbPKgf+ATe+Ybu2ndGJykDTUUXokF58HfyN1ymLrTmaDuT/KXdH8m8W0T
 upFQ==
X-Gm-Message-State: AOAM531XObSlGolChZ+jCnwIjLud4w2TLKdHZrxnHEKCV94jEE4mEwDy
 BYOLTVV3hkcgHnjCpB0EifBhPFqiR1E16PO1r156vOX1zDg=
X-Google-Smtp-Source: ABdhPJxh9wVzZVjuBIkF6QYZkAALVYDelHusgP/OTlT/Wc45anMx6QS4jR0rEUgKsXYBCVwewJXL4yoFfmMQWXd4F10=
X-Received: by 2002:a02:4005:: with SMTP id n5mr723730jaa.105.1608238074918;
 Thu, 17 Dec 2020 12:47:54 -0800 (PST)
MIME-Version: 1.0
References: <CACqP_wyc_RU8uMsRaPgrER-yWb4DqdT=wT35wOG6H6pmpWL9BQ@mail.gmail.com>
 <87lfdwdwb4.fsf@mid.deneb.enyo.de>
In-Reply-To: <87lfdwdwb4.fsf@mid.deneb.enyo.de>
From: Ryan Burn <rnickb731@gmail.com>
Date: Thu, 17 Dec 2020 12:47:44 -0800
Message-ID: <CACqP_wwR2zeXZgtwASAXQ7+HFXz85DeLA8zZH2RGJKGwkiC8vA@mail.gmail.com>
Subject: Re: Trouble with portable linking
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Ryan Burn via Libc-help <libc-help@sourceware.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
 FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: libc-help@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Libc-help mailing list <libc-help.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/libc-help>,
 <mailto:libc-help-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/libc-help/>
List-Help: <mailto:libc-help-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/libc-help>,
 <mailto:libc-help-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2020 20:47:57 -0000

On Thu, Dec 17, 2020 at 12:14 PM Florian Weimer <fw@deneb.enyo.de> wrote:

>
> If you want to be compatible with glibc versions that check the
> embedded soname in symbol versions (which is not visible in the @
> syntax), you need to build a stub library that defines the required
> symbol versions in the right shared object.  There is no way to
> achieve this with .symver directives.

Thanks for the response! Could you elaborate a little more on how I
can build the stub library?

If I understand correctly, newer versions of glibc will resolve a
versioned symbol even if the embedded soname doesn't match. Is there a
way to explicitly define the soname so that I can specify it to
libpthread? Then it would work with both newer and older versions of
glibc, right?