From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) by sourceware.org (Postfix) with ESMTPS id 849D53857004 for ; Fri, 17 Jul 2020 22:03:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 849D53857004 Received: by mail-oi1-x22f.google.com with SMTP id r8so9224869oij.5 for ; Fri, 17 Jul 2020 15:03:40 -0700 (PDT) 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=UNAAyN5ek0FMgazdVaGkdpF/KvGuKXJGyLtfMbtp1GI=; b=oR1eXeqEv0Oq+mkdf47168XQCBUrEu45ms3Mg2300BhMybtsZG/Pv0xGMqIJC92Z+0 Dxk9uOgVndsqztPH7Dr4tptAvpJwDrqRnazkQkKDQMGBNCP3s7s4dJG4D+cTW+h7onP4 a6O1si/1feMErm4J6mOcFNComOWzWsnkf557a5GlQBJ6idNznfDJtMvY4erI7xAxgrXu fkm36SuBHwZrAzvglfVCsidJ39ElKRKfxxpQIzAuaKLvsgu9CpH6eXw0694mcLW+pFbA VgWQFYYYIr+O/YSCBedHt5Q2ivwr5LGzx75xCxRcKtalAIKJ0FrnADshrxwEwVHhFwqz nSkA== X-Gm-Message-State: AOAM5322FtbBBugREiQduIIv50gFsjGFWXN4cYR/umUEUcNE+WpXp1bF 2WdU7xMgHFuUqD/Ee4/F/2XFf/ZsUF3G8h/QfY0F9azC X-Google-Smtp-Source: ABdhPJzdp6pODzfRXVnLv2denpCbnsRp5HeKuHBmUr7saagqBHxtTk+0M/V2+gkyKozmtkw6rfGs1q2gskwhgX4ZjGc= X-Received: by 2002:aca:d1a:: with SMTP id 26mr8859609oin.11.1595023419836; Fri, 17 Jul 2020 15:03:39 -0700 (PDT) MIME-Version: 1.0 References: <20200717214210.GU5016@adacore.com> In-Reply-To: <20200717214210.GU5016@adacore.com> From: Reuben Thomas Date: Fri, 17 Jul 2020 23:03:28 +0100 Message-ID: Subject: Re: Adding Python files to be autoloaded for a particular architecture To: Joel Brobecker Cc: Reuben Thomas via Gdb X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, HTML_MESSAGE, 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 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Fri, 17 Jul 2020 22:03:42 -0000 On Fri, 17 Jul 2020 at 22:42, Joel Brobecker wrote: > > This seems to be a suitable candidate for SYSTEM_GDBINIT_FILES. But if I > > simply add a file to `SYSTEM_GDBINIT_FILES` in > > `gdb/data-directory/Makefile.in`, and then configure with > > > > --with-system-gdbinit-dir=$pkgdatadir/system-gdbinit > > You can try with --with-system-gdbinit=xxx instead. > Thanks, but surely --with-system-gdbinit is designed for the system administrator? For example, on Debian, the supplied gdb is configured with --with-system-gdbinit=/etc/gdb/gdbinit. I don't want to conflict with this usage. We can probably delete these two files, if no one else finds them useful > anymore. But I don't think you really want to use GDB's system-gdbinit > as a system-gdbinit-dir; generally speaking, my understand of the > directory provided in the GDB sources is that it's a collection of > files that are not necessarily meant to always be relevant. > Ah, OK, so I should instead configure with a different --with-system-gdbinit-dir? But how can I get my files installed in that directory? It seems like this is not something I can do with gdb's build system. So should I be using a different route to get an architecture support file always installed and loaded? -- https://rrt.sc3d.org