From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id B937C3858D1E for ; Thu, 1 Sep 2022 12:19:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B937C3858D1E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1662034754; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FeTBe+m7PEsT9ob2BYG23Y58g5cGRCsfvPtht1xWqdM=; b=aJSie2s1Wt57BpzHvW/9sT0r0AT770BBkZUe7Znd91/r0OAL/b7F1hFKZpaXXsY2yQay0H b1cp9HIgxr7dvJcjKjZsKcuL01c7dQDVmJDsQhwF1vFut9G2sb1rKMt0VAB90akGYg8Z6O V/1oXtZWH/usLfuxOVVUFOJ6nrHNVks= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-168-x3k812jMO5yThiV8A8esTw-1; Thu, 01 Sep 2022 08:19:11 -0400 X-MC-Unique: x3k812jMO5yThiV8A8esTw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3ADC185A58A; Thu, 1 Sep 2022 12:19:10 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.37]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9C573403D0D3; Thu, 1 Sep 2022 12:19:09 +0000 (UTC) From: Florian Weimer To: Lv Ying via Libc-help Cc: Lv Ying Subject: Re: ldconfig is statically linked or dynamiclly linked References: <3f822786-189c-1c45-9415-be3f1abe916b@gmail.com> Date: Thu, 01 Sep 2022 14:19:07 +0200 In-Reply-To: <3f822786-189c-1c45-9415-be3f1abe916b@gmail.com> (Lv Ying via Libc-help's message of "Thu, 1 Sep 2022 17:41:39 +0800") Message-ID: <87ilm7qock.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Lv Ying via Libc-help: > So ldconfig is dynamiclly linked or statically linked? Usually, glibc ldconfig is statically linked. The output of the file tool is notoriously unreliable. > I think ldconfig may be statically linked, and can ldconfig be only > statically linked? It's technically possible to link it dynamically, with a few makefile changes, but we don't do that, to make it easier to recover from certain failure scenarios. Thanks, Florian