From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: frp.bissey@gmail.com, ago@gentoo.org
Subject: [gentoo-dev] RFC: Standard build environment variables
Date: Sun, 28 Jun 2020 08:18:23 -0400 [thread overview]
Message-ID: <91a59b26-94e1-9494-3f2c-ca75e8ff1426@gentoo.org> (raw)
As many of you probably know, ago@ has been expanding the scope of our
CFLAGS/CC support to include some other common build variables:
* CC
* CXX
* AR
* CPP
* NM
* RANLIB
* AS
* LD
Some of those are POSIX standards[0],
* CC
* AR
Others are de-facto GNU make standards[1],
* CXX
* CPP
* AS
and a few are de-facto GNU libtool standards[2]:
* NM
* RANLIB
* LD
If we expect them all to work properly in Gentoo, we have to agree on
what they mean, and thus how they should be injected into build systems.
For example, we had a problem with sci-mathematics/pari, whose upstream
is using the LD environment variable for something other than what GNU
libtool uses it for. With LD set to something libtooly in the
environment, the pari build fails. We can solve that by unsetting LD in
the ebuild, but for that to be The Right Thing To Do, we should be
expecting LD to contain something libtooly, and thus something
inappropriate to be passed to the pari build.
To avoid these issues, I suggest creating a list of "Gentoo environment
variables" in the devmanual with descriptions of how they should be used
and pointers to the references (for why we chose that meaning). That way
a user can export LD, for example, and know that it will be used how he
thinks it will be used.
[0] https://pubs.opengroup.org/onlinepubs/009695399/utilities/make.html
[1]
https://www.gnu.org/software/make/manual/html_node/Implicit-Variables.html
[2] https://www.gnu.org/software/libtool/manual/libtool.html
next reply other threads:[~2020-06-28 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 12:18 Michael Orlitzky [this message]
2020-06-28 14:52 ` [gentoo-dev] RFC: Standard build environment variables Kent Fredric
2020-06-28 15:25 ` Mike Gilbert
2020-06-29 8:44 ` [gentoo-dev] " Agostino Sarubbo
2020-06-29 10:04 ` Ulrich Mueller
2020-06-30 16:22 ` [gentoo-dev] " Matthew Thode
2020-07-01 13:36 ` Michael Orlitzky
2020-07-01 19:04 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91a59b26-94e1-9494-3f2c-ca75e8ff1426@gentoo.org \
--to=mjo@gentoo.org \
--cc=ago@gentoo.org \
--cc=frp.bissey@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox