From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) by sourceware.org (Postfix) with ESMTPS id C67543858C50 for ; Wed, 30 Mar 2022 01:50:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C67543858C50 Received: by mail-pf1-x435.google.com with SMTP id w7so14788003pfu.11 for ; Tue, 29 Mar 2022 18:50:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=6vwBV6pM08V6ivz0pfMXG2TACkhrLyEcbqzbWpKlT6g=; b=3nKA441fldBlQtMJgjpy1wihLrQEDnfpl7EeZdFI+hDTsQZJ/VNymomN7HDFh3/up6 WmOD+9fe96tvQEoUeYzUo5va06MVVdkGhnPGbwfRTq3e/Xer2rnuzodwA5LAOGjAo0uP jBjjNi4f42ejsKIFEvuCh9u0ujuaBg5SjwOxdmmjRFS8Fc2soWH+ro8dgT4NZLV9eyPU UaiM830ZRAUq2Lv1GkDAojStVTjFF4BTUMdxwg1KlyAvivZEHKIG/9B7z8HHCS2S27NK mhV1GrX/42qEhTJJf52U96HAKHh4Un8sNdg0Xfymxj/nSNC6V1aklpopofXvTCPGiF3q /M6A== X-Gm-Message-State: AOAM531CRw1NuyLTq2M4gpguL+y3rlPxAW0IcChRkARr5F+yMJIaYFP1 CFZnWal32g8tlAngMxHOw3B7K2FmkfQ= X-Google-Smtp-Source: ABdhPJxFBcmIFXnsPuL5WCUFhwvSk3lv+TkS9He+JQWA076qaYfKH1tpgToNPPXAkycGgYDltp4mKQ== X-Received: by 2002:a63:3f8f:0:b0:386:3116:a1f3 with SMTP id m137-20020a633f8f000000b003863116a1f3mr4176042pga.136.1648605008385; Tue, 29 Mar 2022 18:50:08 -0700 (PDT) Received: from squeak.grove.modra.org ([2406:3400:51d:8cc0:2b3c:fc1c:2309:24b4]) by smtp.gmail.com with ESMTPSA id u37-20020a056a0009a500b004f820de3dcdsm21567716pfg.9.2022.03.29.18.50.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Mar 2022 18:50:07 -0700 (PDT) Received: by squeak.grove.modra.org (Postfix, from userid 1000) id C23811140025; Wed, 30 Mar 2022 12:20:04 +1030 (ACDT) Date: Wed, 30 Mar 2022 12:20:04 +1030 From: Alan Modra To: Michael Tokarev Cc: binutils Subject: Re: puzzling ld behavior, failing to find symbols from .so after adding more .o file Message-ID: References: <7f94bd18-ff3e-d3de-d3a6-1568a0b3709c@msgid.tls.msk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f94bd18-ff3e-d3de-d3a6-1568a0b3709c@msgid.tls.msk.ru> X-Spam-Status: No, score=-3029.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2022 01:50:11 -0000 On Sat, Mar 26, 2022 at 06:19:21PM +0300, Michael Tokarev wrote: > I think I got it sorted out. > > in the new version the tdb.h file (which declares tdb_null > and other stuff) added _PUBLIC_ attribute before all symbols, > which is by default evaluates to attribute(visibility(default)). > But when compiling samba, _PUBLIC_ is defined to > attribute(visibility(hidden)) before including tdb.h. > And things goes the wrong way from here... > > It is interesting still why ld behaves this way, but the > mystery is now solved. A hidden visibility symbol will not be put in .dynsym. So any newly built shared library defining one of the affected symbols won't provide a definition that can be used outside of that shared library. -- Alan Modra Australia Development Lab, IBM