From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) by sourceware.org (Postfix) with ESMTPS id 31BF13857C50 for ; Wed, 24 Mar 2021 15:16:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 31BF13857C50 Received: by mail-qv1-xf31.google.com with SMTP id d10so12446756qve.7 for ; Wed, 24 Mar 2021 08:16:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=A3bVugAgr2V/WP1I0aXzTF2ygeGrl9/OmSYDXbvgxn0=; b=i9go2sQRTzawXeQer3e8ctNGy/zk48z+aOkMZj5QP4LfiYA+AZYBkYQv74pyxAde5Y wKyel5YGnlsPdiuL+o9oIg//SgoL/G7Ad7IHwFwObKCn4iedB6MIp4XV3GZRzlWEnQti Oz48QZtYLGNhZpRDpbXCuuNTAV9RN/37NdBcqHNz/ZJ5cm+RyjyO+VJ1F9wymB/n+r+j cssnYxubBPQpE9S38WFeD/0qjUyY8oC1gWqsMb3i5Qibk8sfVfE1cIz5HgjVxOR/bk24 oS567Bi5iLTFWWm/us05KVJ8gXqdHhGVRZJ7ZEzPsVzJ25CGA5a8YyCcLw6DSIGiskvd FreA== X-Gm-Message-State: AOAM531I5mXKZFM6wKIC+30ZqbmVuqF6P1QZNP3M9xd3yfFXpGfSUerz hJO8JyaNKJcbiN19vk6E0VI0dw== X-Google-Smtp-Source: ABdhPJwY4biWMPoDWcid2/Aff/ayNHXk5N9LYMwJLtvYfi7gnRVsQXZXl1dADoT5RsHqjCvCVQlltg== X-Received: by 2002:a05:6214:9c9:: with SMTP id dp9mr3632602qvb.34.1616599004853; Wed, 24 Mar 2021 08:16:44 -0700 (PDT) Received: from ?IPv6:2804:7f0:4841:2841:ad61:3bf4:83da:f1f1? ([2804:7f0:4841:2841:ad61:3bf4:83da:f1f1]) by smtp.gmail.com with ESMTPSA id b12sm1623965qti.43.2021.03.24.08.16.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Mar 2021 08:16:44 -0700 (PDT) Subject: Re: Broken libcc1 lookup in GDB/Ubuntu From: Luis Machado To: "gdb@sourceware.org" , jan.kratochvil@redhat.com, Jeff Law , Christian Biesinger References: <51acf4b8-5c69-d9e4-c155-e7af083a3c33@linaro.org> Message-ID: Date: Wed, 24 Mar 2021 12:16:41 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <51acf4b8-5c69-d9e4-c155-e7af083a3c33@linaro.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, NICE_REPLY_A, 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: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2021 15:16:46 -0000 Adding Christian, as he ran into this as well. On 3/24/21 12:15 PM, Luis Machado wrote: > Hi, > > While looking at enabling the compile tests in GDB's testsuite, I > noticed GDB doesn't find the right shared library because it is looking > for a different naming pattern. > > In the case of Ubuntu 18.04/20.04, the shared library is named like so: > > /usr/lib/aarch64-linux-gnu/libcc1.so.0.0.0 > /usr/lib/aarch64-linux-gnu/libcc1.so.0 -> libcc1.so.0.0.0 > > But GDB is looking for libcc1.so in the following ways: > > #define GCC_C_FE_LIBCC libcc1.so > #define GCC_CP_FE_LIBCC libcc1.so > > So, basically, the gdb.compile tests will never be exercised > out-of-the-box, even if you install the libcc1 package. I had to add a > symlink named "libcc1.so" to make GDB happy. > > Now, I noticed there was a proposed fix for this many years ago, in the > following series: > > https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01241.html > https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01242.html > https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01243.html > https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01244.html > https://gcc.gnu.org/legacy-ml/gcc-patches/2015-04/msg01245.html > > Was this dropped for some reason? Or is this still valid and should be > pursued upstream? > > > Thanks, > Luis