From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) by sourceware.org (Postfix) with ESMTPS id 5734F385AE62 for ; Sun, 19 Jun 2022 08:40:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5734F385AE62 Received: by mail-wm1-x32a.google.com with SMTP id m39-20020a05600c3b2700b0039c511ebbacso6322777wms.3 for ; Sun, 19 Jun 2022 01:40:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=668Pec95Ug/YWvZ3yOHGVMCGevU8xukRIoUL2R3sH6g=; b=u8cFAyvIH98V39cLp6lr46VKhWvRXuRIGhK8/da5J6OS0Bse9g87m5Gw4XWMrMB0LK BjMkZMqk+Os63krZrfuRxW+/py3uXByqlEQGNDw14XJisoWxiSKENxF3wnoCpskjaKvq W3T24wZrK2bkw8UjwtZLUWFKLlxCJ+CAZfgbM4cwt5xeo9lRNBLcMjK1DXkgpn5HPDjB sVzeLKAglHyaHyHQFrYBHLM0nZw+2qImPvY9Px14gwRBpmQYNhqeY+5uqFkX4XNGvD4M J53xSKGPN4TApwgo+CkkNjthSRnIdVdRkPmo207elXrJ7hrUK++4XdEkhuUDeczNraSh VWQg== X-Gm-Message-State: AJIora/aCJJ75qdB0bySsii+NFN7TzErrrWQAil2K6f4OEjQ3Q3mXeFH pC+fsSHwywFfQTvlHvkx5fI= X-Google-Smtp-Source: AGRyM1v9t8mq4MoYKcqDTueIn9egNreU55lMaip9Ag//N5S+XBmfQ/oPddqVCbbUEwk6zovIZJytTw== X-Received: by 2002:a05:600c:4e49:b0:39e:f77c:d29a with SMTP id e9-20020a05600c4e4900b0039ef77cd29amr6781204wmq.49.1655628005913; Sun, 19 Jun 2022 01:40:05 -0700 (PDT) Received: from [192.168.1.95] (host81-138-1-83.in-addr.btopenworld.com. [81.138.1.83]) by smtp.googlemail.com with ESMTPSA id d18-20020adfe852000000b002108ab90e5asm9679563wrn.58.2022.06.19.01.40.04 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Jun 2022 01:40:05 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: remove intl/ directory? From: Iain Sandoe In-Reply-To: <4169891.DDXKiFAisr@omega> Date: Sun, 19 Jun 2022 09:40:04 +0100 Cc: GCC Development Content-Transfer-Encoding: quoted-printable Message-Id: <61E1C7F4-3CC0-4346-BEE4-3FAC928C5181@googlemail.com> References: <32334822.2dzg3u6YtW@omega> <2F423461-3AF4-4BA9-95D8-EC53B49B43A2@googlemail.com> <4169891.DDXKiFAisr@omega> To: Bruno Haible X-Mailer: Apple Mail (2.3608.120.23.2.7) X-Spam-Status: No, score=-2.7 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.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2022 08:40:09 -0000 Hi Bruno, > On 19 Jun 2022, at 01:32, Bruno Haible wrote: >=20 > Iain Sandoe wrote: >> As a maintainer for GCC on a non-glibc system, I would: >> (b) not want to [force] add a shared lib dependency for my = downstream. >=20 > In order to avoid shared libs, the user merely has to pass the option > '--disable-shared' to GNU gettext's configure. Well, we try to make things easy for end-users, so actually the = objective would be that (for those who are prepared to download a pre-built binary) that = they do not have to find and build _any_ other libs.=20 =E2=80=9CDistributions=E2=80=9D might choose to go the shared library = route - on the basis that they have already presumably automated the installation of dependencies=20= - so it=E2=80=99s just that the user has to wait a little longer for the = install... For people intending to build from source, we can try to automate with = scripts and pre-fetching of prerequisites etc. .. OTOH GCC is complex enough in = its own right, it=E2=80=99s better to keep things as simple as possible. >=20 >> - so, please could we follow the pattern for GMP et. al. where the = library >> can be provided with =E2=80=94with-intl=3D pointing to an = installation >=20 > That convention is already built-in in the gettext.m4 macro; the = option is > called --with-libintl-prefix there. >=20 >> , or be built in-tree by symlinking an approved version into the GCC = tree. >=20 > If you are referring to the sentence found in the GCC documentation = for > ISL, MPFR, etc. > "If an isl source distribution is found in a subdirectory of your GCC > sources named isl, it will be built together with GCC." yes, exactly - that is usually how I build GCC - in addition to the simplification of distributing a built compiler, it also has the = advantage that the same deps that one tested with are fixed into the binary. > I believe that this can be achieved easily by adding a few lines to = the > Makefile.def, such as: >=20 > host_modules=3D { module=3D gettext-runtime; no_install=3Dtrue; > extra_configure_flags=3D'--disable-shared'; > lib_path=3Dintl/.libs; }; >=20 > The symlink 'gettext-runtime' will need to point to the = 'gettext-runtime' > *subdirectory* of an unpacked GNU gettext tarball. Thanks, that=E2=80=99s very helpful information - it could be something = to trial relatively easily. ** NOTE: this is not a GCC-only decision, intl is used by a number of = other pieces (GDB, GDB-server, binutils etc. etc) These projects share the top-level = build infrastructure =E2=80=94 [see Makefile.def and grep intl]. I suppose one could try s/intl/gettext-runtime/ and then rebuild the = top-level makefiles.. thanks, Iain